WordPress MCP Server
WordPress MCP server enabling AI agents to interact with WordPress sites via the WP REST API — reading and creating posts and pages, managing categories and tags, querying media library, handling comments, and integrating WordPress's CMS capabilities into agent-driven content creation, site management, and publishing automation workflows.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
HTTPS recommended. WordPress Application Passwords for auth. Role-based access. Community MCP server. Always use HTTPS. Use Application Passwords. Restrict user to minimum required role.
⚡ Reliability
Best When
An agent needs to create or manage WordPress content — for AI-assisted blogging, automated publishing, or WordPress site management.
Avoid When
You're using Ghost, Contentful, or another CMS — or if you need deep WP admin operations beyond content (themes, plugins, settings).
Use Cases
- • Creating and publishing WordPress posts from content generation agents
- • Managing categories and tags from content organization agents
- • Querying post library and metadata from editorial workflow agents
- • Uploading and managing media files from media management agents
- • Moderating comments from community management agents
- • Generating site content audits from SEO and content strategy agents
Not For
- • Teams using Ghost, Contentful, or other CMSs (use their specific MCPs)
- • WordPress.com hosted sites with restricted API access
- • Teams needing WordPress plugin development (use WP CLI or direct PHP)
Interface
Authentication
WordPress Application Passwords (WP 5.6+) for API auth — username + app password. JWT plugins also common. Basic auth available but not recommended. OAuth via plugins (WordPress.com OAuth for hosted). Author/Editor/Admin roles control access.
Pricing
WordPress.org is free and open source. Self-hosting costs vary. WordPress.com offers free and paid tiers. Community MCP server is open source and free.
Agent Metadata
Known Gotchas
- ⚠ WordPress Application Passwords require WP 5.6+ and must be enabled in admin
- ⚠ REST API may be disabled by security plugins — agents must verify API is accessible
- ⚠ WordPress version affects API capabilities — features differ between WP 5.x and 6.x
- ⚠ Custom post types and fields (ACF) may not be exposed by default REST API
- ⚠ Gutenberg (block editor) content stored as block HTML — not plain text
- ⚠ Community MCP server — may not support WooCommerce or advanced plugin APIs
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for WordPress MCP Server.
Scores are editorial opinions as of 2026-03-06.