Skip to main content
Glama
alokemajumder

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to wpxmcp

No user-submitted related servers found.

    Related Servers

    • WordPress MCP Server

      InstaWP
      F
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to interact with a WordPress site, allowing content and taxonomy management (list, create, update, delete) through 17 MCP tools.
      2
      -

    • wordpress-mcp

      cvrt-jh
      A
      license
      C
      quality
      D
      maintenance
      Enables AI-powered WordPress management via MCP, with 158 tools for posts, pages, media, plugins, themes, users, comments, and more, plus token-optimized responses.
      100
      59 npm
      3
      MIT

    • Factosys MCP

      SantosSjba
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to manage WordPress sites by providing tools for posts, media, users, plugins, menus, widgets, comments, options, and system administration over the MCP protocol, with support for application passwords and OAuth 2.1.
      GPL 2.0
    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

    A3.7/5.0

    Scored across 117 tools

    Disambiguation4/5

    Tools are largely distinct, with clear descriptions for overlapping use cases (e.g., get_content vs get_content_summary vs get_content_by_slug vs find_content_by_url). A few explicit aliases (create_plugin/install_plugin, edit_media/update_media) are labeled as such, but the sheer number of tools may still cause some selection confusion despite clear descriptions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., list_comments, create_term, update_theme_file, delete_menu). Even compound names like assign_terms_to_content and get_global_styles maintain the convention. The aliases also conform to the pattern, so there is no stylistic inconsistency.

    Tool Count1/5

    At 117 tools, this is an extreme count far beyond the calibration's 50+ threshold. While the tools cover a broad WordPress management domain, many could be consolidated (e.g., get_content and get_content_summary could be one tool with a parameter). The volume is overwhelming and likely to confuse agents, making it inappropriate for efficient use.

    Completeness5/5

    The toolset is remarkably comprehensive, covering content lifecycle, taxonomies, media, users, comments, plugins, themes (including draft workflows), menus, widgets, templates, global styles, blocks, revisions, meta, options, SQL, WP-CLI, abilities, snippets, fields, audits, bulk operations, and an escape-hatch REST API tool. There are no obvious dead ends; even edge cases like unregistered meta have dedicated tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources