AutoWP MCP Server
Related Servers
Alternatives to AutoWP MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables direct interaction with WordPress sites via Claude using the REST API, allowing reading, creating, updating, and deleting content securely with application passwords.20MIT
- AlicenseCqualityBmaintenanceEnables Claude Code to read, edit, and manage WordPress pages, posts, shortcodes, and media via the WordPress REST API.8014 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to directly manage WordPress sites via natural language, including posts, pages, categories, tags, media, and multiple site support.MIT
- AlicenseBqualityDmaintenanceConnects Claude Desktop to WordPress sites to manage Elementor pages, Gutenberg content, and Rank Math SEO settings. It enables users to create styled pages, manage section layouts, and perform content updates through natural language commands.398 npmGPL 2.0
- AlicenseCqualityAmaintenanceEnables comprehensive WordPress site management through natural language in Claude Desktop, supporting multiple sites with 59 tools for content creation, media management, user administration, and performance monitoring.71970 npm110MIT
- FlicenseAqualityCmaintenanceEnables Claude to read context, create, and edit pages on WordPress sites via the REST API using Application Passwords.6-
TDQS
Scored across 47 tools
Most tools have clear, distinct purposes (create, list, update, delete). A few near-overlaps exist—list-media vs search-media, get-wp-categories vs list-taxonomies, authenticate-wp vs test-wp-connection—but descriptions likely help an agent disambiguate those pairs.
All tool names follow a consistent hyphenated verb-noun pattern (e.g., create-post, list-users, delete-media, set-featured-image). The consistent snake/hyphen convention and common verbs make the naming scheme predictable and easy to reason about.
47 tools is well above the 25+ threshold for a 'too many' rating. While the WordPress domain is broad, this count makes the toolset heavy, requiring an agent to scan a large surface and risk mis-selection.
The tool surface covers core WordPress workflows: posts, media, taxonomies, users, settings, and a plugin list. However, there are notable omissions such as comment management, plugin activation/deactivation/updates, and theme operations, leaving meaningful gaps for a general WordPress automation server.