Connect Salesflare to Claude Code

Make Claude move deals and log activities in Salesflare. From the terminal, inside the sessions where you already work.

How do you connect Salesflare to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Salesflare, you add a Salesflare MCP server: a small hosted service that exposes Salesflare'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 Salesflare account. No API keys pasted into config files.

claude mcp add --transport http salesflare 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 Salesflare once connected?

Full read-write Salesflare access lets Claude update an opportunity's stage and value, add or edit contacts and accounts, log a meeting or call, set tasks, and attach notes to the right record. The pipeline hygiene that used to mean manual data entry happens inside the CRM, once you approve it.

Move an opportunity to a new pipeline stage and update its value
Create or update a contact and link it to the right account
Log a call, meeting, or email as an activity on a record
Create a follow-up task with a due date and assignee
Add a note to an account summarizing the latest interaction
Update custom fields on an opportunity after a discovery call

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 Salesflare 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 Salesflare API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Salesflare 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 Salesflare 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 Salesflare 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 Salesflare 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 Salesflare'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 Salesflare?

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 Salesflare account it signs in with. Revoking access is one click in Salesflare.

More on the Salesflare connector

Salesflare 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