Skip to main content
Glama
YanaShuvaieva

WordPress MCP Custom Server

by YanaShuvaieva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to WordPress MCP Custom Server

No user-submitted related servers found.

    Related Servers

    • 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.
      36 npm
      1
      ISC

    • WordPress MCP Server

      gdamalis
      F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server for managing WordPress sites through the REST API, featuring 38 tools for content, media, plugin, and theme management. It supports secure Application Password authentication and offers specific compatibility for Divi theme shortcode structures.
      -

    • 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

    • notipo

      kfuras
      A
      license
      A
      quality
      A
      maintenance
      MCP server for publishing to WordPress. 13 tools cover posts, categories, tags, image hosting, featured images, and SEO metadata (Rank Math, etc.) One call runs the full markdown-to-live-URL pipeline.
      13
      10 npm
      4
      AGPL 3.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

    C2.1/5.0

    Scored across 32 tools

    Disambiguation2/5

    The tool set has 32 tools, but many are deprecated aliases for the same underlying operations. There are also overlapping validation tools (validate_urls_raw vs validate_pages vs validate_and_recheck vs autofix_safe) that are quite similar in purpose, and overlapping checklist tools. The deprecated aliases create significant ambiguity about which tool to use.

    Naming Consistency2/5

    The set mixes namespace-dotted versioned names (content.list.v1, site.request.v1) with deprecated snake_case aliases (list_posts, wp_request). Even within the main names, there's inconsistent structure: some use domain.action form (content.publish.v1) while others use flat action form (read_project_file, benchmark.compare_ab.v1).

    Tool Count1/5

    32 tools is excessive for what is genuinely a moderate-scope WordPress automation server. Critically, roughly half of the tools (13+) are deprecated aliases that should have been removed, meaning only about 19 are real and roughly half of those are legitimate. The deprecation burden inflates the count enormously.

    Completeness3/5

    The core surface covers content publishing, ACF updates, project file management, site options, SEO meta, W3C validation, playbooks, and benchmarks. However, there are notable gaps: no tool to update existing posts (only list and publish new), no get single post, and no delete. Content update appears limited to ACF fields rather than general post editing.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources