F
licenseA
qualityC
maintenanceEnables Claude to read context, create, and edit pages on WordPress sites via the REST API using Application Passwords.
6
-
wp-mcp
by amolb1986
Related Servers
Alternatives to wp-mcp
No user-submitted related servers found.
Related Servers
- 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.47212 npm23MIT
- AlicenseCqualityBmaintenanceEnables Claude Code to read, edit, and manage WordPress pages, posts, shortcodes, and media via the WordPress REST API.807 npm3MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI models like Claude to manage WordPress sites through the WordPress REST API, supporting operations like post creation, taxonomy management, and site configuration. It features secure authentication via Application Passwords and provides tools for comprehensive content administration.57 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to directly manage WordPress sites via natural language, including posts, pages, categories, tags, media, and multiple site support.MIT
- AlicenseNot gradedqualityFmaintenanceEnables interaction with WordPress sites through the REST API, supporting content management for posts, pages, users, plugins, and custom post types with Application Password authentication.1,632 npm2MIT
TDQS
A3.6/5.0
Scored across 20 tools
Disambiguation4/5
Most tools have clearly distinct purposes (e.g., wp_list_content vs wp_get_content, wp_list_taxonomies vs wp_list_terms), and descriptions clarify boundaries. However, wp_search and wp_list_content both serve content discovery, and wp_rest is a catch-all that can overlap with any dedicated tool, creating minor selection ambiguity.
Naming Consistency4/5
The wp_ prefix is consistent, and the majority follow a verb_noun pattern (list_*, create_*, get_*, update_*, delete_*). A few exceptions like wp_whoami, wp_sites, wp_search, wp_settings, and wp_rest break the pattern, but the overall style remains readable and predictable.
Tool Count4/5
With 20 tools, the server is on the heavier side but still within reason for a WordPress management tool. Each tool covers a distinct domain (content, terms, media, plugins, themes, settings), and the count is not bloated; the generic wp_rest tool could potentially have reduced the number, but the dedicated tools provide clear value.
Completeness3/5
Content CRUD is fully covered, and basic operations exist for terms, media, plugins, and settings. However, obvious gaps include term update/delete, media delete, user creation/update/delete, and theme activation. While wp_rest can fill these gaps, the dedicated tool surface is incomplete for a fully-featured WordPress management server.
Maintenance
ActivityStale
ResponsivenessNo issues