VORCL
← All courses
Intermediate · 7 lessons

MCP in Practice: Building Model Context Protocol Servers

The full MCP engineer path: from the N×M integration problem and JSON-RPC frames to your own server on the TypeScript SDK — with auth, secrets, Inspector debugging, and connections to Claude, Cursor, and VS Code.

Start →
  1. 01Why MCP Exists: the N×M Integration ProblemWhy every pair of AI app and data source used to need its own connector, and how MCP turns N×M integrations into N+M.35 min
  2. 02Protocol Anatomy: Tools, Resources, Prompts, and JSON-RPCJSON-RPC 2.0 frames, the session lifecycle, the three server primitives, and the two transports — stdio and Streamable HTTP.50 min
  3. 03Your First Server with the TypeScript SDKBuild a working MCP server from scratch: McpServer, registerTool with zod schemas, resources, prompts, and StdioServerTransport.60 min
  4. 04Auth, Secrets, and Permission ScopingHow not to ship a security hole: secrets in the environment, OAuth 2.1 for HTTP, tool annotations, and least privilege.50 min
  5. 05Debugging with MCP InspectorInspector interactive and CLI modes, reading protocol frames, common stdio server failures, and stderr logging discipline.40 min
  6. 06Publishing and Connecting to Claude, Cursor, and VS CodePackage an npm binary with bin and shebang, connect to Claude Code and Claude Desktop, Cursor, and VS Code, deploy a remote HTTP variant.45 min
  7. 07Capstone: an MCP Server for Your Product APIDesign the tool surface around user tasks, wrap a real API with error handling, and ship the server against a production checklist.60 min

Sources

MCP in Practice: Building Model Context Protocol Servers · VORCL