npm @questdb/mcp-server-questdbstdioApache-2.0updated 13d ago
Formerly published as @questdb/mcp-bridge. Every release from 0.3.0 on is published under both names, so existing configs keep working. On an old install, run npx @questdb/mcp-bridge upgrade once ā it migrates your agent configs to the new name.
What can you do with QuestDB Web Console MCP Server?
@questdb/mcp-server-questdb
Formerly published as
@questdb/mcp-bridge. Every release from 0.3.0 on is published under both names, so existing configs keep working. On an old install, runnpx @questdb/mcp-bridge upgradeonce ā it migrates your agent configs to the new name.
An MCP server that connects coding agents (Claude Code, Codex, Cursor, OpenCode ā¦) 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:
npx @questdb/mcp-server-questdb setup
It walks you through two steps:
- Pick agents: multi-select from the ones it detects (Claude Code, Codex, Cursor, OpenCode, Gemini CLI).
- Review settings: optionally override
CONSOLE_ORIGINandMCP_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@<version> 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.)
Manual setup
Or add it to your MCP client's config by hand (e.g. ~/.claude/.mcp.json):
{
"mcpServers": {
"questdb": {
"command": "npx",
"args": ["-y", "@questdb/mcp-server-questdb"]
}
}
}
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. |
MCP_BRIDGE_PORT |
1ā65535 |
auto-allocated | When specified, the bridge uses a fixed port. The port is bound on the first pairing attempt, pairing fails with a bridge_bind_failed error if the port is taken. |
LOG_PATH |
file path | /tmp/questdb-mcp-bridge/<ISO-ts>-<pid>.log |
Override the log file location. |
LOG_LEVEL |
ERROR / WARN / INFO / DEBUG |
INFO |
DEBUG adds heartbeats and full tool payloads. |
Commands
Your MCP client runs the bridge for you via the config above, so you rarely invoke it by hand. When you do:
| Command | Description |
|---|---|
npx @questdb/mcp-server-questdb (no args) |
Start the bridge ā same as start. |
npx @questdb/mcp-server-questdb start |
Start the bridge. |
npx @questdb/mcp-server-questdb setup |
Interactively configure the bridge for your coding agents. |
npx @questdb/mcp-server-questdb --version |
Print the version and exit. Alias: -v. |
npx @questdb/mcp-server-questdb --help |
Print this help and exit. Alias: -h. |
An unknown command exits non-zero with a short error. Pin a version with
npx @questdb/mcp-server-questdb@0.3.0 start. (Installed on your PATH, the
executable is named mcp-server-questdb.)
Pairing
Before any notebook / chart / SQL tool works, your browser has to pair with the bridge. The agent drives the flow.
When the agent needs to pair, it calls get_pairing_credentials and
shows you both:
- A one-click deep link ā open it in the tab showing your Web Console.
- A WebSocket URL + token ā paste into the MCP pill at the bottom of the Web Console if the deep link doesn't land in the right tab.
Either path lands you on a consent prompt. Accept it and the agent's next tool call goes through.
Each bridge run generates a fresh port and pairing token, held only in memory. On restart the old credentials stop working ā the agent will surface new ones the next time it needs to pair.
Logs
The bridge writes to stderr and to a log file. Tail the newest:
tail -F "$(ls -t /tmp/questdb-mcp-bridge/*.log | head -1)"
At default INFO:
2026-05-15T12:29:27.142Z [INFO] tool_call: run_query
2026-05-15T12:29:27.318Z [INFO] tool_result: run_query ok
2026-05-15T12:29:28.011Z [ERROR] tool_result: update_cell internal_error timeout after 15000ms
At DEBUG (full payloads as continuation lines):
2026-05-15T12:29:27.142Z [INFO] tool_call: run_query
2026-05-15T12:29:27.142Z [DEBUG] args: {"query":"SELECT count() FROM trades"}
2026-05-15T12:29:27.318Z [INFO] tool_result: run_query ok
2026-05-15T12:29:27.318Z [DEBUG] content: [{"type":"text","text":"..."}]
License
Apache-2.0.
Install
Add QuestDB Web Console MCP Server to your client. Pick the one you use.
claude mcp add mcp-server-questdb -- npx -y @questdb/mcp-server-questdbcodex mcp add mcp-server-questdb -- npx -y @questdb/mcp-server-questdbamp mcp add mcp-server-questdb -- npx -y @questdb/mcp-server-questdb{
"mcpServers": {
"mcp-server-questdb": {
"command": "npx",
"args": [
"-y",
"@questdb/mcp-server-questdb"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"mcp-server-questdb": {
"command": "npx",
"args": [
"-y",
"@questdb/mcp-server-questdb"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"mcp-server-questdb","command":"npx","args":["-y","@questdb/mcp-server-questdb"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"mcp-server-questdb": {
"command": "npx",
"args": [
"-y",
"@questdb/mcp-server-questdb"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"mcp-server-questdb": {
"command": "npx",
"args": [
"-y",
"@questdb/mcp-server-questdb"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"mcp-server-questdb": {
"command": "npx",
"args": [
"-y",
"@questdb/mcp-server-questdb"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"mcp-server-questdb": {
"type": "local",
"command": "npx",
"args": [
"-y",
"@questdb/mcp-server-questdb"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"mcp-server-questdb": {
"command": {
"path": "npx",
"args": [
"-y",
"@questdb/mcp-server-questdb"
]
}
}
}
}Add to your Zed `settings.json`.
npx -y @questdb/mcp-server-questdbRun `goose configure`, choose **Add Extension ā Command-line Extension**, and paste this command.
Score
39 / 100
Incomplete
- Documentation25/25
- Maintenance19/25
- Trust16/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 5 days ago
- Has a release history
- Repository is not archived
- Licensed Apache-2.0
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint ā no local install
Version history
| Versions | Published |
|---|---|
| 0.3.0Latest | Aug 11, 2026 |