Skip to main content
Glama
siffletdata

sifflet-mcp

Official
by siffletdata

Related Servers

Alternatives to sifflet-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables SRE operations through natural language, providing tools to query SLO status, fetch runbooks, query alerts, and manage incidents with audit logging and latency tracking.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Datadog's observability platform via natural language, covering metrics, logs, APM, monitors, dashboards, incidents, and infrastructure.
      688 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables interaction with the Bigeye Data Observability platform to query data quality issues, analyze data lineage and dependencies, track AI agent data access patterns, and perform root cause analysis for data issues.
      -
    • F
      license
      B
      quality
      F
      maintenance
      Enables comprehensive Datadog monitoring capabilities including CI/CD pipeline management, service logs analysis, metrics querying, monitor and SLO management, service definitions retrieval, and team management through Claude and other MCP clients.
      13
      20
      -
    • A
      license
      B
      quality
      B
      maintenance
      Enables LLM agents to query Dynatrace SaaS for observability data (logs, metrics, traces, entities, problems, vulnerabilities) and manage configurations (dashboards, notebooks, SLOs, synthetic monitors, settings).
      100
      MIT

    TDQS

    A3.6/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (asset lookup vs incident search vs monitor details). However, incident tools use different identifiers ('by_id' vs 'by_issue_number') for what appears to be the same entity, which could confuse an agent. Asset tools by URN are distinct but share similar input patterns.

    Naming Consistency3/5

    Naming conventions are mixed: 'asset_by_urn' does not follow the verb-first pattern used by most others, and pluralization is inconsistent ('search_asset' vs 'search_incidents'). Incident tools also inconsistently use 'by_id' versus 'by_issue_number'.

    Tool Count5/5

    10 tools is well-scoped for a data observability platform, covering assets, monitors, and incidents without being overwhelming. Each tool serves a distinct function, and the count fits comfortably within the ideal range.

    Completeness3/5

    Core workflows like asset search/detail, incident management, and monitor code generation are covered. However, there is no tool to search or list monitors (only get by ID), no monitor creation/update, and only downstream asset lineage (no upstream). These are notable gaps for a monitoring-focused tool.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues