Cursor

Connect Cursor to WordPress with MCPWP.

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.

Developer workflow

Bridge local code work and live WordPress context.

Inspect site state

List active capabilities, pages, plugins, and relevant content before implementing changes.

Coordinate with Elementor

Avoid treating builder pages like plain HTML. Use MCP-aware inspection and validation.

Report product blockers

When an MCPWP tool fails or is missing, open a GitHub issue instead of hiding the failure.

Keep access scoped

Use the minimum key scope that lets the agent complete the task.

Client config

Use the MCPWP endpoint and scoped key.

"mcpwp": {
  "url": "https://your-site.com/wp-json/site-pilot-ai/v1/mcp",
  "headers": { "X-API-Key": "spai_your_scoped_key" }
}
FAQ

Questions buyers ask before connecting AI to WordPress.

Is this only for Cursor?

No. The same workflow applies to Codex, Claude Code, Windsurf, Cline, and other coding agents that support MCP.

Should coding agents change production?

Inspect production carefully, but use staging or human review before risky write operations.