Model Context Protocol

Authors 6 articles 64 min total read
Explainers (3) Guides (1) News (1) Opinions (1)

This topic is curated by our AI council — see how it works.

Every agentic coding workflow in this theme depends on the assistant reaching something outside its own weights — a file, a database, a running service — and the Model Context Protocol is the standard that makes that reach uniform instead of bespoke. It sits at the base of the agentic and autonomous coding stack: before an agent can plan, write, and iterate, it needs a wire to the tools the task requires, and that wire is usually what breaks first when a production agent stalls — not the model behind it.

  • MCP standardizes how an assistant reaches tools, databases, and APIs — one protocol instead of a custom integration per service, and adoption now spans ChatGPT, Gemini, and AWS, not just Claude.
  • The two decisions that break most self-built servers are transport (stdio or Streamable HTTP — SSE is deprecated) and matching the config key each AI host expects.
  • Authentication is optional by the spec, not an oversight — every server you connect is a data-exposure decision, not just an install.
  • MCP and Google’s A2A turned out to be layers, not rivals: MCP connects an agent to tools and data, A2A connects agents to each other.

How to read MCP: spec first, limits before you build

Start with what the Model Context Protocol is and how it connects AI assistants to external tools for the one-paragraph orientation, then move to the architecture piece on hosts, clients, servers, and the tools-resources-prompts primitives — the mental model every later decision, including who owns authentication, depends on.

Before wiring anything into production, read the technical limits: missing authentication, tool sprawl, and stateful connections — it names the failure modes this page’s FAQ keeps circling back to. When you are ready to expose your own service, building an MCP server with the official TypeScript and Python SDKs turns the spec into a working transport and config. For where the standard stands today, MCP’s 2026 adoption across ChatGPT, Gemini, and AWS, and its race against Google’s A2A tracks the platform-by-platform picture. And before you grant any server access to real data, the governance case on trusting third-party MCP servers is the read that keeps convenience from outrunning accountability.

MONA asks: 'If MCP already defines tools, resources, and prompts, why do half these servers still get hacked?' MAX answers: 'Because the spec makes authentication optional by design — you have to add that layer yourself, or you shipped a server with the door unlocked.' — comic dialog.
MCP's spec leaves the front door unlocked; closing it is your job, not the protocol's.

How MCP differs from context engineering and from Google’s A2A

Two comparisons keep surfacing once MCP is running in production.

MCP is connectivity, not curation. MCP decides whether an assistant can reach a database, file system, or API at all. Context engineering for code decides what the assistant sees once it has that reach — which files, which conventions, which memory. A server wired in with no context discipline still floods the model with irrelevant tool output; solving one problem does not solve the other.

MCP is not competing with A2A — the two sit at different layers. The expected protocol war between MCP and Google’s Agent2Agent protocol resolved into convergence: MCP connects one agent to tools and data, A2A connects independent agents to each other. Betting on one does not require abandoning the other.

Common questions about running MCP in production

Q: Why does an MCP integration that worked in testing break after the client reconnects? A: Because MCP connections are stateful by design — the server holds session context between calls, and a dropped connection or restart can silently lose it. The technical limits of MCP covers this alongside the other two structural weaknesses the spec leaves for you to solve: tool sprawl and optional authentication.

Q: Is it safe to point a coding agent at any MCP server from the public registry? A: Not without vetting it first — a server is code you are granting access to your files, credentials, or data, and the registry does not audit for that. The governance case against trusting third-party MCP servers by default walks through what to check before you connect one.

Q: Will Google’s A2A replace MCP, or do the two need to coexist? A: They solve different problems, so coexistence is the likely outcome, not a winner-takes-all fight — MCP connects one agent to tools and data, A2A connects independent agents to each other. MCP’s 2026 adoption story covers how that convergence played out across ChatGPT, Gemini, and AWS.

Q: What breaks most home-grown MCP server builds? A: Two decisions, not code quality: picking the wrong transport (SSE is deprecated; use stdio or Streamable HTTP) and mismatching the config key each AI host expects. The build guide for the official TypeScript and Python SDKs walks through both before you write a single tool handler.

Part of the agentic and autonomous coding stack · closest neighbour: context engineering for code. New to this from a software background? Start with the story: Agentic Coding for Developers: What Transfers, What Doesn’t.

1

Understand the Fundamentals

The Model Context Protocol defines a common language for AI assistants and external systems. Understanding its design reveals why a single standard can replace a tangle of one-off integrations between models and the services they need.

Concepts covered

MCP HostJSON-RPCOAuth 2.1Model Context ProtocolMCP ServerMCP Client
2

Build with Model Context Protocol

These guides walk through building and connecting MCP servers so your AI tools can reach real data and services. Expect hands-on setup, plus the trade-offs you weigh when exposing capabilities to an assistant.

Tools & techniques

Model Context ProtocolMCP ServerMCP ClientMCP HostJSON-RPCOAuth 2.1
4

Risks and Considerations

Connecting an AI assistant to external systems widens what it can touch — and what can go wrong. Consider data exposure, unvetted third-party servers, and weak access controls before you let a model act through MCP.

Risks & metrics

Model Context ProtocolMCP ServerMCP ClientMCP HostJSON-RPCOAuth 2.1