Your App Should Ship an MCP Server
The article argues that every app that stores user data should ship a built-in MCP (Model Context Protocol) server, allowing AI tools to directly query and interact with that data. The author suggests a pattern of implementing MCP server functionality early in development and provides examples of how to add capabilities like tools, resources, and prompts.
Background
- MCP (Model Context Protocol) is an open standard created by Anthropic that lets AI apps (like coding assistants) talk directly to external tools, APIs, or data sources — similar to how USB-C lets devices connect to peripherals.
- This article argues that developers building web apps (SaaS, databases, etc.) should ship a built-in MCP server alongside their product, so AI agents can natively read/write data from it without custom integration work.
- The analogy: just as apps used to ship a REST API or SDK for developers, they should now ship an MCP server for AI agents — treating AI as a first-class "user" of the app.
- Prior context: MCP was announced in late 2024 and has been rapidly adopted by companies like Sourcegraph, Replit, and Codeium; it competes with other agent-to-tool protocols but is gaining momentum thanks to Anthropic's push and open governance.
- Why this matters: if this pattern takes hold, every SaaS product will need to think about how AI agents interact with their data — not just through a UI or API, but through a standardized agent protocol.