AlphaBridge MCP for WordPress
Related Servers
Alternatives to AlphaBridge MCP for WordPress
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityAmaintenanceProduction MCP server that runs as a WordPress plugin, exposing 40+ tools for managing posts, pages, custom post types, WooCommerce products, media, users, and menus from any MCP client. Includes API key + OAuth 2.0 authentication, rate limiting (60 req/min per IP), and activity logging. Free on WordPress.org10-- AlicenseNot gradedqualityAmaintenanceWordPress plugin that runs an MCP server on your own site: search and read published posts and pages, look up WooCommerce products, describe the site as schema.org types and query site figures, with drafts only when the site enables them. Signed-in access by default; anonymous access and OAuth are optional and off.2GPL 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage WordPress sites by providing tools for posts, media, users, plugins, menus, widgets, comments, options, and system administration over the MCP protocol, with support for application passwords and OAuth 2.1.GPL 2.0
- AlicenseBqualityDmaintenanceEnables MCP-compatible clients to securely operate a WordPress site through a signed REST API, managing plugins, content, themes, menus, media, users, WooCommerce, Elementor, audits, and allowlisted WP-CLI commands.5860 npmMIT
- AlicenseNot gradedqualityCmaintenanceManages WordPress sites over the REST API, enabling users, posts/pages, media, ACF fields, and Elementor page operations through MCP-compatible clients.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible clients to manage a WordPress site through the native REST API, including reading and creating posts and tags, uploading media, and assigning featured images with write safeguards.MIT
TDQS
Scored across 95 tools
Most tools target a clearly distinct resource/action (post vs post meta vs builder element, plugin install vs plugin update vs activation), and descriptions explicitly cross-reference near-neighbors. The main risk is density: with 95 tools there are several clusters of similar diagnostic or install/update variants an agent must read carefully to pick correctly.
Names consistently use snake_case under a wp_ prefix, with coherent subsystem prefixes wp_wc_ for WooCommerce and wp_seo_ for SEO. Variants like wp_install_plugin vs wp_install_plugin_zip and wp_upload_media vs wp_upload_media_from_url are predictable.
95 tools is far beyond a well-scoped MCP surface; even a broad WordPress admin domain does not justify this many distinct endpoints. Many operations could be consolidated or scoped to fewer tools with parameters.
The surface covers core WordPress objects, media, users, terms, comments, menus, widgets, plugins/themes/core updates, cache, search-replace, SEO, and some WooCommerce operations. Minor gaps remain (e.g. delete meta operations, broader WooCommerce product/coupon lifecycle, application-password revocation), but most workflows have a path.