A
licenseC
qualityD
maintenanceEnables AI to manage WordPress sites with 190+ tools for complete control over content, themes, plugins, files, and more.
100
20 npm
MIT
MCP Hub
by airano-ir
Related Servers
Alternatives to MCP Hub
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI clients to manage WordPress and WooCommerce sites with over 194 tools for content, users, security, performance, and e-commerce operations.-
- AlicenseCqualityBmaintenanceEnables AI agents to manage WordPress sites with 190+ tools for content management, theme/plugin customization, file system operations, WooCommerce, and complete site control through natural language.10020 npm56MIT
- 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
- FlicenseNot gradedqualityBmaintenanceControls any WordPress site via natural language, offering tools for site health, plugins, posts, SEO, WooCommerce, and more.-
- AlicenseNot gradedqualityDmaintenanceConnects self-hosted WordPress sites to AI assistants for content creation, SEO, media management, and WooCommerce via 163 tools across 33 categories.2MIT
TDQS
C2.9/5.0
Scored across 100 tools
Disambiguation3/5
WordPress tools are largely distinct (posts, pages, media, settings), but several system tools overlap: check_all_projects_health, get_project_health, and get_system_metrics all touch health/metrics. wordpress_audit_hook_status vs wordpress_probe_capabilities and wordpress_probe_upload_limits also blur the line between 'probe' and 'audit' actions.
Naming Consistency3/5
The wordpress_ prefix provides consistency within that domainaine, but the overall set mixes verbs inconsistently (check_all_projects_health, get_project_health, get_system_uptime, probe_upload_limits, audit_hook_status). Generic tools like get_system_metrics and get_project_health use divergent naming from the rest.
Tool Count2/5
100 tools is excessive for a single MCP server and creates a heavy surface area for agents to parse. Even if it aggregates many sub-domains, the cognitive load and prompt size make selection error-prone; this should likely be split into focused servers.
Completeness3/5
WordPress coverage is fairly broad (posts, pages, media, plugins, themes, settings, health), but there are gaps: no get_single_page tool, no user/comment management, and no media upload from local files. The project/system side lacks obvious workflow actions beyond health checks and metrics.
Maintenance
ActivityInactive
ResponsivenessNo issues