MCP explained: how Claude reaches your tools
Sep 2026 · 7 min read · Updated Sep 2026
Quick answer
MCP is a protocol. It lets a model call tools through a shared shape instead of a one-off integration for every app. Anthropic published it as an open standard. It does not make Claude your employee. A connector still needs auth, a scope, and a person who can turn it off. When we wire that into a product, it is AI development, not a plugin you flip on and forget.
Key takeaways
- MCP is the adapter. Your CRM is still the system of record.
- Off-the-shelf connectors exist for common tools. Internal tools need a build.
- Scope the permissions like any other integration. Read-only is a choice, not a default.
- If the job is a nightly sync with retries, you may want n8n automation instead of a chat loop.
What MCP is
Without a connector, you paste. With MCP, Claude can ask a server for calendar events, a ticket, a row. The server talks to the API. The model stays in the conversation. That is the whole trick.
It is not magic access. It is JSON-RPC with a spec. A custom connector is usually a small service plus OAuth. We will not quote a connector count. The catalogue moves weekly.
When it is the right shape
- A person is in the loop and wants one conversation across two or three tools
- The action is occasional: a brief, a ticket, a summary
- You can name the worst case if the model is wrong
A board pack every Friday from three systems can be MCP. It can also be an n8n workflow that posts to Slack without anyone prompting. If nobody needs to chat, do not put a chat in the middle. See Claude as a step in n8n.
What it costs
Claude Pro is $20 a month ($17 annual) on the list we checked in Sep 2026. That is the person. API usage is the product. Pre-built desktop connectors are typically free on top of that. A custom connector for an internal tool is engineering. We scope it in weeks at $2,000 a week.
Treat MCP like any OAuth app. Least privilege. A kill switch. Do not hand write-access to the CRM because the demo looked clever.

