questdb/mcp-server-questdb

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.
Setup
Quick setup (recommended)
The interactive wizard detects your installed coding agents and
writes the bridge into each one's MCP config:
It walks you through two steps:
1. **Pick agents**: multi-select from the ones it detects (Claude Code,
Codex, Cursor, OpenCode, Gemini CLI).
2. **Review settings**: optionally override CONSOLE_ORIGIN and
MCP_BRIDGE_PORT; press Enter to keep the defaults.
The wizard pins each agent's config to the bridge version that ran it. Your
QuestDB Web Console expects a specific bridge version. If you're on an older
console, run the matching version: npx @questdb/mcp-server-questdb@ setup. The config it writes will launch that same version. (When unsure, pair first; on a version mismatch the agent is told which version to switch to.)
For versions earlier than 0.3.0, use the former package name instead:
npx @questdb/mcp-bridge@ setup.
Manual setup
Or add it to your MCP client's config by hand (e.g. ~/.claude/.mcp.json):
Offline / restricted install (no npx)
Environments that can't run npx (no npm registry access, vet-then-vendor
policies) can use the standalone bundle attached to each supported version's
GitHub Release:
a single self-contained .mjs file needing only Node ≥ 22, making no
network connections except the local WebSocket to your Web Console.
Standalone bundles are available starting with bridge version 0.4.0. All
supported QuestDB Web Console versions request bridge version 0.4.0 or later.
Download the bundle (mcp-server-questdb- .mjs) and
THIRD_PARTY_NOTICES.txt from the release, then move the bundle to a
permanent location before setup—do not configure it from
a downloads or temporary directory—and invoke that exact path:
Setup writes agent configs that launch the bundle file directly (no npx
involved), so moving or deleting that exact path will prevent the MCP server
from starting. To switch versions, put the matching bundle beside the current
one and run node /permanent/absolute/path/mcp-server-questdb- .mjs upgrade;
it re-points your agent configs at the new file while keeping env
settings. If a configured file was already moved, run upgrade from its new
absolute path. setup and upgrade always write the install style of the
binary you run: a bundle writes file-path configs; npx writes npx configs.
Environment variables
| Label | Value | Default Value | Description |
| ----------------- | ----------------------------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| CONSOLE_ORIGIN | origin URL | http://127.0.0.1:9000 | QuestDB Web Console origin. 127.0.0.1 and localhost are interchangeable. |