Metabase MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_MODE | No | Server mode: read, write, or full | read |
| LOG_LEVEL | No | Logging: debug, info, warn, error | info |
| METABASE_URL | Yes | Your Metabase instance URL | |
| METABASE_API_KEY | Yes | Metabase API key | |
| METABASE_TIMEOUT | No | Request timeout (ms) | 30000 |
| ANTHROPIC_API_KEY | No | Enables NLQ and insight tools | |
| METABASE_MAX_ROWS | No | Max rows returned per query | 10000 |
| RATE_LIMIT_REQUESTS_PER_MINUTE | No | Rate limit threshold | 60 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_dashboardsA | List all dashboards in Metabase |
| get_dashboardA | Get dashboard details including its cards |
| list_cardsA | List questions/cards in Metabase. Returns up to 100 cards. Use search_content for discovery. |
| get_cardA | Get details of a specific question/card |
| execute_cardB | Execute an existing question/card and get results |
| list_databasesA | List all connected databases |
| get_database_schemaA | Get tables and columns for a database |
| execute_queryB | Execute a SQL query (SELECT statements only) |
| search_contentA | Search across Metabase content (dashboards, cards, collections) |
| get_collectionsA | List all collections |
| batch_executeA | Execute multiple read operations in a single call. Supports up to 20 operations run in parallel. Supported tools: get_dashboard, get_card, execute_card, get_database_schema, execute_query, search_content, list_dashboards, list_databases, list_cards. |
| run_workflowA | Execute a multi-step workflow pipeline in a single call. Steps run sequentially and can reference previous step results using "$stepName.path" syntax. Example: search for dashboards, then get details of the first result, then execute its cards — all in one call. Max 10 steps. |
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/1luvc0d3/metabase-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server