MCPress connects your WordPress site to the AI chat clients you already use — Cursor, Claude Code, Grok, and claude.ai — over the Model Context Protocol (MCP), the open standard that lets an AI assistant discover and call tools on an external system.
Built on WordPress Core’s Abilities API (6.9+), MCPress registers a full set of content-management tools and bridges them to MCP using the official mcp-adapter package, bundled with the plugin — no separate dependency to install, no external service to configure.
What it manages
Content — posts, pages, and any custom post type: create, read, update, delete, publish, draft, or schedule
Taxonomy — categories, tags, and custom taxonomies: browse, assign, create
Comments — browse, moderate, reply, permanently delete
Revisions — browse revision history and restore a prior revision
SEO / Meta — read and write SEO fields through one interface that normalizes Yoast SEO and RankMath
Safe mode — an opt-in, site-level policy that blocks destructive actions (permanent delete, revision restore) regardless of the connecting user’s role, for teams that want an extra guardrail before an AI agent gets full administrator reach
How it authenticates
MCPress uses WordPress’s own built-in Application Passwords — no custom credential store, no third-party account. Every action an AI client takes is bound by the real WordPress capabilities of the user whose Application Password it’s using: an agent connected as an Editor can only do what that Editor could already do in wp-admin. Every mutating action — and every safe-mode block — is recorded to a capped activity log, visible under Tools → MCPress Activity Log.