Skip to main content
Glama
THE-KIPDEV

wpagent-mcp

by THE-KIPDEV
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to wpagent-mcp

No user-submitted related servers found.

    Related Servers

    • Royal MCP by royalplugins

      Royal MCPofficial

      royalplugins
      F
      license
      Not graded
      quality
      A
      maintenance
      Production MCP server that runs as a WordPress plugin, exposing 40+ tools for managing posts, pages, custom post types, WooCommerce products, media, users, and menus from any MCP client. Includes API key + OAuth 2.0 authentication, rate limiting (60 req/min per IP), and activity logging. Free on WordPress.org
      9
      -

    • AgentLinkWP

      AIGenArt
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI agents to securely manage multiple self-hosted WordPress sites, including content editing, theme management, and maintenance operations with fine-grained permission controls.
      -

    • AlphaBridge MCP

      CultureClub-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Turns a WordPress site into a native MCP server: 39 structured tools for content, media, taxonomies, comments, widgets and site settings, with OAuth 2.1 + PKCE and per-call WordPress capability checks. Pure PHP inside WordPress — no bridge server or middleware to host.
      GPL 2.0

    • JalinWP

      fatomate
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP gateway that enables AI clients to securely connect to WordPress and WooCommerce sites via OAuth, retrieve permitted content and data, and apply changes under configurable approval modes.
      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

    B3.4/5.0

    Scored across 58 tools

    Disambiguation4/5

    Most tools follow a clear resource+action split (plugin, content, order, comment, media, user), but a few overlap: wp_site_info vs wp_site_health, wp_get_content vs wp_elementor_get_page, and wp_cli_execute can replicate many dedicated tools. Descriptions generally prevent misselection.

    Naming Consistency4/5

    The overwhelming pattern is wp_<domain>_<verb>_<noun> in snake_case, which is predictable and easy to navigate. Deviations include noun-only names like wp_woocommerce_shipping_zones, wp_woocommerce_payment_gateways, and wp_elementor_widget_types, plus nominal names like wp_site_info and wp_site_health.

    Tool Count2/5

    With 58 tools, this is far beyond the typical well-scoped MCP surface and creates a large namespace for an agent to navigate. While each subdomain is heavily covered, the count is excessive for a single server and many tools could be consolidated or exposed as subcommands.

    Completeness3/5

    The server covers a broad range of domains with solid CRUD cycles for content, plugins, media, options, and comments. However, notable lifecycle gaps remain: themes have no update/delete, WooCommerce coupons and tax rates have no update/delete, and users have no delete operation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources