MCP Deep Dive: The USB-C for AI Tools

Model Context Protocol is the most important open standard in agents. One protocol, 1,200+ servers, and your agent can plug into almost any system. Here's how it actually works.

55 min · Reviewed 2026

Why MCP exists

Before MCP, every agent-to-tool connection was custom. Claude had one way to call a database. GPT had another. Your LangChain glue was a third. Multiply that by 1,000 tools and you had a combinatorial nightmare. Anthropic introduced MCP in late 2024 as 'USB-C for AI tools' — one protocol, any client, any server. By 2026 it's backed by Anthropic, OpenAI, Google, and the GitHub registry has 1,200+ servers.

The architecture

Piece	Role
Host	The app the user interacts with (Claude Desktop, Claude Code, Cursor, OpenClaw).
Client	The host's MCP client instance, one per connected server.
Server	A separate process exposing tools/resources/prompts.
Transport	stdio (spawned subprocess) or HTTP/SSE (remote service).
Protocol	JSON-RPC 2.0. Typed message schemas.

What a server exposes

Tools — function-like actions (call with args, get a result).
Resources — readable data URIs (file://, db://, custom://).
Prompts — reusable prompt templates the host can surface.
Sampling (optional) — server can ask host's model for completions.
Roots — URI hints about where the server operates.

A real MCP config

{ "mcpServers": { "filesystem": { "command": "npx", "args": [ "-y", "@modelcontextprotocol/server-filesystem", "/Users/you/projects" ] }, "github": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-github"], "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_" } }, "supabase": { "command": "npx", "args": [ "-y", "@supabase/mcp-server-supabase@latest", "--project-ref", "your-project-ref" ], "env": { "SUPABASE_ACCESS_TOKEN": "sbp_" } }, "notion": { "url": "https://mcp.notion.com/sse", "transport": "sse", "headers": {"Authorization": "Bearer ntn_"} } } }Claude Desktop / Claude Code MCP config. Four real servers in the April 2026 registry. Drop this into ~/.claude/claude_desktop_config.json and restart.

Writing your own MCP server

// A tiny MCP server in TypeScript (@modelcontextprotocol/sdk) import { Server } from "@modelcontextprotocol/sdk/server/index.js"; import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js"; import { CallToolRequestSchema, ListToolsRequestSchema, } from "@modelcontextprotocol/sdk/types.js"; const server = new Server( { name: "my-server", version: "0.1.0" }, { capabilities: { tools: {} } } ); server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: [{ name: "greet", description: "Say hello to a person.", inputSchema: { type: "object", properties: { name: { type: "string" } }, required: ["name"], }, }], })); server.setRequestHandler(CallToolRequestSchema, async (req) => { if (req.params.name === "greet") { const name = (req.params.arguments as any)?.name ? "friend"; return { content: [{ type: "text", text: `Hello, ${name}!` }] }; } throw new Error("Unknown tool"); }); const transport = new StdioServerTransport(); await server.connect(transport);A complete, minimal MCP server. Registers one tool, speaks stdio. About 30 lines.

Servers worth knowing (April 2026)

modelcontextprotocol/server-filesystem — scoped file access.
modelcontextprotocol/server-github — issues, PRs, repos.
modelcontextprotocol/server-postgres — SQL over any Postgres.
Supabase, Neon, Vercel, Stripe — all ship official first-party MCPs.
Zapier MCP — proxies to 8,000+ Zapier-connected apps.
Notion, Linear, Slack, Google Drive, Calendar — official.
Chroma, Pinecone, Vectara — vector DBs for RAG.
Sentry, Datadog — observability from inside your agent.

Transports

Transport	Use case	Pros	Cons
stdio	Local-only, spawned by host.	Zero network; trivial auth.	One process per client.
SSE / HTTP	Remote or shared server.	Multi-tenant, scales.	Need auth, TLS, ops.
Streamable HTTP (2025+)	Bidirectional over HTTP/2.	Best of both; modern.	Newer, fewer libs.

MCP is the one thing to learn cold. Once you have it, every agent gets cheaper, every tool is reusable, and switching models becomes a config change.

End-of-lesson check

8 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-agentic-mcp-deep-dive-creators

What is the main idea of "MCP Deep Dive: The USB-C for AI Tools"?
1. Model Context Protocol is the most important open standard in agents.
2. Use AI as the final authority for the whole decision
3. Avoid checking the answer once it sounds polished
4. Focus only on speed instead of judgment
Which concept is most central to "MCP Deep Dive: The USB-C for AI Tools"?
1. Model Context Protocol
2. MCP
3. MCP server
4. stdio transport
Which use of AI fits this topic best?
1. Let the AI decide what matters without your review
2. Use the answer before checking whether it fits the situation
3. Tools — function-like actions (call with args, get a result).
4. Treat the AI output as automatically correct
What should a careful learner remember about "MCP servers are code you run"?
1. Use "MCP servers are code you run" as a reminder to verify the AI output before anyone relies on it.
2. Skip the context so the tool can guess faster
3. Treat the output as private even after sharing it online
4. Use the answer without checking the source
You want to use AI after this lesson. What is the safest next step?
1. Act immediately because the AI answer is written clearly
2. Use AI for drafting and comparison, but verify before publishing or relying on it.
3. Hide uncertainty so the final answer looks cleaner
4. Use private or sensitive details before checking permission
How should AI output about MCP be treated?
1. As proof that no other source is needed
2. As a replacement for context, consent, or expert review
3. As a draft or helper output that still needs human judgment and verification
4. As something that becomes correct when it sounds confident
Name one way to verify an AI answer about MCP.
Which action would help you apply "MCP Deep Dive: The USB-C for AI Tools" responsibly?
1. Use the tool to avoid thinking through the tradeoff
2. Keep going even if the output conflicts with a trusted source
3. Treat the AI output as automatically correct
4. Resources — readable data URIs (file://, db://, custom://).

← Back to interactive lesson

Tendril · Creators · Agentic AI

MCP Deep Dive: The USB-C for AI Tools

Model Context Protocol is the most important open standard in agents. One protocol, 1,200+ servers, and your agent can plug into almost any system. Here's how it actually works.

55 min · Reviewed 2026

Why MCP exists

The architecture

Piece	Role
Host	The app the user interacts with (Claude Desktop, Claude Code, Cursor, OpenClaw).
Client	The host's MCP client instance, one per connected server.
Server	A separate process exposing tools/resources/prompts.
Transport	stdio (spawned subprocess) or HTTP/SSE (remote service).
Protocol	JSON-RPC 2.0. Typed message schemas.

What a server exposes

Tools — function-like actions (call with args, get a result).
Resources — readable data URIs (file://, db://, custom://).
Prompts — reusable prompt templates the host can surface.
Sampling (optional) — server can ask host's model for completions.
Roots — URI hints about where the server operates.

A real MCP config

{ "mcpServers": { "filesystem": { "command": "npx", "args": [ "-y", "@modelcontextprotocol/server-filesystem", "/Users/you/projects" ] }, "github": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-github"], "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_" } }, "supabase": { "command": "npx", "args": [ "-y", "@supabase/mcp-server-supabase@latest", "--project-ref", "your-project-ref" ], "env": { "SUPABASE_ACCESS_TOKEN": "sbp_" } }, "notion": { "url": "https://mcp.notion.com/sse", "transport": "sse", "headers": {"Authorization": "Bearer ntn_"} } } }Claude Desktop / Claude Code MCP config. Four real servers in the April 2026 registry. Drop this into ~/.claude/claude_desktop_config.json and restart.

Writing your own MCP server

// A tiny MCP server in TypeScript (@modelcontextprotocol/sdk) import { Server } from "@modelcontextprotocol/sdk/server/index.js"; import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js"; import { CallToolRequestSchema, ListToolsRequestSchema, } from "@modelcontextprotocol/sdk/types.js"; const server = new Server( { name: "my-server", version: "0.1.0" }, { capabilities: { tools: {} } } ); server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: [{ name: "greet", description: "Say hello to a person.", inputSchema: { type: "object", properties: { name: { type: "string" } }, required: ["name"], }, }], })); server.setRequestHandler(CallToolRequestSchema, async (req) => { if (req.params.name === "greet") { const name = (req.params.arguments as any)?.name ? "friend"; return { content: [{ type: "text", text: `Hello, ${name}!` }] }; } throw new Error("Unknown tool"); }); const transport = new StdioServerTransport(); await server.connect(transport);A complete, minimal MCP server. Registers one tool, speaks stdio. About 30 lines.

Servers worth knowing (April 2026)

modelcontextprotocol/server-filesystem — scoped file access.
modelcontextprotocol/server-github — issues, PRs, repos.
modelcontextprotocol/server-postgres — SQL over any Postgres.
Supabase, Neon, Vercel, Stripe — all ship official first-party MCPs.
Zapier MCP — proxies to 8,000+ Zapier-connected apps.
Notion, Linear, Slack, Google Drive, Calendar — official.
Chroma, Pinecone, Vectara — vector DBs for RAG.
Sentry, Datadog — observability from inside your agent.

Transports

Transport	Use case	Pros	Cons
stdio	Local-only, spawned by host.	Zero network; trivial auth.	One process per client.
SSE / HTTP	Remote or shared server.	Multi-tenant, scales.	Need auth, TLS, ops.
Streamable HTTP (2025+)	Bidirectional over HTTP/2.	Best of both; modern.	Newer, fewer libs.

MCP is the one thing to learn cold. Once you have it, every agent gets cheaper, every tool is reusable, and switching models becomes a config change.

End-of-lesson check

8 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-agentic-mcp-deep-dive-creators

What is the main idea of "MCP Deep Dive: The USB-C for AI Tools"?
1. Model Context Protocol is the most important open standard in agents.
2. Use AI as the final authority for the whole decision
3. Avoid checking the answer once it sounds polished
4. Focus only on speed instead of judgment
Which concept is most central to "MCP Deep Dive: The USB-C for AI Tools"?
1. Model Context Protocol
2. MCP
3. MCP server
4. stdio transport
Which use of AI fits this topic best?
1. Let the AI decide what matters without your review
2. Use the answer before checking whether it fits the situation
3. Tools — function-like actions (call with args, get a result).
4. Treat the AI output as automatically correct
What should a careful learner remember about "MCP servers are code you run"?
1. Use "MCP servers are code you run" as a reminder to verify the AI output before anyone relies on it.
2. Skip the context so the tool can guess faster
3. Treat the output as private even after sharing it online
4. Use the answer without checking the source
You want to use AI after this lesson. What is the safest next step?
1. Act immediately because the AI answer is written clearly
2. Use AI for drafting and comparison, but verify before publishing or relying on it.
3. Hide uncertainty so the final answer looks cleaner
4. Use private or sensitive details before checking permission
How should AI output about MCP be treated?
1. As proof that no other source is needed
2. As a replacement for context, consent, or expert review
3. As a draft or helper output that still needs human judgment and verification
4. As something that becomes correct when it sounds confident
Name one way to verify an AI answer about MCP.
Which action would help you apply "MCP Deep Dive: The USB-C for AI Tools" responsibly?
1. Use the tool to avoid thinking through the tradeoff
2. Keep going even if the output conflicts with a trusted source
3. Treat the AI output as automatically correct
4. Resources — readable data URIs (file://, db://, custom://).

← Back to interactive lesson