I require that an API of consequence exposes a Model Context Protocol server so that agents can discover its capabilities and invoke them through a standard, well-understood interface rather than a bespoke one we have to explain over and over. The MCP server should be a governed, documented artifact that maps cleanly to the underlying API, not a science project bolted on the side. I hold this position because MCP is quickly becoming the way agents connect to the tools they use, and providers who supply a clean server become reusable across a whole ecosystem while everyone else gets wrapped in someone else's brittle glue code. Every production API should treat its MCP server as part of the product.
MCP Server Provided
Rules
APIs.json MCP Server Info
APIs should declare an MCP server so agents and MCP-aware tooling can discover and connect to the API through the Model Context Protocol. Declaring a property of type MCPServer in the APIs.json pro...
Strategies
APIs Expose an MCP Server
I want our APIs to meet agents where they already are by exposing a Model Context Protocol server that turns our operations into tools an agent can pick up and use without a custom integration for ...
Experiences
Agent Experience
Agent experience is developer experience for machines. As AI agents become first-class consumers of APIs, the experience they have discovering, understanding, authenticating, and calling an API mat...
Integration
Integrating digital resources and capabilities into other systems using HTTP APIs is commonplace in any enterprise. However, the experience, skills, time, and cost required for successful integrati...
Lifecycle
tune Management Production
Management is the day-to-day operation of an API in production. Plans, rate limits, keys, and access all get administered here, usually through a gateway. Solid management is what lets me offer an ...
