wpxmcp
Related Servers
Alternatives to wpxmcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server that gives AI tools full WordPress management via WP-CLI. 30+ tools for themes, plugins, posts, menus, users, database, scaffolding, and cache. Works locally or over SSH.3415 npm6MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Claude Code and Cursor to control a WordPress site via 58 abilities over stdio (WP-CLI) or HTTP, self-contained and cloud-free.44GPL 2.0
- AlicenseNot gradedqualityCmaintenanceEnables 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
- FlicenseNot gradedqualityFmaintenanceEnables AI assistants to interact with a WordPress site, allowing content and taxonomy management (list, create, update, delete) through 17 MCP tools.2-
- AlicenseNot gradedqualityBmaintenanceExposes a WordPress site as MCP tools so AI agents can write content, build Elementor pages, manage media, menus and comments, and edit ACF, Meta Box and SEO fields. Every write is previewed with a diff, snapshotted, verified by reading the site back, logged, and reversible.3GPL 2.0
- AlicenseCqualityBmaintenanceEnables AI-powered WordPress management via MCP, with 158 tools for posts, pages, media, plugins, themes, users, comments, and more, plus token-optimized responses.3371,015 npm4MIT
TDQS
Scored across 150 tools
Several tools are explicit duplicates or near-duplicates: create_plugin/install_plugin, edit_media/update_media, get_template_for_url/profile_url, and get_content_by_slug/find_content_by_url. Even with strong descriptions, the large number of overlapping retrieval, diagnostic, and plugin-settings tools makes reliable tool selection difficult.
Most tools follow a clean verb_noun pattern such as list_*, get_*, create_*, update_*, and delete_*, but there are clear exceptions like site_info, fleet_report, content_inventory, content_calendar, code_snippet, and rest_api. The mixed conventions are still readable, but the pattern is not uniform.
With 150 tools, this server is far beyond what an agent can reliably navigate; 50+ is an extreme mismatch per the calibration. Many audit, report, registry, and SEO functions could be consolidated into fewer, grouped tools.
The tool surface is exceptionally broad: content, media, taxonomies, users, comments, plugins, themes, menus, widgets, settings, SEO, audits, and escape-hatch tools like REST, WP-CLI, and SQL are all covered. The most notable gap is the absence of dedicated update operations for plugins, themes, and core updates, which are only reachable indirectly.