Skip to main content
Glama
stuffyoushouldautomate

MCP WordPress Server

by stuffyoushouldautomate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to MCP WordPress 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.
      70 npm
      1
      ISC

    • wp-mcp

      cnmbdb
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for WordPress content management via REST API, supporting posts, pages, media, comments, and terms through natural language interfaces like Cursor, ChatGPT, Codex, and Claude.
      13 npm
      MIT

    • WordPress MCP Server

      ad02
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that bridges AI assistants to WordPress, enabling natural-language management of posts, pages, media, comments, users, plugins, and settings across multiple sites simultaneously.
      -

    • 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
    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/5.0

    Scored across 70 tools

    Disambiguation4/5

    Each tool targets a distinct resource+action (posts, pages, media, comments, categories, tags, users, settings), so boundaries are mostly clear. Minor overlap exists within clusters like wp_cache_stats vs wp_cache_info and the many SEO/performance analysis tools, but descriptions help differentiate them.

    Naming Consistency4/5

    Most tools follow a consistent wp_verb_noun pattern (wp_create_post, wp_list_users, wp_delete_comment). A few deviate to noun-first ordering (wp_performance_stats, wp_cache_stats, wp_cache_clear) and auth tools vary (wp_test_auth, wp_get_auth_status), but the overall convention is predictable.

    Tool Count2/5

    At 70 tools the surface is very heavy, well beyond the 3-15 sweet spot. While WordPress is a broad domain, the large SEO, performance, and cache clusters inflate the count and increase selection burden.

    Completeness4/5

    CRUD coverage is strong and near-complete across the core content types (posts, pages, media, comments, categories, tags, users, settings) plus auth and revisions. Gaps like site/plugin/theme administration and menu management exist but core workflows are well served.

    Resources