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.

The interactive wizard detects your installed coding agents and writes the bridge into each one's MCP config:
- Pick agents: multi-select from the ones it detects (Claude Code, Codex, Cursor, OpenCode, Gemini CLI).
- Review settings: optionally overrideCONSOLE_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.)

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"] } } }

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 withnpx @questdb/mcp-server-questdb@0.3.0 start. (Installed on yourPATH, the executable is namedmcp-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 callsget_pairing_credentialsand shows youboth:

- A one-click deep link — open it in the tab showing your Web Console.
- A WebSocket URL + token — paste into theMCP pillat 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.

The bridge writes to stderr and to a log file. Tail the newest:

tail -F "$(ls -t /tmp/questdb-mcp-bridge/*.log | head -1)"

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

AtDEBUG(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":"..."}]

Official Airtable MCP server and skills for working with bases, records, workflows, and business operations from AI agents.

MCP Server For Apache Doris, an MPP-based real-time data warehouse.

Official MCP Server from Atlan which enables you to bring the power of metadata to your AI tools

Query Onchain data, like ERC20 tokens, transaction history, smart contract state.

Read and write access to your Baserow tables.

Introspect and query your apps deployed to Convex.

Interact with the data stored in Couchbase clusters using natural language.

Maritime intelligence for tracking vessels, analysing ports, and exploring ship data.