Skip to main content
Setting up a CRM used to take days in settings screens. With Orbit’s MCP server you tell an agent how you sell. It builds the structure, tells you what it did, and changes it later the same way.
1

Connect an agent

Connect Claude, ChatGPT, Claude Code or Cursor to Orbit (how). On the consent screen, approve crm:write for the setup itself, plus contacts:write, companies:write and deals:write for the records it will work with.
2

Describe how you sell

Explain your sales process in plain words. The agent turns it into pipelines, stages, custom fields, settings and saved views.
3

Check and adjust

Ask the agent to read the setup back to you. Change anything later the same way: split a stage, add a field, save a new view.

​
Set up the structure

Start with how your team actually sells:
“We sell annual contracts. SDRs book demos, then AEs run discovery, send a proposal and negotiate. Set up a New business pipeline for that, plus a Renewals pipeline. On deals we track contract value, seats, renewal date and lead source. Require a lost reason, and flag deals that sit in a stage for more than 14 days.”
What the agent does:
Give each custom field a description. Agents read field descriptions through get_crm_schema before they write data, so write them the way you would explain the field to a new rep.

​
Check the agent’s work

“Read back the pipelines, their stages and probabilities, and every custom field on deals.”
The agent reads the setup with get_crm_schema and list_pipelines, and its own result messages name what it created, so nothing happens silently.

​
Keep shaping it

The same agent keeps the CRM in shape as your process changes:
“Split Proposal into Proposal sent and Verbal yes, and move the deals that are waiting on a signature.”
“Add an Industry select field on companies with SaaS, Agency, Ecommerce and Other, and fill it in for every company.”
“Save a contacts view of qualified leads with no meeting yet, sorted by last activity.”

​
Work the records

Once the structure is there, the agent works the data the same way: it opens companies and deals for qualified leads, fills in fields it has researched, logs calls and meetings with log_activity, adds notes and tasks, and moves deals between stages. A lead list from a spreadsheet goes in with import_contacts, up to 1,000 rows per call, with tags, owners and companies in the same call and any rows with a problem listed back. Available tools lists everything it can do.
Moving from another CRM? That is a job for Orbit, not for the agent. From HubSpot, Settings → Integrations → HubSpot → Import from HubSpot brings contacts, companies, deals, pipelines, custom properties and history across in the background, with HubSpot ids kept (how it works). From any CRM, developers can load records through the API’s bulk imports: see Migrating from another CRM.
Agents connected over MCP can’t delete contacts, companies or deals. That needs the :delete scopes, which only API keys and OAuth apps registered in the Developer Portal can hold on the REST API; assistants that register themselves over MCP never get them. See Available Tools for everything an agent can do.