Metabase
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level: debug, info, warn, error, fatal (debug enables pretty JSON) | info |
| CACHE_TTL_MS | No | Cache time-to-live in milliseconds (default: 10 minutes) | 600000 |
| METABASE_URL | No | The URL of your Metabase instance | |
| EXPORT_DIRECTORY | No | Export location for exported datasets | ~/Downloads/Metabase |
| METABASE_API_KEY | No | Your Metabase API key (recommended authentication method) | |
| METABASE_PASSWORD | No | Your Metabase password (alternative authentication method) | |
| REQUEST_TIMEOUT_MS | No | Request timeout in milliseconds (default: 10 minutes) | 600000 |
| METABASE_USER_EMAIL | No | Your Metabase user email (alternative authentication method) | |
| METABASE_READ_ONLY_MODE | No | Restrict execute tool to SELECT queries only (blocks INSERT, UPDATE, DELETE, DROP, etc.) | true |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search across all Metabase items using native search API. Supports cards, dashboards, tables, collections, databases, and more. Use this first for finding any Metabase content. Returns search metrics, recommendations, and clean results organized by model type. |
| retrieveA | Fetch additional details for supported models (Cards, Dashboards, Tables, Databases, Collections, Fields). Supports multiple IDs (max 50 per request) with intelligent concurrent processing and optimized caching. Includes table pagination for large databases exceeding token limits. |
| listA | Fetch all records for a single Metabase resource type with highly optimized responses for overview purposes. Retrieves complete lists of cards, dashboards, tables, databases, or collections. Returns only essential identifier fields for efficient browsing and includes intelligent caching for performance. Supports pagination for large datasets exceeding token limits. |
| executeA | Unified command to execute SQL queries or run saved cards against Metabase databases. Use Card mode when existing cards have the needed filters. Use SQL mode for custom queries or when cards lack required filters. Returns up to 500 rows per request - for larger datasets, use the export tool instead. SECURITY WARNING: SQL mode can execute ANY valid SQL including destructive operations (DELETE, UPDATE, DROP, TRUNCATE, ALTER). Use with caution and ensure appropriate database permissions are configured in Metabase. Note: When Read-Only Mode is enabled, write operations will be rejected with an error. |
| export | Unified command to export large SQL query results or saved cards using Metabase export endpoints (supports up to 1M rows). Returns data in specified format (CSV, JSON, or XLSX) and automatically saves to Downloads/Metabase folder. |
| clear_cacheA | Clear the internal cache for stored data. Useful for debugging or when you know the data has changed. Supports granular cache clearing for both individual items and list caches. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| execute_card | Execute a Metabase card/question with intelligent parameter handling and display results |
| export_card | Export a Metabase card/question to file with intelligent parameter handling and troubleshooting |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a clearly distinct operation: cache clearing, searching, listing, detail retrieval, and query execution. While search and list both return content, search is for discovery across item types and list is for complete overviews of a single resource type, so there is no real ambiguity.
Most tool names are single-word lowercase verbs (search, retrieve, list, execute), which is consistent and predictable. clear_cache deviates slightly by using snake_case and a compound verb-noun structure, but the pattern is still readable and does not cause confusion.
Five tools is a well-scoped count for a Metabase-focused server. Each tool covers a necessary aspect of the read/query workflow without redundant utilities or overwhelming breadth.
The core discovery and querying workflows are covered well, but the execute tool explicitly directs users to an 'export tool' for larger datasets that is not present in this server. There are also no create/update/delete operations, though that may be intentional for a read-oriented server; the missing export tool is a notable gap.