A
licenseNot graded
qualityC
maintenanceEnables Claude Code to directly manage WordPress sites via natural language, including posts, pages, categories, tags, media, and multiple site support.
MIT
mcp-wordpress
by leonardobora
Related Servers
Alternatives to mcp-wordpress
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables Claude to read context, create, and edit pages on WordPress sites via the REST API using Application Passwords.6-
- AlicenseAqualityDmaintenanceEnables direct interaction with WordPress sites via Claude using the REST API, allowing reading, creating, updating, and deleting content securely with application passwords.20MIT
- AlicenseBqualityCmaintenanceConnects Claude to WordPress sites through the REST API, enabling AI-assisted content creation, publishing, media management, user administration, and site maintenance tasks through natural language.4717 npm23MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to manage WordPress sites through a self-hosted MCP endpoint, including content, media, plugins, themes, page-builder pages, SEO fields, plugin data, theme files, PHP snippets, and updates with approval controls.MIT
- FlicenseNot gradedqualityBmaintenanceEnables full WordPress operator access through Claude Code, including content, media, plugin/theme management, direct theme-file editing, backups, cache purging, and raw REST API calls, all secured with revocable tokens and no SSH requirement.1-
TDQS
C2.9/5.0
Scored across 80 tools
Disambiguation4/5
Tools are generally organized around explicit resource+action pairs, so posts, pages, media, menus, widgets, blocks, patterns, and settings are easy to tell apart. A few edges could confuse an agent: wp_create_category vs wp_ensure_category have overlapping behavior, and the two Elementor tools are listed but marked unavailable. Overall, however, overlapping purposes are rare.
Naming Consistency4/5
The dominant pattern is wp_verb_noun (wp_list_posts, wp_create_menu, wp_delete_media) and most tools follow it predictably. The wp_blocks_* family breaks the pattern by placing the noun before the verb (wp_blocks_list, wp_blocks_update), and plugin-prefixed tools like wp_elementor_update_shortcode_content add a module prefix. These are readable deviations, not chaotic naming.
Tool Count2/5
80 tools is far beyond the comfortable agent-facing range and imposes heavy selection overhead even though the WordPress domain is broad. Several families (blocks, menus, widgets, patterns) could be consolidated with parameterized operations, and the two unavailable Elementor tools should not be included. As a set, it feels more like a full SDK surface than a curated MCP toolkit.
Completeness3/5
The content lifecycle is unusually thorough: posts, pages, media, terms, revisions, blocks, patterns, widgets, menus, and settings all have meaningful CRUD coverage. However, WordPress's core comments and user-management surfaces are absent, and the Elementor tools are dead ends because they are explicitly unavailable. That makes the set broad but uneven rather than complete.
Maintenance
ActivityInactive
ResponsivenessNo recent community issues