Glossary term
What is a custom Claude connector?
A custom Claude connector is a tailored MCP connector built for one specific tool or account, so Claude can read and write that tool's data. It is a small hosted server that exposes your software's actions to Claude over the Model Context Protocol. Unlike a directory connector, it is built for software that is not listed or needs more access.
Why does a custom Claude connector matter?
A custom Claude connector matters because most real tools are not in Claude's connector directory, and many that are stay read-only. A custom connector closes that gap. It lets Claude work directly inside the exact software your team uses, with the read and scoped write access your own account already has.
Without a connector, Claude can only discuss your data secondhand, from text you paste in. With a custom connector, Claude pulls live records and takes actions in the tool itself. That is the difference between an assistant that talks about your work and one that does it with you. See what full read-write access unlocks for how scoped write actions work in practice.
How does a custom connector relate to a Claude connector?
A custom connector is a kind of Claude connector. Every connector, prebuilt or custom, is an MCP server that speaks the Model Context Protocol and exposes tools Claude can call. The difference is scope: a directory connector is prebuilt for a popular tool, while a custom connector is built for one specific system or account.
Because both kinds share the same protocol, Claude treats a custom connector exactly like a directory one once it is added. You can browse the tools we already support on the custom connectors directory, or read the complete guide to custom Claude connectors for the full picture.
What is an example of a custom Claude connector?
An example of a custom Claude connector is one built for an in-house CRM that is not in Claude's directory. The connector exposes tools to read contacts and deals and to create or update records. Claude can then look up an account, draft a follow-up, and log the activity back, all without you leaving the conversation.
The same pattern applies to a niche industry platform, an internal ticketing system, or a tool behind your firewall. If the software has an API, a custom connector can give Claude scoped read-write access to it.
Frequently asked questions
Is a custom connector the same as a regular Claude connector?
Do I have to build a custom connector myself?
Can a custom connector write data, not just read it?
What software can a custom connector work with?
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.
