wp-woo-mcp
Related Servers
Alternatives to wp-woo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to manage WordPress sites through natural conversation, supporting post creation, content updates, site queries, and draft-to-publish workflows via the WordPress REST API.9MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to manage an online store's products, variations, orders, refunds, customers, coupons, shipping, taxes, payment gateways, reports, and settings through the WordPress REST API. It also supports WordPress content operations such as creating and updating posts and metadata.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage WordPress posts, pages, media, taxonomies, comments, users, settings, and custom fields through the WordPress REST API. Supports secure authentication, OAuth deployment, search, and safe write controls.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read and edit WordPress pages, posts, terms, media and menus through 15 guarded tools, with content saved as drafts, no deletions, block allowlists, single-use image uploads and dry-run menu changes that keep a human in control.GPL 2.0
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with WordPress sites through REST APIs, allowing programmatic management of posts, users, comments, categories, and tags with secure authentication.2950MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to read and edit WordPress sites over the REST API, including Divi 4, Divi 5, and Gutenberg content, with safety features like round-trip verification, draft-based editing, and dry-run previews.45MIT
TDQS
Scored across 15 tools
The wp_/wc_ prefixes plus action names cleanly separate WordPress content tools from WooCommerce commerce tools, and no two tools do the same thing. The only soft spot is posts vs. pages: wp_get_post/wp_update_post have no page equivalents, so an agent must infer that wp_list_pages is read-only and not a candidate for page retrieval or edits.
Nearly all tools follow a strict prefix + verb_noun pattern (wp_list_posts, wp_get_post, wc_update_order_status), which is very predictable. wp_site_info breaks the pattern as the one noun-only tool, a minor deviation.
15 tools is well within a healthy range and each one maps to a distinct resource-and-action pair across two domains. Nothing feels padded or redundant; the read/write split per resource is proportionate.
Posts have full read/create/update/trash coverage and products and orders have solid read/update surfaces, but pages are list-only with no get, create or update, and there is no product deletion, no customer tools. Refunds and publishing are explicitly out of scope, which is a deliberate but real dead end.