Home › Databases & Data › QuestDB Web Console MCP Server
QuestDB Web Console MCP Server
Connects coding agents to a running QuestDB Web Console: notebook cells, SQL queries, and charts.
Topics: Databases
Connect
Review any command before running it. Package names and URLs come from the server's own registry entry.
Package (npm 0.4.0)
npx -y @questdb/[email protected]
Or add to your MCP client config:
{
"mcpServers": {
"mcp-server-questdb": {
"command": "npx",
"args": [
"-y",
"@questdb/[email protected]"
],
"env": {
"CONSOLE_ORIGIN": "<YOUR_VALUE>",
"MCP_BRIDGE_PORT": "<YOUR_VALUE>",
"LOG_PATH": "<YOUR_VALUE>",
"LOG_LEVEL": "<YOUR_VALUE>"
}
}
}
}
CONSOLE_ORIGIN— QuestDB Web Console origin.MCP_BRIDGE_PORT— Fixed WebSocket port for pairing. Auto-allocated when unset.LOG_PATH— Log file location. Defaults to a timestamped file under /tmp/questdb-mcp-bridge.LOG_LEVEL— Log verbosity. DEBUG adds heartbeats and full tool payloads.
Related servers
MCP Toolbox for Databases
MCP Toolbox for Databases enables your agent to connect to your database.
baserow
Baserow database integration with table search, list, and row create, read, update, and delete capabilities.
postgres-mcp
All-in-one MCP server for Postgres development and operations, with tools for performance analysis, tuning, and health checks
Supabase
MCP server for interacting with the Supabase platform
mcp-server-mysql
MySQL database integration in NodeJS with configurable access controls and schema inspection
mcp-server-qdrant
A Qdrant MCP server
Listed in punkpeye/awesome-mcp-servers (MIT)
Data from the Official MCP Registry