Skip to main content
Glama
vietanha34

sigma-streaming-platform-mcp

by vietanha34
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to sigma-streaming-platform-mcp

No user-submitted related servers found.

    Related Servers

    • cycloid-mcp-server by cycloidio

      cycloid-mcp-serverofficial

      cycloidio
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with the Cycloid platform for infrastructure management, including blueprint discovery, stack creation, pipeline listing, and event monitoring via natural language.
      MIT
    • ZeroPath MCP Server by ZeroPathAI

      ZeroPath MCP Serverofficial

      ZeroPathAI
      A
      license
      B
      quality
      D
      maintenance
      Allows developers to query security findings (SAST issues, secrets, patches) using natural language within AI-assisted tools like Claude Desktop, Cursor, and other MCP-compatible environments.
      17
      9
      MIT

    • argocd-mcp

      adityaraj178
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with Argo CD applications through natural language, providing tools for cluster, project, application, and resource management via stdio and HTTP transports.
      Apache 2.0

    • DevOps Agent Harness

      stwins60
      A
      license
      Not graded
      quality
      B
      maintenance
      Turns any AI coding agent or MCP client into a governed DevOps engineer by exposing policy-enforced tools for Kubernetes, Docker, Jira, Git/PR, CI/CD, AWS, Terraform, and incident response, with approvals, audit logging, secret redaction, and rollback enforced outside the model.
      6
      Apache 2.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

    A3.5/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose. List tools differentiate by resource (apps, channels, servers, error channels) and get tools provide details. Control verbs (start, stop, restart) are unambiguous. No overlapping functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case (list_apps, get_channel_detail, start_channel). Verbs like list, get, start, stop, restart, and check are used uniformly.

    Tool Count5/5

    11 tools cover the main operations for a streaming platform: listing, details, channel control, health check, and server info. This is well-scoped without unnecessary duplication.

    Completeness4/5

    Core lifecycle operations are present (list, get, start, stop, restart) for channels, plus health and server info. Missing creation or update tools for apps or channels, but these may be out of scope. The surface is mostly complete for management tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources