接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
npx -y @questdb/[email protected]Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
CONSOLE_ORIGIN=<value> MCP_BRIDGE_PORT=<value> LOG_PATH=<value> LOG_LEVEL=<value> claude mcp add io.github.questdb-mcp-server-questdb -- npx -y @questdb/mcp-server-questdb@0.5.0在終端機中執行。
{ "mcpServers": { "io.github.questdb-mcp-server-questdb": { "command": "npx", "args": [ "-y", "@questdb/[email protected]" ], "env": { "CONSOLE_ORIGIN": "<value>", "MCP_BRIDGE_PORT": "<value>", "LOG_PATH": "<value>", "LOG_LEVEL": "<value>" } } }}claude_desktop_config.json
遠端 URL 還是本機指令？ 兩種安裝方式的差異
來自發布者
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.
Connects coding agents to a running QuestDB Web Console: notebook cells, SQL queries, and charts.
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:
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@<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.
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"]
}
}
}
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.
Your MCP client runs the bridge for you via the config above, so you rarely invoke it by hand. When you do:
An unknown command exits non-zero with a short error. Pin a version with
npx @questdb/[email protected] start. (Installed on your PATH, the
executable is named mcp-server-questdb.)
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:
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.
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":"..."}]
Apache-2.0.
Connects coding agents to a running QuestDB Web Console: notebook cells, SQL queries, and charts.
{ "mcpServers": { "io.github.questdb-mcp-server-questdb": { "command": "npx", "args": [ "-y", "@questdb/[email protected]" ], "env": { "CONSOLE_ORIGIN": "<value>", "MCP_BRIDGE_PORT": "<value>", "LOG_PATH": "<value>", "LOG_LEVEL": "<value>" } } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式，而不是 PlugMCP 代理伺服器。
發布者列出了以下環境變數：CONSOLE_ORIGIN, MCP_BRIDGE_PORT, LOG_PATH, LOG_LEVEL。
QuestDB Web Console MCP Server 透過 stdio 在本機執行。
上次檢查時間：2026-11-10。 Connects coding agents to a running QuestDB Web Console: notebook cells, SQL queries, and charts.