mcp-server-questdb
Officialby questdb
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_PATH | No | Override the log file location. | /tmp/questdb-mcp-bridge/<ISO-ts>-<pid>.log |
| LOG_LEVEL | No | Log level: ERROR, WARN, INFO, DEBUG. DEBUG adds heartbeats and full tool payloads. | INFO |
| CONSOLE_ORIGIN | No | QuestDB Web Console origin. Default is http://127.0.0.1:9000. '127.0.0.1' and 'localhost' are interchangeable. | http://127.0.0.1:9000 |
| MCP_BRIDGE_PORT | No | 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. Leave unset for auto-allocation. |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/questdb/mcp-server-questdb'
If you have feedback or need assistance with the MCP directory API, please join our Discord server