Skip to content
Custom Connectors

Glossary term

What is the Model Context Protocol (MCP)?

The Model Context Protocol (MCP) is an open standard that lets AI assistants like Claude connect to outside tools and data in a consistent way. Instead of teaching the assistant each system by hand, MCP defines how a small server describes its tools, so the assistant can read information and take actions safely.

Why does the Model Context Protocol matter?

The Model Context Protocol matters because it gives every tool one shared way to talk to AI assistants. Before MCP, each integration was a one-off. With a common standard, the same connector can be reused across compatible clients, and an assistant can work directly inside your real systems instead of guessing from copied-in text.

For a buyer, the practical payoff is reach. Because MCP is open, the list of software Claude can work with is not limited to a fixed directory. Any tool with an API can be exposed through a connector, which is exactly what makes custom connectors for niche and in-house software possible.

How does MCP relate to a connector?

MCP relates to a connector as the protocol relates to the product. MCP is the language. A connector is a specific server that speaks that language for one tool, like a CRM or a billing system. You add the connector in Claude, it exposes that tool's read and write actions over MCP, and Claude uses them on your behalf.

That separation is why a connector can be scoped. The server decides which tools to expose and how, so it can offer full read-write access while still gating destructive or outbound actions behind a human-in-the-loop confirmation. The connector never grants Claude more access than your own account already has. To go deeper, the complete guide to custom Claude connectors walks through how a connector is built, authenticated, and maintained.

What is an example of MCP in practice?

An example of MCP in practice is connecting Claude to an invoicing tool. The connector exposes tools such as list invoices, create an invoice, and mark one paid. You ask Claude to draft this month's invoices, it reads the right records and creates drafts through those tools, and you approve before anything is sent.

Related terms

  • MCP connector: The packaged server you add in Claude so it can use a specific tool over MCP.
  • Custom connector: An MCP connector built for software that is not in Claude's directory, including in-house systems.
  • Full read-write: A connector that can both read your data and take scoped write actions, not just look.

Frequently asked questions

Is the Model Context Protocol open?
Yes. MCP is an open standard, so any software vendor or team can build a server that exposes their tool to AI assistants, and any AI client can speak the same protocol. Because it is open, you are not locked into a single integration, and a connector built for one MCP client can be reused with others that support the standard.
Does MCP give an AI assistant access to my data?
Only through the tools a connector chooses to expose, and only with the credentials you provide. An MCP connector authenticates as your own account and inherits your existing permissions. It never grants Claude more access than you already have, and write actions can be scoped so create and update flow while destructive or outbound actions are gated behind a confirmation.
What is the difference between MCP and an API?
An API is how two pieces of software talk in general. MCP is a specific standard for how an AI assistant discovers and calls tools, so it does not have to be taught each API by hand. An MCP connector usually sits on top of a tool's existing API and translates it into tools the assistant can read and write through.
Do I need to know about MCP to use a connector?
No. MCP is the plumbing. As a user you add a connector in Claude, authenticate, and start working in plain language. The protocol matters to the people who build the connector, because it defines how the server describes its tools to Claude and how Claude calls them safely.

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.