QuestDB Web Console MCP Server

Name: QuestDB Web Console MCP Server
Author: questdb

by questdbversion 0.5.0i★ 3iRuns on your computer

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

How to install

What it does

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

Connects Runs on your computer
Account or key No key needed
Category Developer tools

Install

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

Passed 3/3 checks · Runs on your computer

First: which AI do you use?

ClaudeWeb · app · phoneChatGPTWebClaude CodeTerminalCursorCode editorVS CodeCode editorOtherOther apps

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a QuestDB Web Console MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Install Node.js
One time only; it works for every server that needs Node.js
Open the Node.js download page ↗
Done
Sign up and create a QuestDB Web Console MCP Server key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Open the QuestDB Web Console MCP Server site ↗
Done
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Done

Paste these settings and save the file

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

Paste the key only into the app’s field, never into a chat or to anyone

Done

Quit Claude and open it again
Done
Try it
Use QuestDB Web Console MCP Server and tell me what you can do for me, then show me one thing
✓ If Claude says it is using QuestDB Web Console MCP Server or shows a QuestDB Web Console MCP Server tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect QuestDB Web Console MCP Server yet

QuestDB Web Console MCP Server runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect QuestDB Web Console MCP Server

Steps for Claude →You need a QuestDB Web Console MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Steps for Claude Code →You need a QuestDB Web Console MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Steps for Cursor →You need a QuestDB Web Console MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Steps for VS Code →You need a QuestDB Web Console MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Sentry✓ ChatGPT
Compiler Explorer✓ ChatGPT
GitDiagram✓ ChatGPT

Works with Claude Code, with some setup first

You need a QuestDB Web Console MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Install Node.js
One time only; it works for every server that needs Node.js
Open the Node.js download page ↗
Done
Sign up and create a QuestDB Web Console MCP Server key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Open the QuestDB Web Console MCP Server site ↗
Done
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Done

Paste this command and press Enter

claude mcp add --scope user 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

Replace “your-value” with your key before pressing Enter

Paste the key only into the app’s field, never into a chat or to anyone

Done

Type /mcp in Claude Code
You should see QuestDB Web Console MCP Server listed as connected
Done
Try it
Use QuestDB Web Console MCP Server and tell me what you can do for me, then show me one thing
✓ If Claude Code says it is using QuestDB Web Console MCP Server or shows a QuestDB Web Console MCP Server tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a QuestDB Web Console MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Install Node.js
One time only; it works for every server that needs Node.js
Open the Node.js download page ↗
Done
Sign up and create a QuestDB Web Console MCP Server key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Open the QuestDB Web Console MCP Server site ↗
Done
Click this button to open Cursor
Open in Cursor
Cursor asks you to confirm; click Install
Done
Fill in your key
In the QuestDB Web Console MCP Server settings, CONSOLE_ORIGIN, MCP_BRIDGE_PORT, LOG_PATH, LOG_LEVEL is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Done
Open the AI chat in Cursor in Agent mode
Done
Try it
Use QuestDB Web Console MCP Server and tell me what you can do for me, then show me one thing
✓ If Cursor says it is using QuestDB Web Console MCP Server or shows a QuestDB Web Console MCP Server tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a QuestDB Web Console MCP Server key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Install Node.js
One time only; it works for every server that needs Node.js
Open the Node.js download page ↗
Done
Sign up and create a QuestDB Web Console MCP Server key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Open the QuestDB Web Console MCP Server site ↗
Done
Click this button to open VS Code
Open in VS Code
VS Code asks you to confirm; click Install
Done
Fill in your key
In the QuestDB Web Console MCP Server settings, CONSOLE_ORIGIN, MCP_BRIDGE_PORT, LOG_PATH, LOG_LEVEL is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Done
Open the AI chat in VS Code in Agent mode
Done
Try it
Use QuestDB Web Console MCP Server and tell me what you can do for me, then show me one thing
✓ If VS Code says it is using QuestDB Web Console MCP Server or shows a QuestDB Web Console MCP Server tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use QuestDB Web Console MCP Server💬 Discussion →

For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user 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

Claude Desktop (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"
      }
    }
  }
}

Cursor (~/.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"
      }
    }
  }
}

VS Code (mcp.json)

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

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.

At a glance

GitHub stars i: 3
Downloads per weeki: 191/wk
Licence i: Apache-2.0
Connection: Runs on your computer
Transport: stdio
Latest versioni: 0.5.0
Categoryi: Developer tools
Published to registryi: Sep 30, 2026
Code last changedi: Nov 9, 2026
Maker: questdb
Packages: npm: @questdb/mcp-server-questdb
Repo: questdb/mcp-server-questdb
Website: questdb.com
Registry status: Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

Claude Goose LM Studio Msty Studio Cherry Studio Cursor VS Code + GitHub Copilot Visual Studio Windsurf (Devin Desktop)Zed Kiro Cline Continue JetBrains AI Assistant Claude Code Codex CLI Gemini CLI OpenCode nodecode Warp LibreChat Raycast

All apps, with pros and cons →

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 13, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account questdb, which owns the repo
✓ Pass
Still maintained
Code last changed 4 days ago
✓ Pass
Has a licence
Uses Apache-2.0
– 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

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

User reviews

No reviews yet

Compared with others in Developer toolsi

More stars than 81% of the other 5819 servers in this category
Published to the registry more recently than 44% of the other 5819 servers in this category
Basic checks equal to or better than 100% of the other 5819 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 3 of 3 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 4 days ago, and the latest version (0.5.0) reached the registry 44 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: REA, GitHub, Serena MCP: the IDE for your agent

Others in the same category

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

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

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

by morlutoWidely used↓ 388.7K/wk★ 453.3KUpdated yesterday

Runs on your computer

Install

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.4KUpdated 10 days ago

Computer or cloud

Install

Serena MCP: the IDE for your agent

A powerful toolkit for coding, providing semantic retrieval and editing capabilities.

by oraiosWidely used↓ 35.2K/wk★ 31.3KUpdated 6 months ago

Runs on your computer

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

What it does

Install

Install Node.js

Sign up and create a QuestDB Web Console MCP Server key

Open the Claude desktop app’s settings file

Paste these settings and save the file

Quit Claude and open it again

Try it

What you can do instead

Install Node.js

Sign up and create a QuestDB Web Console MCP Server key

Open Terminal

Paste this command and press Enter

Type /mcp in Claude Code

Try it

Install Node.js

Sign up and create a QuestDB Web Console MCP Server key

Click this button to open Cursor

Fill in your key

Open the AI chat in Cursor in Agent mode

Try it

Install Node.js

Sign up and create a QuestDB Web Console MCP Server key

Click this button to open VS Code

Fill in your key

Open the AI chat in VS Code in Agent mode

Try it

Installed on your computer

Values you fill in

At a glance

Which apps can use it

Related guides

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

Discussion

User reviews

Compared with others in Developer toolsi

Common questions

Others in the same category

REA

GitHub

Serena MCP: the IDE for your agent

README from the maker

QuestDB MCP Server

Setup

Quick setup (recommended)

Manual setup

Offline / restricted install (no npx)

Environment variables

Commands

Pairing

Logs

License