Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Use case: custom CRM

Connect a custom CRM to Claude

If your CRM is custom, in-house, or heavily modified, it is not in Claude's connector directory. We build and maintain a custom MCP connector for your exact system, with scoped read-write access.

Build my connectorSee how it works

How do I connect a custom CRM to Claude?

Connecting a custom CRM to Claude requires a custom MCP connector, a small server that exposes your CRM's data and actions to Claude over the Model Context Protocol. Because custom and in-house CRMs are not in Claude's connector directory, the connector has to be built specifically for your system, with read and scoped write access.

How do we build a connector for your CRM?

We build a connector for your CRM in three steps: map your data and the actions Claude should take, build and host a custom MCP server with separated read and write tools, then connect it in Claude. You do not run or maintain any server, because that is the part we own.

01

Map your CRM

On a short call we map your objects (contacts, companies, deals, activities, custom fields) and decide what Claude should be able to read and which write actions need a confirmation step.

02

Build the connector

We build and host a custom MCP server with separated read and write tools, OAuth where your CRM supports it, and scoped permissions matched to your account.

03

Connect and use

You add the connector in Claude and work in your day-to-day. We maintain it as your CRM's schema and API change, so it keeps working.

How does authentication work?

Authentication works by connecting as your CRM account, using OAuth where your CRM supports it or a scoped API key where it does not. The connector inherits your existing permissions and never grants Claude more access than your account already has. We handle the OAuth lifecycle, including token refresh, so connections stay live.

What about an on-prem CRM behind a firewall?

An on-prem CRM behind a firewall can still connect to Claude. We build the connector to reach your system through IP allowlisting, a tunnel, or a small component inside your network, scoped only to the endpoints Claude needs. We work with your IT so access stays tight, auditable, and inside your control.

How long does it take and what does it cost?

Timeline and cost depend on how many CRM objects and write actions you need and how your system is reachable. After a short scoping call we give you a fixed quote and a build estimate. Pricing is a one-time build fee plus a monthly maintenance fee that keeps the connector working as your CRM changes.

We scope each connector to your CRM objects, write actions, and how your system is reachable, so the quote fits your build. See current pricing for how the one-time build fee and monthly maintenance fee work.

See pricingSee the custom CRM connectorHow we build connectors

Frequently asked questions

How do I connect a custom CRM to Claude?
You connect a custom CRM to Claude with a custom MCP connector that we build for your specific system. Because in-house and bespoke CRMs are not in Claude's connector directory, there is nothing to install off the shelf. We map your data and actions, build and host the connector, and you add it in Claude with scoped read-write access.
Can Claude write back to my CRM, or only read from it?
Claude can write back. The connector exposes write tools, so Claude can create and update contacts, companies, deals, activities, and custom fields. Create and update flow freely inside a conversation you start. Destructive or outbound actions like deleting a record or sending an email are gated behind a human-in-the-loop confirmation you control.
How does authentication work for a custom CRM connector?
The connector authenticates as your CRM account, using OAuth where your CRM supports it or a scoped API key or token where it does not. It inherits your existing permissions and never grants Claude more access than the account already has. We handle the OAuth lifecycle, including token refresh, so connections stay live.
My CRM is on-prem or behind a firewall. Can it still work?
Yes. We build connectors for internal and on-prem CRMs that are not reachable from the public internet. Depending on your setup that means IP allowlisting, a tunnel, or a small component inside your network, scoped to only the CRM endpoints Claude needs. We work with your IT to keep access tight and auditable.
What if my custom CRM's schema changes later?
We maintain the connector over time. When your CRM adds fields, changes its API, or rotates auth, we update the connector so it keeps working. That ongoing maintenance is the difference between a one-off script that breaks and a connector your team can rely on in production.

Tell us about your CRM. We'll build the connector.

Book a 30-minute scoping call. We'll map your CRM's objects, the actions Claude should take, and what full read-write would unlock.

Build my connectorTalk to us