Skip to main content
Glama
mpierre135

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to wp-mcp-control-server

No user-submitted related servers found.

    Related Servers

    • TypeScript WordPress MCP

      bokazio
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for WordPress content management that provides a secure interface for AI assistants to interact with WordPress sites, enabling content creation, editing, and media management without destructive operations.
      MIT

    • TanukiMCP

      AppleJax2
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server for WordPress automation that enables users to manage content, themes, and site configurations using AI-driven workflows and the WordPress REST API. It provides a wide array of tools for site planning, management, and optimization compatible with tools like Cursor and Claude.
      62 npm
      1
      ISC

    • wp-mcp

      cnmbdb
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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.
      12 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 149 tools

    Disambiguation3/5

    Many tools are clearly separated by resource type, but there are notable overlaps: wp_elementor_update_element is a general tool that subsumes wp_elementor_update_text/button/image, and wp_update_product overlaps with wp_update_product_price. Similarly, the line between generic CPT tools and concrete post/page/product tools can be blurry. Overall, descriptions help but the large surface creates real selection ambiguity.

    Naming Consistency5/5

    Every tool follows the same wp_verb_noun snake_case pattern. List/get/create/update/delete are used predictably across all resource types, and specialized actions like restore, clone, purge, and audit also follow the convention consistently. No mixed casing or random verb styles are present.

    Tool Count1/5

    With 149 tools, this is an extreme count that goes well beyond what an agent can efficiently navigate or reliably select from. Even a broad WordPress control surface does not justify this many individual operations, and the count strongly harms coherence and usability.

    Completeness4/5

    The surface is exceptionally broad: posts, pages, media, users, comments, taxonomies, menus, plugins, themes, settings, SEO, Elementor, WooCommerce, forms, webhooks, redirects, snapshots, revisions, and audits are all covered. Minor gaps exist—such as no user update/delete, no menu create/update/delete, and no form submission get/delete—but they do not block most workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources