QuestDB Web Console MCP Server

QuestDB MCP Server

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.

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:

Codex, Cursor, OpenCode, Gemini CLI).

1. Pick agents: multi-select from the ones it detects (Claude Code,

MCPBRIDGEPORT; press Enter to keep the defaults.

1. Review settings: optionally override CONSOLE_ORIGIN and

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@ 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.)

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

Environment variables

Commands

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/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 getpairingcredentials and shows you both:

Shortened. The full README is on GitHub.