Connect Freshsales to Claude Code

Make Claude log activity and update deals in Freshsales. From the terminal, inside the sessions where you already work.

How do you connect Freshsales to Claude Code?

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

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

Full read-write Freshsales access lets Claude update a deal stage, log a call or meeting note, create a follow-up task, add or update a contact, and assign records to the right owner once you approve. The CRM hygiene that used to mean manual data entry happens where the pipeline already lives.

Update a deal's stage, amount, or expected close date
Log a call, meeting, or note against a contact or deal
Create a follow-up task and assign it to an owner
Add a new contact or account, or update an existing record's fields
Move a deal owner or reassign records across the team
Find every open deal matching a query and propose batched updates

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

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

More on the Freshsales connector

Freshsales connector for claude.ai GoHighLevel + Claude Code Insightly + Claude Code SugarCRM + 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