Category

A WordPress MCP plugin for real site operations.

Connect Claude, ChatGPT, Cursor, Codex, and other MCP clients to a self-hosted WordPress site with scoped access, read-first safety, and Elementor-aware workflows.

What it does

Turn WordPress into an agent-ready operating surface.

Scoped MCP endpoint

Expose WordPress tools through an authenticated MCP route instead of handing an AI broad admin access.

Content and site operations

Draft, update, inspect, and organize posts, pages, media, menus, metadata, and site state.

Elementor-aware workflows

Work with real Elementor structures, validate layouts, and keep the page-builder path distinct from blog/editorial flows.

SEO and launch work

Use AI clients to inspect metadata, page flow, internal links, and conversion readiness before traffic arrives.

Why MCPWP

Built around the first successful MCP call.

The conversion is not just installing a ZIP. It is connecting a scoped key, asking the AI client to inspect the site, and proving it can operate safely before writes are enabled.

Read-only-first setup pathScoped API keysDynamic tool discoveryElementor and Gutenberg separationGitHub-visible issue tracking for blockers
FAQ

Questions buyers ask before connecting AI to WordPress.

Is MCPWP only for Claude?

No. It is built for MCP-capable clients, including Claude, ChatGPT, Cursor, Codex, and other agents that can call remote MCP tools.

Does it replace WordPress admin?

No. It gives AI clients a controlled operational layer while WordPress remains the source of truth.

Should AI write to production immediately?

No. Start with read-only inspection, verify site state, then enable scoped write access only where the workflow requires it.