metabase-lite-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| METABASE_API_KEY | Yes | Metabase API key | |
| METABASE_BASE_URL | Yes | Your Metabase instance URL |
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 |
|---|---|
| get_configured_databasesA | List all databases configured in Metabase (id, name, engine) |
| get_database_metadataB | Get schema, tables, and fields for a specific database |
| get_collectionsA | List all collections in Metabase |
| search_cardsA | Search for cards (saved questions) by name or text |
| get_cardA | Get full details of a specific card (saved question) |
| search_dashboardsC | Search for dashboards by name or text |
| get_dashboard_fullB | Get full dashboard details including tabs, dashcards, and parameters |
| run_query_previewA | Execute a read-only query preview and return results. Validates queries are read-only before execution. |
| create_cardB | Create a new card (saved question) in Metabase |
| update_cardA | Update an existing card (saved question). Only provided fields are changed. |
| copy_cardA | Duplicate a card for safe iteration or re-use |
| move_cardA | Move a card to a different collection (card is not deleted) |
| create_dashboardB | Create a new dashboard in Metabase |
| update_dashboardA | Update an existing dashboard. Only provided fields are changed. Uses GET-then-PUT pattern for safety. |
| add_card_to_dashboardA | Place a saved card on a dashboard, optionally in a specific tab and position. Auto-packs if no placement given. |
| remove_card_from_dashboardA | Remove a dashcard from a dashboard (the card itself remains intact) |
| ensure_dashboard_filters_and_mappingsB | Create/update dashboard parameters (filters) and wire them to card variables on specified dashcards |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Each tool targets a distinct resource and action (cards vs dashboards vs databases). The only potential overlap is copy_card vs create_card, but descriptions clearly distinguish duplication from fresh creation. Search vs get follows standard patterns, and all tools have clear boundaries.
All tools follow a consistent verb_noun pattern with snake_case (get_, search_, create_, update_, move_, add_, remove_, ensure_, run_). Even copy_card fits the convention. No camelCase or mixed verb styles.
17 tools is slightly above the typical 3-15 range but is justified for the domain, covering cards, dashboards, and database metadata. Each tool has a legitimate purpose, and the set is not bloated with redundant utilities.
The set covers CRUD for cards (create, read, update, copy/move) and dashboards (create, read, update, add/remove cards, filters), but lacks delete operations for both cards and dashboards. Missing direct get_dashboard (only full) but full supersedes. These are notable gaps that prevent full lifecycle management.