WordPress MCP Server

WordPress MCP server enabling AI agents to interact with WordPress sites — creating, reading, updating, and deleting posts and pages, managing media, handling comments, accessing user and taxonomy data, and integrating WordPress content management into agent-driven content creation and publishing workflows.

Evaluated Mar 07, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Content Management wordpress cms content-management mcp-server rest-api blogging automattic
⚙ Agent Friendliness
79
/ 100
Can an agent use this?
🔒 Security
82
/ 100
Is it safe for agents?
⚡ Reliability
78
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
80
Documentation
82
Error Messages
78
Auth Simplicity
80
Rate Limits
75

🔒 Security

TLS Enforcement
92
Auth Strength
80
Scope Granularity
78
Dep. Hygiene
80
Secret Handling
82

Application Password auth. HTTPS required. Official Automattic MCP. Use editor user not admin. Store password in env var.

⚡ Reliability

Uptime/SLA
78
Version Stability
80
Breaking Changes
78
Error Recovery
75
AF Security Reliability

Best When

An agent needs to create or manage content on a WordPress site — for AI-assisted blogging, automated content pipelines, or WordPress site administration.

Avoid When

You use a different CMS platform, or your WordPress site doesn't have REST API access enabled.

Use Cases

  • Drafting and publishing blog posts from AI content creation agents
  • Managing WordPress media library from content management agents
  • Automating content updates and revisions from editorial workflow agents
  • Retrieving and analyzing post performance from analytics agents
  • Managing WordPress comments and moderation from community agents
  • Bulk content operations across WordPress sites from automation agents

Not For

  • Non-WordPress CMS platforms (Drupal, Ghost, Contentful require different MCPs)
  • WordPress.com free tier (requires Business plan or self-hosted for API access)
  • Teams without WordPress REST API or Application Password configured

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
Yes

Authentication

Methods: application_password oauth2
OAuth: Yes Scopes: Yes

WordPress Application Passwords (recommended for self-hosted) or OAuth2 via WordPress.com for hosted. Application Passwords available in WordPress 5.6+. Generate from WordPress admin under user profile.

Pricing

Model: freemium
Free tier: Yes
Requires CC: No

WordPress software is free and open source. Self-hosted WordPress has full API access. WordPress.com requires Business plan ($25/month) for REST API. MCP server is free open source from Automattic.

Agent Metadata

Pagination
cursor
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • Application Password must be generated per-user in WordPress admin dashboard
  • WordPress REST API must be enabled (enabled by default in WP 5.6+)
  • Permalink structure must be enabled (non-plain) for REST API to work properly
  • WordPress.com vs self-hosted have different authentication flows
  • Published posts are immediately public — use draft status for staged content
  • Automattic-maintained MCP — higher quality than average community MCP

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for WordPress MCP Server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-07.

6228
Packages Evaluated
26150
Need Evaluation
173
Need Re-evaluation
Community Powered