Zinn® Cache: connect an AI agent (MCP)

Zinn® Cache makes your WordPress site an MCP server: an AI app such as Claude, Cursor or VS Code can read and change Zinn® Cache's content and settings through it, signed in as you.

Before you start

1. WordPress 6.9 or newer. In Zinn® Cache's settings, Allow AI agents (MCP) is on by default.
2. In wp-admin open Users → Profile → Application Passwords, add one named after your AI

app, and copy it (it is shown once). Your connection address is https://your-site/wp-json/zinn-cache/v1/mcp.

Claude Desktop and Cursor

Settings → Developer → Edit Config (Claude Desktop) or .cursor/mcp.json (Cursor):

{"mcpServers": {"zinn-cache": {"command": "npx", "args": ["-y", "@automattic/mcp-wordpress-remote@latest"], "env": {"WP_API_URL": "https://your-site/wp-json/zinn-cache/v1/mcp", "WP_API_USERNAME": "your-username", "WP_API_PASSWORD": "your-application-password"}}}}

VS Code

.vscode/mcp.json uses servers instead of mcpServers, with "type": "stdio" added.

Claude Code

claude mcp add zinn-cache -e WP_API_URL=https://your-site/wp-json/zinn-cache/v1/mcp -e WP_API_USERNAME=your-username -e WP_API_PASSWORD=your-application-password -- npx -y @automattic/mcp-wordpress-remote@latest

Other apps

Any app that runs MCP servers can use the same command; one that connects to remote servers with a header can call the address directly with your username and application password. On the server itself: wp mcp-adapter serve --server=zinn-cache --user=<login>. ChatGPT cannot connect yet: it signs in to MCP servers only by OAuth, which an application password is not.

Safety

Every ability checks the WordPress permission it names for the exact page or post, so an agent can never do more than the user it signs in as; visitors and subscribers are always refused. Revoke the application password, or switch Allow AI agents (MCP) off, to stop it at once.

Step-by-step guide: https://zinndigital.com/wordpress-plugins/zinn-cache/mcp