A
licenseC
qualityD
maintenanceEnables AI to manage WordPress sites with 190+ tools for complete control over content, themes, plugins, files, and more.
100
36 npm
MIT
WordPress MCP Server
by RaheesAhmed
Related Servers
Alternatives to WordPress MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with WordPress websites through structured tools, supporting posts, pages, media, users, categories, tags, plugins, themes, menus, and WooCommerce with secure authentication.14 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage WordPress sites via ~74 capabilities including content, media, plugins, themes, and more.-
- FlicenseNot gradedqualityDmaintenanceEnables AI clients to manage WordPress and WooCommerce sites with over 194 tools for content, users, security, performance, and e-commerce operations.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage WordPress sites through the WordPress REST API, supporting content, media, users, settings, and Elementor management with safety policies for production use.MIT
- AlicenseNot gradedqualityFmaintenanceEnables 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
TDQS
C2.7/5.0
Scored across 190 tools
Disambiguation3/5
Many tools have clear resource-action separation (posts, users, themes, plugins), but there are overlapping pairs like wordpress_get_posts vs wordpress_search_posts, wordpress_get_plugins vs wordpress_get_plugins_detailed, and wordpress_get_site_info vs wordpress_get_site_health that could cause selection ambiguity. With 190 tools, the sheer volume increases the chance of picking a near-duplicate.
Naming Consistency4/5
Most tools follow a consistent wordpress_<verb>_<noun> pattern (create_post, get_posts, delete_user). However, there are inconsistencies: wordpress_wc_is_active vs wordpress_get_plugins (non-verb prefix), wordpress_theme_exists vs get_ forms, and wordpress_run_cron vs wordpress_list_cron_jobs. These are minor deviations from an otherwise uniform convention.
Tool Count2/5
190 tools is excessive for a single MCP server. The scope spans core content, themes, plugins, files, users, WooCommerce, SEO, performance, security, and database operations, creating a monolithic surface that is difficult to navigate.
Completeness4/5
The tool surface is incredibly comprehensive, covering posts, pages, media, users, taxonomies, comments, themes, plugins, menus, widgets, WooCommerce, and system maintenance. Gaps are minor (e.g., no comment spam moderation, no specific user registration tool), but most obvious workflows are represented.
Maintenance
ActivityInactive
ResponsivenessNo issues