Skip to main content
Glama
cvsloane

MainWP MCP Server

by cvsloane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MainWP MCP Server

No user-submitted related servers found.

    Related Servers

    • MainWP MCP Server by mainwp

      MainWP MCP Serverofficial

      mainwp
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to manage WordPress networks through a MainWP Dashboard, including site management, updates, plugin/theme control, and bulk operations via natural language.
      2
      115 npm
      24
      GPL 3.0

    • WordPress MCP Server

      LiamCioci
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with WordPress sites through the REST API. Supports multiple WordPress sites with secure authentication, enabling content management, post operations, and site configuration through natural language.
      20 npm
      MIT

    • Passepartout

      AlessandroB1989
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage content on self-hosted WordPress sites via the WordPress REST API, supporting multiple sites with custom key authentication and tools for posts, pages, media, and taxonomies.
      MIT

    • WordPress MCP Server

      gaupoit
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage WordPress sites through natural conversation, supporting post creation, content updates, site queries, and draft-to-publish workflows via the WordPress REST API.
      9
      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

    B3.4/5.0

    Scored across 43 tools

    Disambiguation4/5

    Tools are clearly grouped by resource (clients, costs, plugins, etc.) with distinct actions. Some potential confusion exists between 'apply' updates and specific update types, but descriptions clarify. Overall, most tools are unambiguous.

    Naming Consistency5/5

    All tools follow a consistent pattern: 'mainwp_<resource>_<verb>'. Verbs are uniform (add, delete, list, etc.) and resources are clearly named. No mixing of conventions.

    Tool Count4/5

    43 tools is high, but the server covers multiple sub-domains (sites, plugins, themes, updates, clients, costs, tags). Each sub-domain has a reasonable number of operations. Slightly over the typical range, but justified by the scope.

    Completeness3/5

    The tool set covers most CRUD and lifecycle operations for sites, plugins, themes, updates, clients, and costs. However, tag management is incomplete (only list and get sites by tag; no create/delete/edit). This is a notable gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources