A
licenseA
qualityD
maintenanceEnables to interact with WordPress sites through the WordPress REST API, fetching posts, pages, categories, and site information.
7
3
MIT
claude-wp-mcp
by gs4lthung
Related Servers
Alternatives to claude-wp-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables comprehensive management of WordPress sites including posts, users, media, categories, tags, and site settings via the WordPress REST API.201Apache 2.0
- 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,523 npm2MIT
- AlicenseNot gradedqualityAmaintenanceEnables interaction with WordPress sites through the WordPress REST API via natural language, supporting single and multi-site management, content and taxonomy operations, media uploads, and more.133 npm99GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible clients to manage a WordPress site through the native REST API, including reading and creating posts and tags, uploading media, and assigning featured images with write safeguards.MIT
- AlicenseNot gradedqualityBmaintenanceManages WordPress sites over the REST API, enabling users, posts/pages, media, ACF fields, and Elementor page operations through MCP-compatible clients.MIT
TDQS
B3.4/5.0
Scored across 17 tools
Disambiguation5/5
Each tool maps clearly to a distinct WordPress resource and action: full CRUD for posts and pages, read-only lists for categories/tags/media/users, plus site info, URL fetching, and an explicit REST escape hatch. The list/get/create/update/delete variants are not ambiguous because the target resource is always named.
Naming Consistency4/5
The wp_ prefix and list/get/create/update/delete verb_noun pattern are highly consistent for the main post and page tools. Minor deviations like wp_site_info, fetch_url, and wp_request break the pattern slightly, but they are still readable and predictable overall.
Tool Count4/5
At 17 tools, the server is slightly above the ideal 3-15 range, but the count is justified by parallel CRUD surfaces for posts and pages plus supporting resource lookups. No tool feels redundant, though the set is a bit heavy for casual use.
Completeness4/5
Posts and pages have complete CRUD/lifecycle coverage, and categories/tags/media/users provide the read-side needed for content authoring. There are minor gaps around dedicated create/update/delete tools for taxonomies, media, and users, plus comments/settings, but the wp_request escape hatch covers any remaining WP REST API route.
Maintenance
ActivitySlowing
ResponsivenessNo issues