Why MCP
If you've spent any time with AI tools in the last year, you've probably seen the acronym MCP show up in places it didn't used to. Model Context Protocol. It's the reason Paper Route can connect to Claude Code, Claude.ai, ChatGPT, Cursor, and Codex with one plugin and one server. This page explains what MCP is, what problem it solves, and why we built Paper Route on it instead of doing what most WordPress AI tools have done so far.
The problem MCP solves
Before MCP existed, if you wanted to connect an AI tool to an external service, you had two options.
Option one was that the AI tool's vendor built a custom integration. Anthropic built tool use APIs, OpenAI built function calling, both worked roughly the same way but with different shapes. If you wanted to support both, you wrote your integration twice. If a third tool came along, you wrote it a third time. Each new tool meant another integration, another shape, another set of credentials, another way of describing the same capabilities.
Option two was that the service exposed a public API and the user had to wire it up themselves through whatever bridge their AI tool provided. This worked for power users but created a huge operational burden. Every user had to manage their own tokens, their own rate limits, their own field mappings. Every AI tool had a slightly different way of describing tool calls, so the same service ended up looking different in each one.
This is the classic M times N problem. M services times N AI tools equals M-times-N integrations. The total amount of work to connect everything to everything grew quadratically. Most things just didn't get connected.
MCP is the standard that turns the M-times-N problem into M plus N. Each service implements the protocol once. Each AI tool implements the protocol once. They connect through the standard. No custom integration per pair.
What MCP actually is
The Model Context Protocol is a specification for how AI tools talk to external services. It defines three kinds of things a service can expose to an AI tool:
- Tools are actions the AI tool can call. Things like "create a WordPress post" or "read a file." Tools take structured arguments and return structured responses.
- Resources are pieces of data the AI tool can read. Things like a list of available sites, or the contents of a file. Resources are passive; the agent decides when to fetch them.
- Prompts are reusable templates the AI tool can invoke. Less commonly used, but worth knowing about.
The protocol also defines how the AI tool connects to the service in the first place. There's an authentication handshake (Paper Route uses OAuth 2.1 with PKCE for this), an initialization step where the service tells the agent what tools and resources are available, and then a series of tool calls and responses for the rest of the session.
MCP is transport-agnostic. The original implementation used standard input and output for local servers. The version Paper Route uses is the streamable HTTP transport, which lets remote services like ours expose MCP endpoints over the public internet. From the agent's point of view, the transport is invisible. It just sees a list of tools it can call.
Why Paper Route bet on it
When we started building Paper Route, the choice was between writing custom integrations for each AI tool we wanted to support or betting on MCP. We bet on MCP for three reasons.
The protocol is genuinely universal. As of this writing, MCP works across Claude (both Claude.ai and Claude Code), ChatGPT, Cursor, Codex, and a growing list of other tools. Building a single MCP server means Paper Route can be used from any of them, today, without writing a single line of tool-specific code. The "Works with" claim on the Paper Route homepage is true precisely because MCP is the universal protocol.
The standard is moving in our direction. WordPress Core itself is standardizing on something called the Abilities API, which is a way for plugins to declare their capabilities in a structured format. The official WordPress mcp-adapter automatically translates abilities into MCP tools. In other words, the WordPress ecosystem is being designed from the ground up to be MCP-accessible. Paper Route is positioned to be the layer that adds operational context on top of whatever the abilities ecosystem produces, rather than having to compete with it.
The architecture lets users bring their own AI. This is the most important reason and it's easy to miss. Because Paper Route is an MCP server and not an AI product, the AI doing the work lives in the user's tool of choice. Their Claude subscription, their ChatGPT account, their Cursor seat. We're not paying for inference. We're not training models. We're not running an LLM on our servers. We're the proxy between the agent the user already has and the WordPress sites they already manage. This makes Paper Route's unit economics dramatically better than most AI products and lets us offer a generous free tier without bleeding money.
What this means for you
If you're using Paper Route, MCP is mostly invisible. You install the WordPress plugin on your sites, you connect your AI tool to Paper Route through its MCP connector flow, and from that point forward you're just having a conversation. You don't see the protocol. You don't see the tool definitions. You don't see the OAuth handshake. You see your AI tool helping you manage your WordPress sites.
The reason this matters even though you don't see it is that you're not locked in. If you want to switch from Claude Code to Cursor next month, your Paper Route setup keeps working. If a new AI tool comes out next year that supports MCP, it'll work with your existing Paper Route install on day one. The protocol is the abstraction layer that protects your investment in setting things up.
That portability is a relatively new thing in the AI tools space. A year ago, every AI integration was a one-way street into one vendor's ecosystem. MCP changed that. Paper Route is built on top of that change.
Where MCP is going
A few things worth knowing about where the protocol is headed.
The Abilities API integration with WordPress Core is the biggest single thing on the horizon for the WordPress side. As more plugins ship abilities, the universe of MCP tools available on a WordPress site grows automatically. Yoast, RankMath, WooCommerce, all the major plugins have a path to becoming MCP-accessible without anyone writing custom MCP code for them. That's a step change for the ecosystem.
The protocol itself is also evolving. New transports are being added, the resource and prompt primitives are getting more attention, and the authentication story is getting more sophisticated. Paper Route tracks the protocol's development and updates as the spec evolves.
Where to go next
If you want to understand the rest of how Paper Route works, the two most useful pages are: