Skip to main content
Glama
teamchrisfromthelc

local-wp-mcp

by teamchrisfromthelc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to local-wp-mcp

No user-submitted related servers found.

    Related Servers

    • LocalWP MCP

      kazimshah39
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to discover, manage, and interact with LocalWP sites through integrated WP-CLI, SQL access, and backup workflows. It provides cross-platform site diagnostics and environment resolution for seamless local WordPress development.
      11 npm
      1
      ISC

    • AI Site Manager MCP

      nkd3v
      A
      license
      B
      quality
      A
      maintenance
      Enables MCP clients to connect to a WordPress site with a scoped API key and manage posts, pages, custom post types, taxonomies, comments, media, approved settings, plugins, and themes. It runs locally over stdio and requires the companion WordPress plugin to be installed and activated.
      35
      MIT

    • 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

    • wp-ultra-mcp

      mdnishath
      A
      license
      Not graded
      quality
      A
      maintenance
      Turns any WordPress site into an MCP server, allowing AI clients to directly control files, database, WP-CLI, PHP, content, and more through declarative abilities without writing code.
      3
      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

    A4.1/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target distinct resources (sites, WP-CLI, database, files). The main overlap is wp_active_plugins vs wp_cli_run 'plugin list', but descriptions clarify the direct database query vs CLI execution. Otherwise, each tool serves a clear purpose.

    Naming Consistency4/5

    Tools use clear prefixes for domains (wp_*, mysql_*) and consistent verb_noun for file operations (read_site_file, write_site_file). Minor inconsistency: wp_cli_run is noun_verb rather than verb_noun, and file operations lack a prefix, but the pattern is still predictable.

    Tool Count5/5

    10 tools is well-scoped for a local WordPress development server covering sites, WP-CLI, database, and file operations. Each tool earns its place without feeling redundant or excessive.

    Completeness4/5

    The surface covers core workflows: read/write files, query database, run WP-CLI, list sites, and inspect schema. A minor gap is the lack of a tool to switch the 'current site' referenced by wp_site_info, but overall the lifecycle is adequately covered.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources