QuestDB Web Console MCP Server
Connects coding agents to a running QuestDB Web Console: notebook cells, SQL queries, and charts.
Connector by questdb · GitHub account verified by the MCP Registry
Install
Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/questdb-mcp-server-questdb
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.
- Tools
- 2 read · 0 write · 0 deleteRead-only
- Secrets
- None asked for
- Install scripts
- None found
- Runs as
- Node.js package
Tools by what they do 2
Read from the source code; the running server may list different tools.
Read 2 · Look things up without changing anything.
get_pairing_credentialswait_for_pairing
Secrets and settings it asks for
Other settings (environment variables or headers).
CONSOLE_ORIGINLOG_LEVELLOG_PATHMCP_BRIDGE_PORT
Network hosts it talks to 4
github.com· found in codeglama.ai· found in codequestdb.com· found in coderaw.githubusercontent.com· found in code
Files it touches
/tmp/questdb-mcp-bridge- Your home directory (~)
Tools (2)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
get_pairing_credentialsGet the credentials the user needs to pair their browser with this MCP bridge — calling this tool does NOT itself pair anything. It returns a deep_link, ws_url, token, AND a pre-rendered `userMessage` with the exact text to show the user. REQUIRED FLOW — do all three in the defined: (1) call this tool, (2) write a message to the user containing the `userMessage` text (or your own equivalent showing deep_link + ws_url + token), (3) call `wait_for_pairing`. DO NOT skip step (2). Calling `wait_for_pairing` without first showing the credentials guarantees a timeout — the user has no credentials to…
wait_for_pairingPoll for completion of pairing started by `get_pairing_credentials`. PREREQUISITE: you have already written a message to the user containing the deep_link + ws_url + token from `get_pairing_credentials`'s last response. If you have NOT yet shown those credentials, do that first — calling this tool without showing credentials only burns 50 s of polling while the user sees nothing actionable. Blocks for `timeout_ms` (default 50 s, max 50 s — sized to fit under typical MCP client tool-call timeouts). Returns `{paired:true, consoleOrigin, permissions:{grantSchemaAccess,read,write}}` on success, or…
Compare and alternatives
Featured in
Signals
- Stars
- 3
- Forks
- 2
- Open issues
- 0
- Last commit
- Sep 30, 2026 (28 days ago)
- Last release
- Sep 30, 2026 (28 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- Registry name
io.github.questdb/mcp-server-questdb- Version
- 0.5.0
- Auth
- No auth
- Packages
- npm @questdb/mcp-server-questdb
- License
- Apache-2.0
- Repository
- github.com/questdb/mcp-server-questdb
- Website
- questdb.com
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
Cite this page
QuestDB Web Console MCP Server. Agent Mart. https://agentmart.dev/connectors/questdb-mcp-server-questdb (last updated 2026-10-24)