wp-ops-mcp
Related Servers
Alternatives to wp-ops-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 gradedqualityDmaintenanceEnables AI assistants to manage WordPress content (create, retrieve, update posts) via the WordPress REST API with secure authentication.1 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage WordPress sites via ~74 capabilities including content, media, plugins, themes, and more.-
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with WordPress sites through REST APIs, allowing programmatic management of posts, users, comments, categories, and tags with secure authentication.2949MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to inspect a WordPress blog, reuse existing media and taxonomy, prepare and update drafts, and publish only after explicit human approval through a narrow, auditable interface.MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
TDQS
Scored across 45 tools
Each tool targets a distinct resource and action (e.g., users, options, theme files, comments, taxonomies). Even closely related tools like wp_get_settings vs wp_get_option or wp_get_seo vs wp_get_acf have clear, non-overlapping scopes. No two tools appear to perform the same operation.
Most tools follow a `wp_<verb>_<entity>` pattern (wp_get_user, wp_list_users, wp_create_user), but there are notable exceptions like wp_edit_page instead of wp_update_page, wp_get_content as a listing tool rather than wp_list_posts, and wp_site_health as a noun phrase. The mix of get/list and the occasional unique verbs (extract, discover, moderate) makes naming slightly inconsistent overall.
With 38+ tools, the set is large but justified for a comprehensive WordPress operations server covering content, users, options, theme files, comments, taxonomies, plugins, settings, ACF, SEO, and menus. The count is on the high end but not excessive given the domain breadth; only a few redundant or overly niche tools could be trimmed.
The server covers many core WordPress areas, but has notable gaps: there is no tool for deleting posts/pages directly (only comment/user/term/option deletion), no media upload tool despite references to wp_upload_media, and no plugin activation/deactivation (deliberately omitted but still a functional gap). These absences leave some common workflows incomplete.