Skip to main content
Glama
Sign In
metrics-mcp

metrics-mcp

by razornne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to metrics-mcp

No user-submitted related servers found.

    Related Servers

    • governed-analytics-agent

      Binary-yev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to answer analytics questions with provable correctness by resolving metrics through the semantic layer, tracing lineage, traversing knowledge graphs, checking freshness, and searching glossary definitions, while enforcing access controls and logging every call.
      MIT

    • zigmo

      unprimathe
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents and their users to ask business questions in plain language and receive governed metric values, breakdowns, share-of-total figures, and the exact parameterized SQL behind them, drawn from a single semantic model rather than ad-hoc SQL. It also lets clients inspect available metrics and their definitions, and preview optimized queries without executing them.
      4
      MIT

    • semantic-mcp

      stefbartieri
      A
      license
      A
      quality
      C
      maintenance
      Exposes a governed semantic layer to AI agents so they select metrics and dimensions from a closed, engineer-declared vocabulary instead of writing SQL. Validates every typed call against the contract, rejects out-of-contract requests with structured errors and suggestions, and returns query rows together with the compiled SQL and dbt lineage for auditing.
      4
      MIT

    • slh-server

      alexmerced-oss
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to list metrics and dimensions, inspect definitions, and run governed metric queries against Apache Iceberg tables through a semantic layer, without writing SQL or accessing raw rows or columns outside their role.
      5
      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

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: listing available metrics, retrieving full definitions with caveats, computing metric values, and verifying drafted answers. There is no overlap or ambiguity about which tool to call for a given step.

    Naming Consistency5/5

    All tool names follow the same snake_case verb_noun pattern: list_metrics, get_metric, query_metric, verify_answer. The pattern is consistent and predictable, with only the expected singular/plural variation for the metric resource.

    Tool Count5/5

    Four tools is well-scoped for a read-only metrics warehouse surface. Each tool covers a necessary step in the workflow and none feel redundant or missing.

    Completeness5/5

    The tool set covers the full analytical workflow: discover what metrics exist, understand their exact definitions and caveats, query them, and verify any final answer before it is delivered. There are no obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources