Skip to main content
The Orbit MCP server exposes more than 100 tools, grouped by area below. Together they make Orbit a CRM your agents can both work in and build: read and update contacts, companies, deals, tasks and notes; work forms, meetings, sequences and workflows; configure fields, pipelines, settings, views and teams; and configure the dialer, build call lists, write call scripts and read call outcomes, transcripts and AI feedback (calls themselves are only ever placed by a person from the Dialer page). Each table lists the name an agent calls, what the tool does, the scope its credential needs, and its access level:
  • Read: only looks. Hosts usually run these without asking.
  • Write: changes data inside your Orbit workspace.
  • Outbound: also emails someone, sends a calendar invite, or delivers data to a URL outside Orbit, so hosts ask before running it.
The same list is in the app under MCP → Tools available. An agent can configure the whole CRM over MCP: start with get_crm_schema, then add fields, build pipelines and change settings. Build your CRM walks through it end to end. Configuration deletes (fields, stages, pipelines, views, teams) and task / note deletes are available; deleting contacts, companies, deals and workflows is intentionally left to the REST API, which needs the :delete scopes. Find any contact, company, deal or task by name, email, domain or phone number in one call, best match first, within what the credential may see.

CRM setup

Read the whole CRM in one call, change object settings, and manage custom fields on contacts, companies and deals.

Pipelines

Build and reshape deal pipelines and their stages, and control who can see each pipeline.

Saved views & lists

Saved views of the Contacts table: columns, filters and sort.

Contacts

People, the tags you organize them with, CSV imports and duplicate merges.

Companies

Accounts. A company domain links contacts with matching emails.

Deals

Opportunities in your pipelines, with their company, contacts, stage history and pipeline totals.

Tasks

Follow-ups linked to a contact, company or deal.

Notes

Notes on a contact, company or deal, and comments on notes and logged activity.

Activity & timeline

A record’s whole timeline and its field changes, and the emails, calls, meetings and messages that happened outside Orbit: log them one at a time or import history in bulk (with undo).

Files

Files on contacts, companies and deals: list them, get download links, bring them in from URLs, delete them.

Team

Named groups of team members, used to filter records and share pipelines.

Workflows

Build, run and inspect automations, and the AI agent templates they use.

Forms & submissions

Your forms and what people submitted.

Scheduling & meetings

Scheduling pages, availability, and the meetings booked through them.

Sequences

Email sequences: build them and write their steps, activate or pause them, see how they perform and who is enrolled.

Email templates

Email templates and snippets people insert in the composer, Inbox replies and sequence steps. Merge fields like {{ contact.first_name }} fill in per recipient; add a fallback with {{ contact.first_name | there }}.

Emails

One-to-one email from a contact’s page: send an email to a contact from the connected person’s address, and read what the team sent with its delivery, open and reply status.

Dialer

Configure the power dialer, preview call lists built from saved views, read calls, outcomes and statistics, manage the do-not-call list, write the call scripts reps read on a call, and read each call’s transcript and AI feedback. Calls are only ever placed by a person from the Dialer page.

Webhooks

Deliver submission events to your own endpoints.

Integrations

Which apps are connected to the workspace and whether they are syncing. Credentials never leave Orbit.

Annotations

Every tool carries the MCP tool annotations hosts use to decide when to ask before running it. Read-only tools can run without a confirmation; the others are marked by what they change.

Booking a meeting

An agent books a meeting in three steps: find the scheduling page and event type (list_scheduling_pages → list_event_types), fetch open slots for a date with get_available_slots (working hours intersected with the host’s live calendar free/busy), then call book_meeting with one of the returned slots. Booking creates the meeting, sends calendar invites to both sides, and triggers configured workflows; a taken slot returns a 409 so the agent can pick another. The team_id on these calls is always derived from your credential server-side — it cannot be overridden.

Rate limits & behavior

MCP tool calls execute the corresponding /api/v1 endpoints internally, so REST API rate limits apply unchanged. List tools return the same paginated envelope as the REST API (data plus meta.total / meta.page / meta.total_pages); pass page and per_page arguments to page through results. Tool results include the JSON payload as both text and structuredContent; errors carry the HTTP status and the same error / error_description the REST API returns.