Cursor

Registers exactly as Claude Code does, because its config file uses the same shape.

Connect it

In the app, register with Cursor. It writes a single Multiagentry entry into ~/.cursor/mcp.json, under mcpServers, in the same JSON shape Claude Code uses.

Restart Cursor and the tools appear.

What you get

The same tools, the same abilities, the same WordPress handling. There is no reduced feature set for Cursor: it is the same MCP server answering, and the app does not know or care which agent is on the other end beyond naming it in the ledger.

What has and has not been proven

Cursor is not the path this was developed against. Registration is verified: the file is written correctly and the server is reachable. But it has not had the hours of live editing that Claude Code has. If something behaves oddly, it is worth trying the same request through Claude Code to find out whether the problem is the agent or the app.

We would rather say that than let you discover it on a client site. The app shows the same thing, per agent, on its own agent screen.

If the tools do not appear

Check Troubleshooting. The usual cause is that Cursor was running when the entry was written, and it only reads that file at startup.