create_card
Create a new question/card in Metabase.
LABSCO SUMMARY
A question can be answered and then left behind as a saved card instead of as a chat message.
The read path is complete enough to start from nothing: find the database, list its tables, read a table's fields, then run the SQL. The write path stops where a reviewer would want it to — create_card and create_collection add new work, and nothing in the list edits or deletes an existing card, so a wrong query becomes an extra card rather than a silent change to someone's dashboard. execute_query takes native SQL against a database_id, so the guardrail is whatever the Metabase credentials in use are permitted to do.
What it is
A server over the Metabase API covering schema discovery, native SQL execution, saved questions and collections.
What you get
- Schema discovery from the top down: list_databases returns what the instance has configured, list_tables returns one database's tables, and get_table_fields returns a table's columns.
- Native SQL: execute_query runs a query against a named database_id and takes native_parameters alongside it.
- Saved questions as callable units: list_cards enumerates them, execute_card runs one with parameters and returns its results, and create_card saves a new query with a name, description, collection and visualization_settings.
- Collections: list_collections reads what exists and create_collection adds one, with a parent_id and a colour.
Requirements
A running Metabase instance and the settings to reach it — METABASE_URL and METABASE_API_KEY, set in the client configuration's env block.
Setup effort
Build from source — git clone https://github.com/cuenca-mx/metabase-mcp-server.git
USE CASES
01
Answering a data question without knowing the schema first
Walk from databases to tables to fields, then write the SQL against what is actually there rather than against what you remember.
02
Leaving a one-off query behind as something the team can rerun
Save the query as a question with its visualization settings, and file it in an existing collection or a new one.
03
Rerunning last month's report with this month's parameters
Find the saved question, then run it with the parameters changed instead of rewriting the SQL.
9 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_collection
Create a new collection in Metabase.
execute_card
Execute a saved Metabase question/card and retrieve results.
execute_query
Execute a native SQL query against a Metabase database.
get_table_fields
Get all fields/columns in a specific table.
list_cards
List all saved questions/cards in Metabase.
Returns: Dictionary containing all cards with their metadata.
list_collections
List all collections in Metabase.
Returns: Dictionary containing all collections with their metadata.
list_databases
List all databases configured in Metabase.
Returns: A dictionary containing all available databases with their metadata.
list_tables
List all tables in a specific database.
BEFORE YOU INSTALL
What to know first
Tools you get
9 tools when we connected.
Requires
- uv on PATH
- Python 3.12+
- a running Metabase instance
- METABASE_URL in your environment
- METABASE_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 9 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/cuenca-mx/metabase-mcp-server.git
cd metabase-mcp-serverMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"metabase": {
"command": "uv",
"args": [
"--directory",
"<YOUR_PATH_TO_PARENT_FOLDER_METABASE_MCP>",
"run",
"app.py"
],
"env": {
"METABASE_URL": "https://metabase.domain.com/",
"METABASE_API_KEY": "<YOUR_METABASE_API_KEY>"
}
}
}
}In --directory, <YOUR_PATH_TO_PARENT_FOLDER_METABASE_MCP> is the metabase_mcp_server folder (with underscores) inside your metabase-mcp-server clone — the folder that holds app.py — so the path ends …/metabase-mcp-server/metabase_mcp_server.
