Loading lesson…
Model Context Protocol is the USB-C of AI tools. Learn the protocol, wire up a server, and understand why this standard quietly changed the ecosystem.
Model Context Protocol (MCP) is an open standard, originally published by Anthropic in late 2024, that lets AI agents talk to external tools using a common JSON-RPC interface. By April 2026 it has hit roughly 100 million monthly downloads with 3,000+ indexed servers and is supported by Claude Code, Codex CLI, Cursor, and Windsurf.
Before MCP, every AI tool invented its own plugin system. If you wrote a GitHub integration for one IDE, it didn't work anywhere else. MCP is the common adapter — one server speaks to every compliant client. The USB-C analogy is apt.
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";
const server = new McpServer({
name: "weather",
version: "1.0.0",
});
server.tool(
"get_forecast",
{
city: z.string().describe("City name"),
},
async ({ city }) => {
const res = await fetch(`https://api.weather.example/${city}`);
const data = await res.json();
return {
content: [{ type: "text", text: JSON.stringify(data) }],
};
},
);
const transport = new StdioServerTransport();
await server.connect(transport);A real MCP server in ~20 lines. Any compliant client can now call get_forecast with a city string.{
"mcpServers": {
"weather": {
"command": "node",
"args": ["/path/to/weather-server/index.js"]
},
"postgres": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-postgres", "postgresql://localhost/mydb"]
}
}
}A claude_desktop_config.json or .claude/mcp.json file wiring two servers. Same file format across Claude Code, Cursor, and Windsurf.| Category | Example servers |
|---|---|
| Databases | Postgres, SQLite, MongoDB, Redis |
| Version control | GitHub, GitLab |
| Docs | Sentry, Linear, Notion, Confluence |
| Cloud | AWS, Vercel, Cloudflare, Stripe |
| Browsers | Playwright, Puppeteer, Chrome DevTools |
Protocols are patient. They don't win today; they win in five years.
— A veteran protocol designer
The big idea: MCP turned AI coding tools from siloed islands into a composable ecosystem. If you build, extend, or integrate AI agents in 2026, this is the protocol layer you cannot ignore.
15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-coding-mcp-external-tools-creators
What problem was MCP designed to solve in the AI tooling landscape?
What communication interface does MCP use to let AI agents talk to external tools?
Which company originally published the Model Context Protocol?
What does the 'USB-C analogy' refer to in the context of MCP?
What are the three primitive categories defined in MCP?
In MCP terminology, what are 'Tools'?
What type of data can MCP 'Resources' provide to an AI agent?
What are MCP 'Prompts' used for?
What is a key security advantage of MCP servers running locally by default?
Where does authentication flow in MCP's architecture?
Why should you audit the source code of MCP servers before installing them?
What does the lesson identify as the minimum observability requirement for MCP deployments?
Which permission model does MCP support for agents attempting to modify production systems?
What architectural change did MCP bring to AI coding tools?
By April 2026, approximately what was MCP's monthly download metric?