Skip to main content
Glama
turkenberg

MCAP MCP Server

by turkenberg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCAP MCP Server

No user-submitted related servers found.

    Related Servers

    • Bagel

      Extelligence-ai
      A
      license
      A
      quality
      A
      maintenance
      MCP server for chatting with physical-world data from robotics, drones, automotive, and IoT sources using natural language. It generates auditable SQL queries over Apache Arrow/DuckDB to let you analyze, summarize, and build data pipelines.
      18
      397
      Apache 2.0

    • text2sql-agent

      PriyankaHichkad
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants and MCP clients to ask natural-language questions about DuckDB or CSV data and receive safe, read-only SQL-generated tabular insights with automatic schema discovery and multi-table joins.
      -

    • MCP Data Analyst

      DonMul
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language querying of SQL databases using AI, supporting multiple database types and automatic schema discovery.
      1
      MIT

    • MCP-DB-Server

      sujalsamkaria0066
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language querying of SQL databases with robust safety guarantees including read-only enforcement, AST validation, and row caps.
      -
    • GraphJin by dosco

      GraphJinofficial

      dosco
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to query databases using natural language, with automatic schema discovery and SQL compilation.
      451 npm
      3,173
      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.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing, inspecting, schema inspection, version info, loading, and querying. There is no ambiguity or overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., list_recordings, load_recording). Even 'query' fits as a single verb without a noun, maintaining uniformity.

    Tool Count5/5

    With 6 tools, the server is well-scoped for its domain of MCAP recording management. Each tool serves a necessary step in the workflow without redundancy.

    Completeness5/5

    The tool surface covers the full lifecycle: discovery, inspection, loading, and querying. No obvious gaps exist for typical usage scenarios.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources