Connects coding agents to a running QuestDB Web Console to create notebook cells, run SQL queries, and build charts.
Also known as questdb/mcp-server-questdb, mcp-server-questdb, @questdb/mcp-server-questdb
- Stars
- 3
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.5.0
- Last commit
- Nov 15, 2026
- License
- Apache-2.0
What is QuestDB Web Console MCP?
QuestDB Web Console connects coding agents to a running QuestDB Web Console to create notebook cells, run SQL queries, and build charts.
Summary generated from the project's README
About QuestDB Web Console MCP server
Connecting coding agents to a running QuestDB Web Console is what this MCP server enables for developers using tools like Claude Code, Cursor, or Gemini CLI. It provides a bridge that allows an AI agent to interact directly with your existing database session through the browser. By using this connection, agents can perform data tasks such as creating notebook cells, executing SQL queries, and building charts without manual intervention.
Setup is handled through an interactive wizard that detects your installed agents and configures them automatically. You can use npx for a quick installation or download a standalone .mjs bundle for offline environments that require strict security policies. The server operates locally, communicating with your Web Console via WebSockets. To ensure security, the agent initiates a pairing process that requires you to accept a consent prompt in your browser using a deep link or a specific token.
What you can do with it
- 1Automated data visualizationAsk your AI agent to generate visual representations of your time-series data directly in the console.
- 2Interactive SQL explorationHave a coding agent execute complex queries against your QuestDB instance to analyze datasets.
- 3Secure offline database managementDeploy the server in restricted environments where network access to registries is prohibited.
Written from the project's README. Every use case is checked against a quote from it.
How to install QuestDB Web Console MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall QuestDB Web Console MCP in Claude Code
$ claude mcp add mcp-server-questdb -- npx -y @questdb/mcp-server-questdbInstall QuestDB Web Console MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server-questdb": {
"command": "npx",
"args": [
"-y",
"@questdb/mcp-server-questdb"
]
}
}
}Install QuestDB Web Console MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server-questdb": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@questdb/mcp-server-questdb"
]
}
}
}Install QuestDB Web Console MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp-server-questdb","type":"stdio","command":"npx","args":["-y","@questdb/mcp-server-questdb"]}'Install QuestDB Web Console MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-server-questdb": {
"command": "npx",
"args": [
"-y",
"@questdb/mcp-server-questdb"
]
}
}
}Install QuestDB Web Console MCP in Codex
$ codex mcp add mcp-server-questdb -- npx -y @questdb/mcp-server-questdbInstall QuestDB Web Console MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-server-questdb] command = "npx" args = ["-y", "@questdb/mcp-server-questdb"]
Install QuestDB Web Console MCP in Gemini CLI
$ gemini mcp add -s user mcp-server-questdb npx -- -y @questdb/mcp-server-questdbInstall QuestDB Web Console MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server-questdb": {
"command": "npx",
"args": [
"-y",
"@questdb/mcp-server-questdb"
]
}
}
}Configuration
CONSOLE_ORIGINQuestDB Web Console origin.
LOG_LEVELLog verbosity. DEBUG adds heartbeats and full tool payloads.
LOG_PATHLog file location. Defaults to a timestamped file under /tmp/questdb-mcp-bridge.
MCP_BRIDGE_PORTFixed WebSocket port for pairing. Auto-allocated when unset.
| Name | Description | |
|---|---|---|
| CONSOLE_ORIGIN | QuestDB Web Console origin. | |
| LOG_LEVEL | Log verbosity. DEBUG adds heartbeats and full tool payloads. | |
| LOG_PATH | Log file location. Defaults to a timestamped file under /tmp/questdb-mcp-bridge. | |
| MCP_BRIDGE_PORT | Fixed WebSocket port for pairing. Auto-allocated when unset. |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubQuestDB MCP Server
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:
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.)
For versions earlier than 0.3.0, use the former package name instead:
npx @questdb/mcp-bridge@<version> setup.
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"]
}
}
}
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-<version>.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:
node /permanent/absolute/path/mcp-server-questdb-<version>.mjs setup
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-<new-version>.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. |
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.
QuestDB Web Console MCP questions
How do I add QuestDB Web Console MCP to Claude Code?
Run claude mcp add mcp-server-questdb -- npx -y @questdb/mcp-server-questdb in your terminal. Add --scope user to make it available in every project.
How do I add QuestDB Web Console MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I set up the QuestDB MCP server?
You can use the interactive wizard by running npx @questdb/mcp-server-questdb setup, which detects your coding agents and writes the necessary configuration.
Can I use this server in an offline or restricted environment?
Yes, you can use a standalone bundle available from GitHub Releases that requires only Node ≥ 22 and makes no network connections except to your local Web Console.
How does the agent connect to my QuestDB session?
The agent uses a pairing process where it provides a deep link or a WebSocket URL and token that you must accept in your QuestDB Web Console.
What happens to pairing credentials if I restart the bridge?
Credentials are held in memory and are unique to each run; restarting the bridge will invalidate old credentials and generate new ones.