Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Insightly to Claude Code

Make Claude create records and advance opportunities in Insightly. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Insightly to Claude Code?

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

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

Full read-write Insightly access lets Claude create and update leads, contacts, organizations, and opportunities, move an opportunity to the next pipeline stage, link a record to a project, and log notes, tasks, and events. The data entry that used to live between tabs happens where your CRM already keeps it.

  • Create or update a lead, contact, or organization from a conversation or email
  • Advance an opportunity to the next pipeline stage and update its value
  • Create a contact and linked opportunity from a lead's details (the API has no one-click lead conversion, so Claude recreates and links the records)
  • Log a note, task, or event against the right record
  • Link a closed opportunity to a new delivery project
  • Find every record matching a query and propose batched field 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 Insightly 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 Insightly API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Insightly 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 Insightly 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 Insightly 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 Insightly 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 Insightly'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 Insightly?
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 Insightly account it signs in with. Revoking access is one click in Insightly.

More on the Insightly connector

Insightly connector for claude.aiGoHighLevel + Claude CodeFreshsales + Claude CodeSugarCRM + 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 connectorTalk to us