Skip to main content
Glama
questdb

mcp-server-questdb

Official
by questdb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-server-questdb

No user-submitted related servers found.

    Related Servers

    • qmcp

      gabiteodoru
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to interact with q/kdb+ databases for development and debugging workflows. It supports executing queries, persistent connection management, and includes a Qython translator for converting Python-like syntax to q.
      9
      MIT

    • Quarry

      yiminspace
      A
      license
      Not graded
      quality
      A
      maintenance
      Quarry provides an MCP server for database querying with safety rails, allowing AI agents to execute SQL queries, list connections, and manage schemas through a structured interface.
      193 PyPI
      4
      MIT

    • dbecho

      ginkida
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives AI agents direct read-only access to PostgreSQL databases, enabling natural language analytics through tools for schema exploration, querying, trend analysis, and data quality checks.
      11
      5
      MIT

    • OctoQuery

      benedya
      A
      license
      Not graded
      quality
      B
      maintenance
      OctoQuery is an MCP server that converts databases into AI-accessible tools by exposing each configured database as a tool that accepts SQL queries and returns JSON results, enabling AI agents to query your data directly.
      3
      MIT
    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

    A3.6/5.0

    Scored across 36 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, and descriptions proactively disambiguate the notable overlaps (apply_notebook_state vs add_cell/update_cell; run_cell vs run_query). However, the read surface has several overlapping 'state' tools — get_workspace_state, get_notebook_state, list_cells, and get_cell — that an agent could easily confuse, and set_cell_layout vs set_cell_dimensions require careful reading to tell apart.

    Naming Consistency5/5

    Nearly all tools follow a predictable snake_case verb_noun pattern (get_cell, set_cell_mode, create_notebook, delete_cell, move_cell_up, run_query). Deviations like wait_for_pairing and the numbered/suffixed movers remain readable and consistent with the scheme.

    Tool Count3/5

    36 tools is heavy for a single server and pushes past the comfortable 15-25 band. The domain (notebook+cell+layout+chart+autorefresh editing plus QuestDB schema/docs/pairing) partially justifies the breadth, but several fine-grained setters (set_cell_maximized, set_cell_name, set_cell_layout, set_cell_dimensions) inflate the count.

    Completeness4/5

    The surface covers notebook lifecycle, cell CRUD, layout/chart/highlight/autorefresh configuration, pairing, schema introspection, docs, and query validation/execution — a solid lifecycle for the domain. Minor gaps exist (no list_notebooks or rename_notebook, and cell data is only reachable via run_query), but agents can work around them.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources