Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
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 แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
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>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ 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.