Technical Explainer

Model Context Protocol: A Technical Overview for Enterprise Architects

Model Context Protocol (MCP) is an open standard, introduced by Anthropic, that defines a common client-server interface for connecting AI models to external tools, data sources, and services. It replaces custom point-to-point integrations with a standardized protocol built on JSON-RPC 2.0.

MCP at a Glance

Origin

Introduced by Anthropic as an open-source standard in late 2024

Architecture

Host, client, and server roles connected via JSON-RPC 2.0

Core primitives

Tools, resources, and prompts exposed by MCP servers

Transport

Local stdio-based or remote HTTP-based connections

What Problem MCP Solves

Before MCP, connecting an AI model to external tools and data sources typically required a custom integration for every pairing of model and system. Each new data source or tool meant writing and maintaining bespoke connector code. MCP replaces this pattern with a single, standardized interface: a tool or data source that implements an MCP server can be used by any AI application with a compatible MCP client, without a custom integration for each combination.

How the Architecture Is Structured

MCP defines three roles. The host is the AI application the user interacts with. The client, embedded in the host, manages a connection to a single MCP server. The server exposes tools, resources, or prompts that the model can use. Communication between client and server runs over JSON-RPC 2.0, a lightweight remote procedure call format, which keeps message structure consistent regardless of what the server does internally.

Core Primitives in the Specification

MCP servers expose functionality through three primitives: tools, which are functions the model can invoke to take action; resources, which are data the model can read for context; and prompts, which are reusable templates that structure how a task is presented to the model. This shared vocabulary is what allows different hosts and servers to interoperate without custom negotiation.

Security and Governance Considerations

MCP defines message formats, capability negotiation, and transport options, but it does not mandate authentication, authorization, or audit logging. Those controls must be implemented by the host, the server, or a governance layer operating alongside the protocol. This has a direct architectural consequence worth stating plainly:

  1. 1

    Where MCP extends the agent's permission boundary

    Connecting an AI agent to an MCP server is not a passive integration. It extends what that agent can effectively do to whatever the connected server is capable of doing.

A local, stdio-based server operates within the trust boundary of the host machine, which reduces network exposure. A remote, HTTP-based server introduces a network-accessible attack surface and requires its own authentication and access controls to reach an equivalent level of safety. Enterprises evaluating MCP adoption need to treat each server connection as a permission grant, not a neutral technical hookup.

Practical Implementation Decisions

Teams adopting MCP in production generally need to decide, explicitly, which servers are approved, how those servers are authenticated, and how tool calls are logged. These are organizational and architectural decisions that sit alongside the protocol rather than being answered by it.

Common Questions on MCP Adoption

Does MCP itself provide security controls?

No. MCP defines message formats, capability negotiation, and transport options, but does not mandate authentication, authorization, or audit logging. These must be implemented by the host, the server, or a governance layer alongside the protocol.

Is a local MCP server inherently safer than a remote one?

A local stdio-based server operates within the trust boundary of the host machine, reducing network exposure. A remote HTTP-based server introduces a network-accessible attack surface and requires its own authentication and access controls to reach equivalent safety.

Can one MCP server be used by multiple AI applications?

Yes. Because MCP standardizes how tools, resources, and prompts are exposed, a single server implementation can be reused across different AI hosts that implement a compatible MCP client, without custom integration code for each pairing.

Questions Architects Should Answer Before Production Adoption

  • Which MCP servers, internal or third-party, will agents be permitted to connect to, and who approves that list
  • What authentication and authorization mechanisms are enforced for any remote MCP server connection
  • How are tool calls and their responses logged and audited across MCP-enabled deployments
  • What MCP specification version do current client and server implementations support, and how is compatibility tracked
  • How is a third-party server's tool exposure reviewed before it is granted access to sensitive systems or data

Evaluate MCP Adoption With Governance in Mind

Understanding MCP architecture is the first step. Enforcing least privilege, tool approval, and audit logging across MCP-connected agents is the operational work that follows.

Explore MCP Security