Verified

Questdb MCP Server

QuestDB Web Console interactions via query execution, cell creation, and chart building.

Data last scanned today · Reviewed today

383 tools★ 2TypeScriptApache-2.0

Overview

The QuestDB MCP Server acts as a bridge between coding agents and your local QuestDB Web Console. It provides tools that allow AI assistants to manipulate notebook cells, execute SQL queries, and generate charts directly within your established browser-based session. By automating these tasks, the server enables agents to interact with your time-series data without manual browser switching. Setup is facilitated through an interactive CLI wizard that detects installed coding agents and handles configuration pinning. Users can specify custom origins and port configurations via environment variables, or manually configure their MCP clients to invoke the server using npx. The server is designed to maintain compatibility with specific QuestDB console versions by pinning bridge versions to individual agent configurations.

Our verdict

This server carries a high-risk score of 33/100, primarily due to it being a community-maintained project rather than an official vendor release and the fact that its authentication methods have not been independently reviewed. Because the server bridges external agents to your live database console, users should exercise caution. It is suitable for experimentation by experienced users who understand the implications of linking AI agents to local database sessions, but it should be avoided in sensitive production environments.

Interactive CLI wizard simplifies agent configuration and version pinning
Supports custom log paths and granular debug logging levels
Low supply-chain footprint with only seven direct dependencies
Apache-2.0 open-source licensing

Security assessment of authentication methods remains incomplete
Lack of official vendor maintenance and editorial review
Single-contributor codebase presents a notable bus-factor risk

Setup

Claude Desktop

{
  "mcpServers": {
    "mcp-server-questdb": {
      "args": [
        "-y",
        "@questdb/mcp-server-questdb"
      ],
      "command": "npx"
    }
  }
}

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.

No read-only mode — running this grants full read/write access.
No built-in authentication — anyone with access to this config can invoke every tool it exposes.

Tools

Tool	Description	Risk
get_pairing_credentials	Provides pairing credentials for the browser to authorize the MCP bridge.	low
run_query	Executes a SQL query against the QuestDB instance.	medium
update_cell	Updates a notebook cell within the QuestDB Web Console.	medium

Compatibility

Client	Local	Docker	Remote	Read-only
ChatGPT
Claude Desktop
Cursor
VS Code
Windsurf

Frequently asked questions

›How do I configure my coding agent to use the QuestDB MCP server?

You can use the interactive setup wizard by running 'npx @questdb/mcp-server-questdb setup', which automatically detects your installed agents and updates their configuration.

›What should I do if my QuestDB Web Console version does not match the bridge?

You must run the matching version of the server by executing 'npx @questdb/mcp-server-questdb@<version> setup' to ensure compatibility with your specific console version.

›How do I pair my browser with the MCP bridge?

The agent will provide a deep link to open in your Web Console tab or a WebSocket URL and token to paste into the MCP pill located at the bottom of the Web Console.

›Do I need to re-pair every time I restart the bridge?

Yes, each bridge run generates fresh credentials held only in memory, so you must perform the pairing process again if the bridge restarts.

›Can I manually set a fixed port for the MCP bridge?

Yes, you can specify a fixed port by setting the 'MCP_BRIDGE_PORT' environment variable, though note that the pairing will fail with a 'bridge_bind_failed' error if that port is already in use.

›Where are the bridge logs stored?

By default, logs are stored in '/tmp/questdb-mcp-bridge/' using an ISO timestamp and PID for the filename, though this location can be overridden using the 'LOG_PATH' environment variable.