What it is
The Model Context Protocol is the emerging standard for exposing tools to agents. An MCP server declares a set of operations with typed inputs, and the agent calls them.
Crucially, you choose which operations exist. It is not general access to your API — it is a deliberately narrow surface you define and can revoke.
Why an agent cares
This is the top of the ladder. Readable means you can be described; actionable means you can be used; MCP means you can be operated.
It also inverts the integration question. Instead of asking customers to build against you, you ship a server and every MCP-capable agent can already use it.
How to fix it
Don't port your whole API. Pick the three to five operations that represent real value and wrap those.
- Choose operations a user would plausibly delegate.
- Serve the server over streamable HTTP at
/mcp. - Require auth for anything that writes, and log every call.
How we test it
We probe /mcp and /.well-known/mcp.json and require a genuine protocol signal in the response — a bare 405 is far too common on ordinary routes to count as evidence.