Skip to main content
Glama
wmatragi

rollout-playbook-mcp

by wmatragi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to rollout-playbook-mcp

No user-submitted related servers found.

    Related Servers

    • Nibble

      Talia04
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to investigate production incidents by exposing service health, logs, and deployment data through MCP tools.
      10 npm
      -

    • hypen-argocd-mcp

      hypen-code
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with ArgoCD APIs through standardized MCP tools for managing applications, resources, and deployments.
      MIT

    • GCP MCP Server

      MCP-Mirror
      A
      license
      B
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with and manage Google Cloud Platform resources including Artifact Registry, BigQuery, Cloud Build, Compute Engine, Cloud Run, Cloud Storage, and monitoring services through a standardized MCP interface.
      1
      MIT

    • flowmcp

      indra0007
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes declarative Prompt flow workflows as individual MCP tools, allowing generalist agents to invoke deterministic, isolated, and permission-bound operations without custom code.
      -
    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

    A3.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one searches existing playbooks, the other generates new plans. No overlap or confusion possible.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern: search_playbooks and generate_rollout_plan. Naming is clear and predictable.

    Tool Count2/5

    With only 2 tools, the server feels very thin for a 'rollout-playbook' domain. A typical set would include at least listing, retrieving, creating, and updating playbooks.

    Completeness2/5

    The domain of rollout playbooks is missing fundamental operations like create, read, update, delete, and execute playbooks. Only search and generate are present, leaving significant gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources