17. Connecting Systems with MCP (The Stateless Wire Protocol)
Show notes
In Episode 17 of Beyond Prompting, author Sho Shimoda breaks down the Model Context Protocol (MCP)—the open standard that connects Claude Code to external systems like ticket trackers, wikis, and databases. We explore how MCP replaces custom one-off integrations with a universal wire protocol, and examine the major 2026 specification revision. In this episode, we cover:
- The Three Primitives: Distinguishing between Tools (model-controlled functions), Resources (application-controlled context and documents), and Prompts (user-controlled command templates).
- The July 2026 Protocol Shift: How the updated MCP specification (2026-07-28) eliminated connection handshakes (initialize) and persistent session IDs (Mcp-Session-Id) in favor of stateless, standalone HTTP POST requests carrying capabilities in _meta.
- Configuring .mcp.json: Setting up stdio and HTTP transports across local (~/.claude.json), project (.mcp.json), and user scopes, and leveraging tool search (ENABLE_TOOL_SEARCH) to prevent schema overload.
- Security & Host Access: Why stdio MCP servers run as unconstrained processes on the host machine outside the shell sandbox, and what security teams must verify before connecting third-party servers.
(Note for listeners: This episode covers Chapter 17 of Sho Shimoda's book RUNNING CLAUDE: The Operator’s Guide to Chat, Cowork and Claude Code, available on Amazon as the successor book to Master Claude: Chat, Cowork and Code).