MCPWP turns your WordPress site into a Model Context Protocol server, so Claude, Cursor, Codex and other AI clients can safely operate real site workflows in plain English.
Dynamic tool discovery. Role-scoped keys. Human-safe WordPress operations.
You: Build a pricing page from our offer design.AI: I found Elementor, checked reusable parts, and will draft the page safely.Tool: wp_set_elementor → validated → savedResult: A real WordPress page, not a mockup.Edit sections, menus, SEO, media and WooCommerce with scoped access.Works with MCP-capable clients and developer workflows
The assistant speaks natural language. MCPWP translates requests into authenticated, validated WordPress operations with scoped access and an activity trail.
Use Claude, Cursor, Codex or any MCP-compatible client with your site endpoint and API key.
Tools adapt to your active plugins, site setup, role permissions and enabled integrations.
Create pages, edit Elementor, manage SEO, media, menus and commerce workflows with validation.
Instead of promising a fixed count, MCPWP exposes the right tools for each site: what is installed, licensed, enabled and allowed by the key.
Start with the outcome, then move from plan selection to setup, scoped API key creation, and a first working AI-to-WordPress action.
See how your existing site becomes a controllable, auditable tool for AI clients.
Choose which workflows an assistant can use before it touches real site content.
Paste the endpoint and key into your MCP client, then inspect live tools before making changes.
MCPWP can assemble structured Elementor sections from intent: hero, pricing, FAQ, feature grids, CTAs, service pages and other repeatable site patterns.
The differentiator is depth across the site stack: MCP discovery, Elementor, content, SEO, media, menus, commerce, permissions and repeatable workflows.
| Capability | MCPWP | Basic adapter | Manual workflow |
|---|---|---|---|
| Live tool discovery | ✓Site-aware | Limited | No |
| Elementor workflows | ✓Build and edit | Usually no | Manual |
| Scoped API keys | ✓Role controlled | Varies | No |
| SEO/media/menus | ✓Operational layer | Partial | Manual |
| Blueprint patterns | ✓Reusable sections | No | No |
Start with a scoped MCP connection, then expand into advanced builder, commerce, SEO and multi-site workflows as your operation grows.
Get a WordPress site speaking MCP with scoped API keys and auditable access.
Use AI clients for richer site-building and optimization workflows.
Coordinate repeatable AI-assisted workflows across client sites.
The short answer: MCPWP gives assistants a controlled interface. You decide the key, scope and workflows before any operation runs.
It exposes your WordPress site as a Model Context Protocol server so AI clients can discover and call site operations through a secure endpoint.
Use scoped API keys, roles, tool controls and activity logs. Start read-only, inspect tools, then enable only the workflows you need.
No. Elementor is a major workflow, but MCPWP also covers core WordPress content, media, menus, settings and other integrations when available.
Your MCP client calls the endpoint, authenticates with a scoped key, and asks MCPWP to inspect the site and list available tools.
Install the plugin, create a scoped API key, paste the endpoint into your MCP client, and run your first safe site operation.
Endpoint: https://your-site.com/wp-json/site-pilot-ai/v1/mcp Header: X-API-Key: your scoped key First command: "Inspect my WordPress site and list available MCP tools."