Developer agents are strongest when they can inspect the real site. MCPWP gives Cursor a scoped MCP surface for WordPress context and site-operation workflows.
List active capabilities, pages, plugins, and relevant content before implementing changes.
Avoid treating builder pages like plain HTML. Use MCP-aware inspection and validation.
When an MCPWP tool fails or is missing, open a GitHub issue instead of hiding the failure.
Use the minimum key scope that lets the agent complete the task.
"mcpwp": {
"url": "https://your-site.com/wp-json/site-pilot-ai/v1/mcp",
"headers": { "X-API-Key": "spai_your_scoped_key" }
}No. The same workflow applies to Codex, Claude Code, Windsurf, Cline, and other coding agents that support MCP.
Inspect production carefully, but use staging or human review before risky write operations.