Skip to main content
Glama
sbguangha

agent-gateway

by sbguangha

Related Servers

Alternatives to agent-gateway

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query live schema, lineage, and query-context across data warehouses, dbt projects, orchestration systems, and BI tools via MCP tools.
      Apache 2.0
    • F
      license
      B
      quality
      B
      maintenance
      Enables AI agents to query an air-gapped enterprise knowledge vault via seven MCP tools for deterministic and hybrid retrieval, entity graph traversal, context compression, archive inspection, onboarding scans, and node status.
      7
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables enterprise AI agents to query governed data lineage, PII-aware schema documentation, and semantic metadata from SQL logs via MCP, with role-based access and vector search.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Production Model Context Protocol (MCP) server for business — replaces stale generic descriptions with concrete 2026 technical intelligence and data agents. Exposes dynamic KPI analytics, forecasting, anomaly detection, and schema resources across 10 enterprise domains via FastMCP over stdio and SSE transports.
      2
      9
      AGPL 3.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to query databases correctly by serving governed context over MCP, including canonical metric definitions, relationships, business meaning, and guardrails, so answers come back with resolved definitions, fired filters, freshness, and a trust score instead of guesses.
      3
      -

    TDQS

    A4.1/5.0

    Scored across 12 tools

    Disambiguation4/5

    The knowledge base tools (kb_list_tags, kb_search, kb_get_doc, kb_get_outline, kb_read_section) have a clear hierarchical flow (search -> outline -> read), and the business tools (biz_list_metrics, biz_query_sales, biz_get_sku, biz_get_order, biz_anomaly_scan) are distinct operationally. Minor overlap exists between kb_get_doc and kb_read_section, both for reading content, but guidance on when to use each is provided.

    Naming Consistency4/5

    Tool names are consistent, following a verb_noun pattern with prefixes indicating domain (kb_, biz_, catalog_). Most use standard verbs like list, get, read, search, query, and anomaly_scan is a slight deviation but still readable.

    Tool Count4/5

    With 12 tools, the server covers three distinct domains (knowledge, business, catalog) without excessive granularity. The count is reasonable and each tool serves a clear purpose, though it is a bit high for the scope, justifying a slightly lower score.

    Completeness3/5

    The server offers a comprehensive read/search surface for knowledge (tag, search, outline, section, full doc) and metrics (dictionary, query, SKU, order, anomaly scan), but lacks write or update tools (no create/edit/delete). This is acceptable if it's a fetch-only gateway, but for general lifecycle coverage it's incomplete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues