QuestDB Web Console MCP Server

Name: QuestDB Web Console MCP Server
Author: questdb

by questdbversion 0.5.0i★ –iRuns on your computer

Registry nameio.github.questdb/mcp-server-questdb

Install

Overview

Description from the maker (original English)

Connects coding agents to a running QuestDB Web Console: notebook cells, SQL queries, and charts.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Databases & datasets

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: CONSOLE_ORIGIN, MCP_BRIDGE_PORT, LOG_PATH, LOG_LEVEL

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "questdb": {
      "command": "npx",
      "args": [
        "-y",
        "@questdb/mcp-server-questdb"
      ],
      "env": {
        "CONSOLE_ORIGIN": "your-value",
        "MCP_BRIDGE_PORT": "your-value",
        "LOG_PATH": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add questdb --env CONSOLE_ORIGIN=your-value --env MCP_BRIDGE_PORT=your-value --env LOG_PATH=your-value --env LOG_LEVEL=your-value -- npx -y @questdb/mcp-server-questdb

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "questdb": {
      "command": "npx",
      "args": [
        "-y",
        "@questdb/mcp-server-questdb"
      ],
      "env": {
        "CONSOLE_ORIGIN": "your-value",
        "MCP_BRIDGE_PORT": "your-value",
        "LOG_PATH": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "questdb": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@questdb/mcp-server-questdb"
      ],
      "env": {
        "CONSOLE_ORIGIN": "your-value",
        "MCP_BRIDGE_PORT": "your-value",
        "LOG_PATH": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

CONSOLE_ORIGIN env
QuestDB Web Console origin.
MCP_BRIDGE_PORT env
Fixed WebSocket port for pairing. Auto-allocated when unset.
LOG_PATH env
Log file location. Defaults to a timestamped file under /tmp/questdb-mcp-bridge.
LOG_LEVEL env
Log verbosity. DEBUG adds heartbeats and full tool payloads.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account questdb, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Databases & datasetsi

More stars than 0% of the other 953 servers in this category
Published to the registry more recently than 44% of the other 953 servers in this category
Basic checks equal to or better than 100% of the other 953 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is QuestDB Web Console MCP Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.5.0) reached the registry 37 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Supabase

by supabase

Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.

Computer or cloud★ 2,993Apache-2.0Updated today

Install

MongoDB MCP Server

by mongodb-js

MongoDB Model Context Protocol Server

Runs on your computer★ 1,157Apache-2.0Updated 2 days ago

Install

Elasticsearch MCP Server

by cr7258

MCP server for interacting with Elasticsearch

Runs on your computer★ 315Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

QuestDB MCP Server

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.

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:

Pick agents: multi-select from the ones it detects (Claude Code, Codex, Cursor, OpenCode, Gemini CLI).
Review settings: optionally override 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@ 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@ setup.

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

Offline / restricted install (no npx)

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

Environment variables

Label	Value	Default Value	Description
`CONSOLE_ORIGIN`	origin URL	`http://127.0.0.1:9000`	QuestDB Web Console origin. `127.0.0.1` and `localhost` are interchangeable.
`MCP_BRIDGE_PORT`	`1`–`65535`	auto-allocated	When specified, the bridge uses a fixed port. The port is bound on the first pairing attempt, pairing fails with a `bridge_bind_failed` error if the port is taken.
`LOG_PATH`	file path	`/tmp/questdb-mcp-bridge/ - .log`	Override the log file location.
`LOG_LEVEL`	`ERROR` / `WARN` / `INFO` / `DEBUG`	`INFO`	`DEBUG` adds heartbeats and full tool payloads.

Commands

Your MCP client runs the bridge for you via the config above, so you rarely invoke it by hand. When you do:

Command	Description
`npx @questdb/mcp-server-questdb` (no args)	Start the bridge — same as `start`.
`npx @questdb/mcp-server-questdb start`	Start the bridge.
`npx @questdb/mcp-server-questdb setup`	Interactively configure the bridge for your coding agents.
`npx @questdb/mcp-server-questdb --version`	Print the version and exit. Alias: `-v`.
`npx @questdb/mcp-server-questdb --help`	Print this help and exit. Alias: `-h`.

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

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

Logs

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

License

Apache-2.0.

QuestDB Web Console MCP Server

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Databases & datasetsi

Common questions

Alternatives

Supabase

MongoDB MCP Server

Elasticsearch MCP Server

README from the maker

QuestDB MCP Server

Setup

Quick setup (recommended)

Manual setup

Offline / restricted install (no npx)

Environment variables

Commands

Pairing

Logs

License