ProjectBuild a Permission-Aware Knowledge Hub as an MCP Server: the explanation · Module 3: MCP in depth: protocol, transports and the SDK · part 5 of 22
Part 5 · Module 3: MCP in depth: protocol, transports and the SDK
Module 3: MCP in depth: protocol, transports and the SDK
22 min read·
About 50 minutes · Needs: Module 2 (the solution) · Code: research/spike_mcp_server.py, server/wayfinder/mcp/server.py, server/wayfinder/main.py, server/wayfinder/mcp/stdio.py, server/tests/test_mcp.py
Where this fits
This module (highlighted) opens the MCP layer and the stdio bridge, the protocol that Claude Code, whose model is drawn amber, and MCP Inspector use to talk to Wayfinder.
Module 2 (the solution) said that AI clients reach Wayfinder "through MCP". This module opens that box: what the protocol is, what travels on the wire, how a connection starts and ends, the two ways to carry it, the official Python SDK Wayfinder is built on, and the two protocol eras the code supports. You need it to debug a client that will not connect, and to understand why the server runs as a single process.
The rest of this project is yours to keep
This project is bought on its own, once, and stays readable afterwards, including the parts added to it later.