mcp-rs
Related Servers
Alternatives to mcp-rs
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for WordPress content management via REST API, supporting posts, pages, media, comments, and terms through natural language interfaces like Cursor, ChatGPT, Codex, and Claude.18 npmMIT
- AlicenseNot gradedqualityCmaintenanceRead-only MCP server for exploring WordPress MySQL/MariaDB databases. Provides schema inspection, relationship mapping, and safe SQL querying.6MIT
- AlicenseCqualityDmaintenanceA lightweight MCP server that connects to WordPress via REST API, enabling content management (posts, pages, categories, etc.) and site configuration through natural language commands.49Apache 2.0
- FlicenseBqualityDmaintenanceLocal MCP server for Codex/Claude to query and edit WordPress content through the WordPress REST API.26-
- AlicenseNot gradedqualityCmaintenanceAn MCP server for managing multiple WordPress sites via the WordPress REST API. It supports posts, categories, tags, media, comments, and site configuration through natural language.48 npmISC
- FlicenseNot gradedqualityBmaintenanceProvides MCP servers to interact with WordPress sites via REST API, supporting multiple sites and aggregated tools.-
TDQS
Scored across 33 tools
Several tools have heavily overlapping purposes: create_post, create_post_with_featured_image, create_post_with_categories_tags, create_advanced_post, and create_post_with_embeds all create posts, differing only by optional features. Retrieval tools also blur together: get_posts, get_all_content, get_post, and get_pages overlap, while get_media and get_media_item are easily confused. An agent would struggle to choose the correct tool without trial and error.
Most names follow a predictable snake_case verb_noun pattern such as get_posts, create_category, update_tag, and delete_media. A few deviate with compound or noun-first forms like wordpress_health_check, mcp_rs_status, and create_post_with_featured_image, but the overall convention remains readable and mostly consistent.
With 33 tools, the surface is heavy for a WordPress content-management server. The count is inflated by redundant post-creation variants and overlapping retrieval tools, so many tools do not clearly earn their place.
Core content operations are well covered: posts and pages can be retrieved, created, updated, and deleted; media and taxonomies have CRUD; settings and front-page configuration are present. However, comments are read-only, and there is no user, plugin, theme, or menu management, leaving notable gaps for broader WordPress administration.