Clearon WordPress MCP
Related Servers
Alternatives to Clearon WordPress MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables management of WordPress posts and pages including creating, updating, deleting, duplicating, scheduling, and bulk editing content through the WordPress REST API.-
- AlicenseBqualityBmaintenanceEnables reading and managing WordPress sites via the WP REST API, including posts, pages, media, taxonomies, users, and arbitrary REST endpoints, with optional authenticated write operations.17176 npm1MIT
- AlicenseAqualityBmaintenanceEnables comprehensive management of WordPress sites including posts, users, media, categories, tags, and site settings via the WordPress REST API.201Apache 2.0
- 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.489 npm99GPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables interaction with WordPress sites through the WordPress REST API, supporting content management and post operations with safety confirmations.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,020 npm2MIT
TDQS
Scored across 13 tools
Most tools map to distinct actions, but get_server_health overlaps with get_auth_mode and get_endpoint_config, and get_post/find_posts have similar retrieval purposes. The three disabled tools set_social_meta, set_featured_image, and upsert_share_block share nearly identical 'use a reviewed payload workflow' descriptions, which adds ambiguity.
The set mostly follows a verb_noun snake_case pattern like get_post, upload_media, audit_slug_state, and resolve_duplicate_posts. Minor deviations such as publish_now and the mix of set_/upsert_ for disabled mutation tools keep it from being fully consistent.
13 tools is a reasonable size for a WordPress publishing server. However, three of those tools are disabled stubs that add clutter rather than functionality, so the effective tool surface is closer to 10.
The active tools cover post retrieval, payload-based upsert/publish, media upload, and duplicate management. Notable gaps remain: no direct way to set featured images or social meta, no general media retrieval, and no delete/update flow outside the payload workflow.