Ship an MCP server for an existing REST API

Each lesson built one part of an MCP server and tested it on its own: a naive wrapper and its cost, the messages on the wire, tools designed for a model, tests and agent evaluations, resources and confirmations, a remote endpoint behind OAuth, defences against injection, and a release process that doesn't break the agents using it. This project puts them together into one server you could hand to a team: larchmere-desk, in front of the REST API Larchmere's support team already runs.

It uses every module. The protocol and its mental model gives you the baseline to beat and the wire-level understanding to debug with. Designing servers agents use well gives you the tools, the resources and prompts, and the numbers that say the design is better. Running servers in production puts it behind HTTP and OAuth, hardens it, and ships it with a contract you can't break by accident.