---
title: "QuestDB MCP Server: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/questdb/
description: "Node server published in questdb/mcp-server-questdb that pairs a coding agent with a QuestDB Web Console session so the agent can drive notebook cells, queries, and charts in that browser session."
---

# QuestDB MCP Server: review, setup & limitations · Undominated.ai

> Node server published in questdb/mcp-server-questdb that pairs a coding agent with a QuestDB Web Console session so the agent can drive notebook cells, queries, and charts in that browser session.

[← Explore all mcp servers](/mcp-servers/)

ANALYTICS DATABASES / QuestDB

# QuestDB MCP Server

Node server published in questdb/mcp-server-questdb that pairs a coding agent with a QuestDB Web Console session so the agent can drive notebook cells, queries, and charts in that browser session.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/questdb/mcp-server-questdb)

SOURCE REVIEW

 Reviewed 2026-10-15
 Evidence 4 linked sources
 Publisher QuestDB
 Licence [Apache-2.0 ↗](https://github.com/questdb/mcp-server-questdb/blob/b80e8557c9b6a492fb17ba626ffb23721fe1e51e/LICENSE)
 Revision b80e8557c9b6
 [Read what was—and wasn’t—checked ↓](#review)

“An MCP server that connects coding agents (Claude Code, Codex, Cursor, OpenCode, Gemini CLI) to a running QuestDB Web Console. The agent gets tools to create notebook cells, run queries, and build charts. Every action executes in the browser against your already-established QuestDB session.”

 [QuestDB · upstream description ↗](https://github.com/questdb/mcp-server-questdb/blob/b80e8557c9b6a492fb17ba626ffb23721fe1e51e/README.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - QuestDB publishes this package as @questdb/mcp-server-questdb in questdb/mcp-server-questdb. package.json at b80e8557c9b6a492fb17ba626ffb23721fe1e51e names author QuestDB, version 0.5.0, and license Apache-2.0.
- The README's setup command and manual MCP config are printed in that file. src/pairingTools.ts registers get_pairing_credentials and wait_for_pairing, which the README describes as the step before notebook, chart, and SQL tools run.

### A good fit for

 - Attach an agent to a QuestDB Web Console that is already open and run notebook queries through that session.
- Install a pinned bridge build as a standalone .mjs file when the environment cannot use npx.

### Weigh up before choosing

 - The default-branch commit read here, b80e8557c9b6a492fb17ba626ffb23721fe1e51e, is dated 2026-09-30. The default branch is master.
- The printed quick-setup command does not pin an npm version. The same README says the Web Console expects a specific bridge version and shows npx @questdb/mcp-server-questdb@<version> setup, and for versions earlier than 0.3.0 the former package name @questdb/mcp-bridge.
- Pairing keeps a fresh port and token only in memory. Logs default to /tmp/questdb-mcp-bridge/<ISO-ts>-<pid>.log. CONSOLE_ORIGIN defaults to http://127.0.0.1:9000.
- package.json engines field requires Node >=22.0.0. Standalone bundles are described as available from bridge version 0.4.0 and as making no network connections except the local WebSocket to the Web Console.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - README.md at b80e8557c9b6a492fb17ba626ffb23721fe1e51e: description, setup command, manual JSON, environment table, pairing, and licence line.
- package.json at the same revision: name, version 0.5.0, author, Apache-2.0, engines node >=22, typescript in devDependencies.
- LICENSE at the same revision: Apache License 2.0, appendix Copyright 2024 QuestDB Limited.
- src/pairingTools.ts at the same revision: tool names get_pairing_credentials and wait_for_pairing.

### Our findings

 - The manual config launches npx -y @questdb/mcp-server-questdb with no version. The quick-setup command is also unpinned.
- Notebook tool names are not fixed in pairingTools.ts. The README describes notebook, query, and chart actions executing in the browser session after pairing. A log sample in the README shows the name run_query; that sample was not treated as the full tool list.
- LICENSE appendix reads Copyright 2024 QuestDB Limited. package.json author is QuestDB.

### Not established by this review

 - Not executed: it was not installed or run.
- The setup wizard was not run and no Web Console was paired.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://github.com/questdb/mcp-server-questdb/blob/b80e8557c9b6a492fb17ba626ffb23721fe1e51e/README.md)

DOCUMENTED COMMAND

 npx @questdb/mcp-server-questdb setup Copy command ↗

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - Run the printed setup command. It is an interactive wizard that writes MCP config for the agents it detects.
- When the console requires a specific bridge, the README says to run npx @questdb/mcp-server-questdb@<version> setup instead of the unpinned command.
- Or paste the manual mcpServers block. For an environment without npm registry access, the README describes a release-attached .mjs bundle invoked as node /permanent/absolute/path/mcp-server-questdb-<version>.mjs setup.

### Before you start

 - A running QuestDB Web Console.
- Node and npx for the npm command, or Node >=22 for the standalone bundle described in the README.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

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

### Compatibility

Coding agents named in the README: Claude Code, Codex, Cursor, OpenCode, and Gemini CLI. · A running QuestDB Web Console. Node >=22.0.0 for the standalone bundle, as package.json and the README state for that bundle.

### Implementation

TypeScript

### Local Web Console session

 - The bridge talks to the QuestDB Web Console over a local WebSocket. Default origin is http://127.0.0.1:9000.
- Before notebook, chart, or SQL tools work, the operator accepts a consent prompt using a one-click link or a WebSocket URL plus token from get_pairing_credentials.
- The unpinned npx command fetches the package from the npm registry. The README says the standalone bundle makes no network connections except that local WebSocket.

### Cost model

Apache-2.0. The files read here do not state a fee for the server or for QuestDB.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [QuestDB MCP Server README at b80e8557 ↗](https://github.com/questdb/mcp-server-questdb/blob/b80e8557c9b6a492fb17ba626ffb23721fe1e51e/README.md) Checked 2026-10-15 https://github.com/questdb/mcp-server-questdb/blob/b80e8557c9b6a492fb17ba626ffb23721fe1e51e/README.md Supports: upstreamDescription, install, configExample, limitations, access, bestFor
- [Apache License 2.0 at b80e8557 ↗](https://github.com/questdb/mcp-server-questdb/blob/b80e8557c9b6a492fb17ba626ffb23721fe1e51e/LICENSE) Checked 2026-10-15 https://github.com/questdb/mcp-server-questdb/blob/b80e8557c9b6a492fb17ba626ffb23721fe1e51e/LICENSE Supports: license
- [package.json at b80e8557 ↗](https://github.com/questdb/mcp-server-questdb/blob/b80e8557c9b6a492fb17ba626ffb23721fe1e51e/package.json) Checked 2026-10-15 https://github.com/questdb/mcp-server-questdb/blob/b80e8557c9b6a492fb17ba626ffb23721fe1e51e/package.json Supports: language, compatibility, whySelected
- [pairingTools.ts at b80e8557 ↗](https://github.com/questdb/mcp-server-questdb/blob/b80e8557c9b6a492fb17ba626ffb23721fe1e51e/src/pairingTools.ts) Checked 2026-10-15 https://github.com/questdb/mcp-server-questdb/blob/b80e8557c9b6a492fb17ba626ffb23721fe1e51e/src/pairingTools.ts Supports: whySelected, review.findings

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### CrateDB MCP Server ↗ Python MCP server from the crate organisation that runs SQL against a CrateDB cluster over its HTTP endpoint behind a SELECT-only check, reads table columns, table metadata and cluster health, lists a curated CrateDB documentation index, and fetches documentation pages by link under three permitted URL prefixes.](/mcp-servers/cratedb/)[### Firebolt MCP Server ↗ Go MCP server from Firebolt that connects a client to Firebolt Cloud or Firebolt Core, runs SQL, and exposes Firebolt documentation tools.](/mcp-servers/firebolt/)[### Teradata MCP Server ↗ Explore Teradata tables, profile data and investigate workloads using selectable tool modules.](/mcp-servers/teradata/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
