wpagent-mcp
Related Servers
Alternatives to wpagent-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceManages 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
- AlicenseNot gradedqualityAmaintenanceProvides a secure MCP bridge to interact with WordPress sites via signed requests, scoped keys, and approval workflows.1GPL 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to manage WordPress content and WooCommerce resources through scoped, expiring connections, with human-approved change proposals, revision checks, audit records, and controlled maintenance windows.GPL 2.0

Royal MCPofficial
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.org9-- AlicenseNot gradedqualityNot gradedmaintenanceTurns a WordPress site into MCP-accessible tools so AI clients can build pages, manage content, plugins, users, settings, and media, while running performance and security audits. It also integrates with installed builders, plugins, and services such as Elementor, WooCommerce, SEO tools, and form builders when available.GPL 2.0
TDQS
Scored across 58 tools
Most tools follow a clear resource+action split (plugin, content, order, comment, media, user), but a few overlap: wp_site_info vs wp_site_health, wp_get_content vs wp_elementor_get_page, and wp_cli_execute can replicate many dedicated tools. Descriptions generally prevent misselection.
The overwhelming pattern is wp_<domain>_<verb>_<noun> in snake_case, which is predictable and easy to navigate. Deviations include noun-only names like wp_woocommerce_shipping_zones, wp_woocommerce_payment_gateways, and wp_elementor_widget_types, plus nominal names like wp_site_info and wp_site_health.
With 58 tools, this is far beyond the typical well-scoped MCP surface and creates a large namespace for an agent to navigate. While each subdomain is heavily covered, the count is excessive for a single server and many tools could be consolidated or exposed as subcommands.
The server covers a broad range of domains with solid CRUD cycles for content, plugins, media, options, and comments. However, notable lifecycle gaps remain: themes have no update/delete, WooCommerce coupons and tax rates have no update/delete, and users have no delete operation.