1. Overview
Cursor exposes MCP via its .cursor/mcp.json config — point it at your server and code + content workflows live side by side.
2. Install Cursor + MCP config
.cursor/mcp.json json
{
"mcpServers": {
"wp": {
"command": "node",
"args": ["./mcp-server/dist/server.js"],
"env": { "WP_URL": "http://localhost:8080", "WP_AUTH": "${WP_AUTH}" }
}
}
}3. Code-first workflows
Ask the Cursor agent: "Add a new tool that bulk-updates post tags, then test it against the local site." It writes the code AND runs it through MCP.
4. Inline edits & previews
Use Cursor's inline diff view to review tool source + the call's effect side by side before approval.
5. Tips & gotchas
Restart Cursor after editing mcp.json. Stdio servers don't hot-reload. Watch the MCP panel for spawn errors.