One protocol, taught properly, by someone who ships it in production

I'm an enterprise AI and process-automation architect. By day I connect agentic systems to real tools and data — which in 2026 means MCP — in environments where security reviews, audit trails, and change control are a way of life. This site is where I write the MCP guidance I wish existed: for anyone building with the protocol — students, hobbyists, startup builders, and enterprise teams alike. The production experience is a bonus you'll feel in the depth, not a prerequisite for reading.

Why a whole site for one protocol? Because the internet is full of MCP hello-worlds and nearly empty after step 5. The transports question, the Windows failures, the OAuth maze, deployment, security hardening, token cost — that's where builders get stuck, and that's what this site is built around.

Three promises, so you know what you're getting:

• Everything is evergreen. No launch hot takes, no "top 10 MCP servers this week." Claims are pinned to spec revisions and SDK versions, and revisited when the spec moves.
• Code is written to run. Tutorials follow the official SDK idioms exactly, and troubleshooting sections contain real error strings — the ones you'll actually hit, including on Windows and ARM64.
• The production lens is real, and generic. Governance, gateways, and threat models drawn from large-scale enterprise practice — always genericized, never anyone's internals.

Where to start

New to MCP? Start with what MCP actually is, then build your first server. Choosing between approaches? Compare & Decide. Responsible for rolling MCP out at work? Production & Governance is written for you.