MCP WordPress Server
Related Servers
Alternatives to MCP WordPress Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to directly manage WordPress sites via natural language, including posts, pages, categories, tags, media, and multiple site support.MIT
- AlicenseBqualityCmaintenanceConnects Claude to WordPress sites through the REST API, enabling AI-assisted content creation, publishing, media management, user administration, and site maintenance tasks through natural language.47198 npm23MIT
- AlicenseBqualityDmaintenanceConnects Claude Desktop to WordPress sites to manage Elementor pages, Gutenberg content, and Rank Math SEO settings. It enables users to create styled pages, manage section layouts, and perform content updates through natural language commands.398 npmGPL 2.0
- AlicenseAqualityDmaintenanceEnables direct interaction with WordPress sites via Claude using the REST API, allowing reading, creating, updating, and deleting content securely with application passwords.20MIT
- AlicenseNot gradedqualityDmaintenanceEnables managing self-hosted WordPress sites via AI assistants, providing 69 tools for content creation, SEO, media, comments, and site management through the MCP protocol.3MIT
- AlicenseCqualityBmaintenanceEnables AI-powered WordPress management via MCP, with 158 tools for posts, pages, media, plugins, themes, users, comments, and more, plus token-optimized responses.2771,113 npm3MIT
TDQS
Scored across 27 tools
Most tools clearly target distinct resources such as comments, media, posts, categories, users, and settings. However, there is notable overlap among SEO tools: wp_seo_site_audit, wp_seo_analyze_content, wp_seo_get_live_data, and wp_seo_test_integration have fuzzy boundaries that could cause misselection.
The naming pattern is generally consistent with wp_ + verb + noun, e.g., wp_get_media, wp_delete_post, wp_create_user. SEO tools follow a readable wp_seo_ prefix pattern, though a few like wp_seo_site_audit use a noun phrase rather than a clear verb_action form.
At 27 tools, the server is above the comfortable range and feels bloated. Roughly a third of the tools are SEO-specific while core WordPress content operations are sparse, making the count high without corresponding breadth of fundamental functionality.
The core WordPress lifecycle has significant gaps: there is no post creation or editing, no media deletion/update, no user listing/updating, no comment moderation, and category support is limited to get/update. The SEO toolset is broad but does not compensate for these missing fundamental operations.