The open protocol for connecting models to tools, data, and prompts across vendors.
13 articles
Listed inData LayerModel Context Protocolon
The normative source: lifecycle, capability negotiation, transports, and the exact shape of tools, resources, and prompts.
Listed inModel Context Protocol (MCP)Model Context Protocolon
Hosts, clients, servers, and the three primitives a server can expose — with a working TypeScript server in forty lines and the four mistakes that make one useless.
Listed inModel Context Protocol (MCP)Model Context Protocolon
The announcement that started the ecosystem — why a shared protocol beats N×M bespoke integrations.
Listed inTransport LayerModel Context Protocolon
stdio and streamable HTTP, and which one your deployment needs.
Listed inMCP ServerModel Context Protocolon
The process that exposes tools, resources, and prompts to a host.
Listed inMCP HostModel Context Protocolon
The application that owns the model loop and decides which servers to trust.
Listed inConnect to a Local ServerModel Context Protocolon
Running a server over stdio next to your app during development.
Listed inBuilding an MCP ServerModel Context Protocolon
Defining tools with schemas and returning results a model can actually use.
Listed inData LayerModel Context Protocolon
Tools, resources, and prompts — the three things a server can expose.
Listed inMCP ClientModel Context Protocolon
The per-server connection the host spawns to speak the protocol.
Listed inConnect to a Remote ServerModel Context Protocolon
Auth, transport, and trust when the server isn't on your machine.
Listed inModel Context Protocol (MCP)Model Context Protocolon
A standard wire format so tools work with any model host.
Listed inBuilding an MCP ClientModel Context Protocolon
Connecting, listing capabilities, and wiring calls into your own loop.