MCP Hub
Related Servers
Alternatives to MCP Hub
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables AI to manage WordPress sites with 190+ tools for complete control over content, themes, plugins, files, and more.10029 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI clients to manage WordPress and WooCommerce sites with over 194 tools for content, users, security, performance, and e-commerce operations.ISC
- AlicenseCqualityDmaintenanceEnables 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.10029 npm56MIT
- 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 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
Scored across 554 tools
Service prefixes (wordpress_, woocommerce_, gitea_, n8n_, supabase_) help separate domains, but there are outright duplicate-intent tools: wordpress_wp_db_check vs wordpress_specialist_wp_db_check, wordpress_cache_purge vs wordpress_wp_cache_flush, wordpress_transient_flush vs wordpress_wp_transient_delete_all, wordpress_generate_and_upload_image vs woocommerce_generate_and_upload_image, and wordpress_delete_media vs woocommerce_delete_media. Multiple unrelated *_list_projects (Coolify, OpenPanel, n8n, hub-level) and several health-check tools across services make selection error-prone.
The dominant pattern is service_verb_noun snake_case (wordpress_create_post, gitea_merge_pull_request, supabase_delete_policy), which is readable. However, the WordPress surface is split across three prefixes ('wordpress_', 'wordpress_specialist_wp_', 'wordpress_wp_'), and hub-level tools (get_endpoints, set_rate_limit_config, check_all_projects_health, manage_api_keys_rotate) break the verb_noun prefix convention.
554 tools in a single server is an extreme mismatch; no agent can reasonably navigate this surface, and it far exceeds any scoped-purpose guideline. This is effectively a bundled aggregator of a dozen-plus integrations rather than a coherent tool set.
Most integrations (WordPress, WooCommerce, Gitea, Supabase, n8n, Coolify, Cloudflare) have broad CRUD coverage, so dead ends are rare within them. But other surfaces are thin: Gmail has no send/draft/compose tool, Search Console exposes only four read operations, and OAuth lacks update/secret-rotation lifecycle.