Skip to main content
Glama
cascade-cms-mcp-server
by kuklaph

Related Servers

Alternatives to cascade-cms-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to interact with the Data API, manage sites and content, and perform Designer-related operations through MCP tools. It supports both remote OAuth and local API-token configurations.
      511 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      An MCP server that wraps the TeamDynamix (TDX) REST API, enabling AI-assisted IT service management through natural language. It exposes 41 tools for managing tickets, assets, CMDB, knowledge base articles, and other core TDX domains.
      41
      70 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to interact with a WordPress site, allowing content and taxonomy management (list, create, update, delete) through 17 MCP tools.
      2
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLMs to interact with generated REST API services by exposing MCP tools and resources for CRUD operations, listing, and retrieval. It lets AI clients discover and call create, update, delete, list, and get-by-id actions against the same data available over REST.
      MIT

    TDQS

    A4.4/5.0

    Scored across 37 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose, from asset CRUD to post-read inspection, workflow management, and system administration. Descriptions effectively differentiate between similar operations (e.g., cascade_read_workflow_information vs cascade_read_workflow_settings).

    Naming Consistency5/5

    All tools follow a consistent 'cascade_verb_noun' pattern (e.g., cascade_read, cascade_create, cascade_asset_list_facts). The naming convention is uniform and predictable across the entire set.

    Tool Count4/5

    With 37 tools, the surface is comprehensive but slightly heavy. The count is justified by the depth of CMS operations (CRUD, workflow, messaging, search, audit, etc.), though some consolidation (e.g., asset inspection tools) could be considered.

    Completeness4/5

    The tool set covers most major CMS workflows: read, create, edit, copy, move, delete, publish, workflow, search, audit, access control, and preferences. A minor gap is the absence of a direct 'list children' tool, but search can serve this purpose.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data