redash-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDASH_URL | Yes | Redash server URL, e.g. http://redash | |
| REDASH_API_KEY | Yes | Default API key for Redash (required for stdio; can be overridden via X-REDASH-API-KEY header in HTTP mode) | |
| REDASH_TIMEOUT | No | HTTP timeout in seconds | 30 |
| REDASH_MAX_ROWS | No | Maximum number of rows returned | 1000 |
| REDASH_MCP_HOST | No | Host address for HTTP transport | 127.0.0.1 |
| REDASH_MCP_PORT | No | Port for HTTP transport | 8000 |
| REDASH_POLL_TIMEOUT | No | Maximum wait time for job polling in seconds | 60 |
| REDASH_MCP_TRANSPORT | No | Transport mode: stdio or streamable-http | stdio |
| REDASH_MCP_ALLOWED_HOSTS | No | Comma-separated allowed Host header values for DNS rebinding protection, e.g. redash-mcp:* |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_queriesB | クエリ一覧・検索。qで全文検索、page/page_sizeでページング。 |
| get_queryC | 指定IDのクエリ詳細(api_keyは秘匿済み)。 |
| execute_queryB | 保存済みクエリを実行し行データを返す。max_age=0でキャッシュ回避。 |
| list_data_sourcesC | データソース一覧。 |
| get_data_source_schemaC | データソースのスキーマ(テーブル・カラム)。 |
| list_dashboardsC | ダッシュボード一覧・検索。 |
| get_dashboardC | ダッシュボード1件(id または slug)。ウィジェット構成を含む。 |
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/oceandepthz/redash-api-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server