Skip to main content
Glama
crunchtools

MCP WordPress CrunchTools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP WordPress CrunchTools

No user-submitted related servers found.

    Related Servers

    • 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

    • WordPress MCP Server

      nao9net
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for managing multiple WordPress sites via the WordPress REST API. It supports posts, categories, tags, media, comments, and site configuration through natural language.
      54 npm
      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.
      17 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.
      -
    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 30 tools

    Disambiguation4/5

    Most tools target distinct resources (posts, pages, media, comments, categories, tags, revisions), but there is redundancy: list_posts and search_posts overlap (both support keyword search), and update_comment and moderate_comment both manipulate comment status, creating potential confusion.

    Naming Consistency5/5

    All tools follow a consistent 'wordpress_verb_noun' pattern, with standard verbs like list, get, create, update, delete, search, upload, moderate. Even page-revisions follow the same convention (list_page_revisions). No mixed naming styles or unpredictable variations.

    Tool Count2/5

    30 tools is excessive for a WordPress MCP server, exceeding the 'heavy' threshold of 25+. While WordPress has many entities, the set could be consolidated (e.g., merging search_posts into list_posts, reducing revision tools), and the count will likely overwhelm agents with too many options.

    Completeness3/5

    Core content management is well covered: posts, pages, media, comments, and revisions. However, notable gaps exist: no update/delete for categories or tags, no search_pages (only list_pages with search), no get_page_revision (only list_page_revisions), and no user management. This leaves some workflows incomplete, but major operations are present.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources