The Model Context Protocol (MCP) is how AI apps reach outside data. MazeGraph can act as an MCP server for your site, so an AI app on your computer can answer questions about your content, media, plugins and site health with real data from your site.
You might ask your editor’s assistant “Which posts have not been updated in a year?”, “Which images are missing alt text?” or “Is anything overdue in WP-Cron?”, and it calls MazeGraph’s tools on your site to answer.
What the MCP server can and cannot do
| It can | It cannot |
|---|---|
| Read your site through MazeGraph’s own read-only tools: content, revisions, media, structure, plugins, themes, updates and Site Health. | Change anything. No tool that writes is offered over MCP, and no call can be approved from an outside app. |
| Answer only to an administrator who signs in with a connection password made on the MCP screen. | Be reached by editors, authors or visitors. |
| Follow MazeGraph tool switches, WordPress permissions and policy for every call. | Write to the site. Personal or WooCommerce reads are not permanently excluded, but require an administrator to enable the corresponding tool and the person’s WordPress permission. |
| Record every call in Activity, marked as coming from MCP. | Start a model run or spend your AI provider’s tokens. The outside app uses its own model. |
The server is off by default. Nothing is exposed until an administrator turns it on and creates a connection.
Which apps work
Developer apps that connect to a remote MCP server with a header work today: Claude Code, Cursor, VS Code (Copilot), Claude Desktop, OpenAI Codex CLI, Gemini CLI, Windsurf, OpenCode, and any other app that supports a streamable HTTP server with a custom header. MazeGraph writes the setup text for each one; see Connect an AI app.
Hosted apps such as claude.ai and ChatGPT sign in with OAuth, which MazeGraph does not offer yet.
Two ways to serve it
MazeGraph can answer MCP requests itself, or through the official WordPress MCP Adapter plugin if you have it installed. You choose under Server on the MCP screen; the default picks the adapter when a compatible version (0.7.1 or later) is active and MazeGraph’s own server otherwise. Only one answers at a time, and both go through the same MazeGraph checks.
| Server | Address |
|---|---|
| MazeGraph’s own server | https://example.com/wp-json/maze-graph/v1/mcp |
| The MCP Adapter plugin | https://example.com/wp-json/maze-graph/mcp |
The MCP screen always shows the address in use, so copy it from there.
The available list follows the Tools catalogue. A new install starts with a small recommended set of reads. During the 1.3.0 upgrade, if MazeGraph’s MCP server or the MCP Adapter sharing switch was enabled, any enabled tool from the fourteen-tool former held-back list is switched off once. An administrator can deliberately enable other eligible read tools later. Treat any personal or WooCommerce data returned by an enabled tool as information being shared with the connected app.
MazeGraph’s own server speaks MCP revision 2026-07-28 and the earlier revisions 2025-11-25, 2025-06-18 and 2025-03-26. Through the MCP Adapter, apps that speak only 2025-03-26 cannot connect; choose MazeGraph’s own server if an older app has trouble.
Next steps
- Connect an AI app: turn the server on and set up your first app.
- Tools available over MCP: exactly what a connected app can read.
- MCP security and access: connection passwords, limits, logging and multisite.
- An MCP app cannot connect: fixes for common errors.