Connect Capsule CRM to Claude Code

Make Claude log activity and move deals through the pipeline in Capsule CRM. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Capsule CRM to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Capsule CRM, you add a Capsule CRM MCP server: a small hosted service that exposes Capsule CRM's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Capsule CRM account. No API keys pasted into config files.

claude mcp add --transport http capsule-crm https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Capsule CRM once connected?

Full read-write Capsule access lets Claude create and update contacts and organisations, log notes and activity against a record, create and advance opportunities through pipeline stages, manage tags, and add tasks. The record-keeping that used to mean switching tabs happens where your CRM data already lives, with your approval on the actions that matter.

Create a new person or organisation record with the right fields populated
Log a note or activity against an existing contact or opportunity
Create an opportunity and move it through pipeline stages
Add, apply, or remove tags to segment your contacts
Create a task and assign it to a teammate
Update a contact's details after you approve the change

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Capsule CRM access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Capsule CRM API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Capsule CRM changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Capsule CRM connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Capsule CRM connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Capsule CRM account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Capsule CRM's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Capsule CRM?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Capsule CRM account it signs in with. Revoking access is one click in Capsule CRM.

More on the Capsule CRM connector

Capsule CRM connector for claude.ai GoHighLevel + Claude Code Freshsales + Claude Code Insightly + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us