Skip to main content
Glama
kroq86

Runtime Copilot MCP Server

by kroq86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Runtime Copilot MCP Server

No user-submitted related servers found.

    Related Servers

    • @us-all/dbt-mcp

      us-all
      A
      license
      B
      quality
      B
      maintenance
      A read-only MCP server that exposes dbt project artifacts and data quality result tables (BigQuery/Postgres) to LLM clients, enabling deep introspection, run-history analysis, source freshness, test coverage, and lineage walks.
      27
      35 npm
      MIT

    • Alma Atlas

      velum-labs
      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

    • databricks-mcp

      ChrisChoTW
      A
      license
      C
      quality
      D
      maintenance
      A read-only MCP server that enables users to query Databricks SQL, browse metadata, and monitor Delta Lake tables. It also supports tracking Databricks Jobs, DLT Pipelines, and cluster metrics through natural language interfaces.
      25
      4
      MIT

    • AI-DBA

      steveramos21
      F
      license
      Not graded
      quality
      B
      maintenance
      Universal database copilot for diagnostics, operations, and performance analysis via MCP and CLI.
      -
    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

    C2.1/5.0

    Scored across 47 tools

    Disambiguation1/5

    Many tools have overlapping purposes, particularly the multiple 'explain' and 'project_*' tools are hard to distinguish. The demo, benchmark, and schema tools also have unclear boundaries, making selection confusing for an agent.

    Naming Consistency2/5

    Naming conventions are inconsistent: some use underscore (benchmark_calls), some use project_ prefix, others schema_ prefix, and demo_explain_*. While groups have internal consistency, the overall pattern is mixed and unpredictable.

    Tool Count2/5

    47 tools is excessive for a single server. Many tools could be consolidated or split into separate servers. The count feels bloated and hard to navigate.

    Completeness2/5

    The tool set appears to cover many areas (benchmarking, demo, schema management, project state) but lacks clear CRUD coverage for key entities and has dead ends (e.g., no delete for most entities). Gaps in lifecycle operations are notable.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources