Get started free
All integrations

Metabase integration

Metabase is an open-source business intelligence platform. The REST API exposes the same operations the web UI does: explore databases and tables, build and run questions (cards), assemble dashboards, organize content in collections, manage users and permissions, and execute ad-hoc native or MBQL queries through the dataset endpoint.

25 toolsAPI keyAPI docs

Common Metabase use cases

  • build data dictionary
  • browse saved questions
  • rename a saved question
  • verify api key identity
  • add cards to a dashboard
  • fetch user details by id
  • inspect a saved question
  • purge a card permanently
  • scaffold a new dashboard
  • browse the collection tree

What you can do with Metabase

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Card, 5 operations

  • POSTcreate_card

    Create a new card (question, model, or metric). Provide the underlying dataset_query, the desired display, and the visualization_settings.

  • DELETEdelete_card

    Permanently delete a card by numeric ID. This is a hard delete - the card cannot be recovered.

  • GETget_card

    Get a single card (question, model or metric) by numeric ID. Returns name, dataset_query, visualization settings, parameters, and metadata.

  • GETlist_cards

    List Metabase cards (questions, models and metrics). Supports filtering by ownership, archive status, bookmarks, and parent model.

  • PUTupdate_card

    Update an existing card. All fields are optional - supply only the ones you want to change.

Dashboard, 5 operations

  • POSTcreate_dashboard

    Create a new empty dashboard. Use update_dashboard afterwards to add tabs, parameters, and dashcards.

  • DELETEdelete_dashboard

    Permanently delete a dashboard by numeric ID. To soft-delete instead, archive it via update_dashboard.

  • GETget_dashboard

    Get a dashboard by numeric ID, including its dashcards, tabs, parameters, and metadata.

  • GETlist_dashboards

    List all non-archived dashboards visible to the authenticated user. Returns dashboard IDs, names, descriptions, and parent collection IDs.

  • PUTupdate_dashboard

    Update an existing dashboard. Rename, move between collections, archive, edit parameters, or replace the dashcards/tabs layout.

User, 3 operations

  • POSTcreate_user

    Create a new Metabase user (superuser scope). The new user receives an invitation email with a setup link.

  • GETget_user

    Get a specific Metabase user by numeric ID. Returns the full user profile including email, name, group memberships, and login metadata.

  • GETlist_users

    List Metabase users (superuser scope). Returns user IDs, emails, names, group memberships, and active flag.

Collection, 2 operations

  • POSTcreate_collection

    Create a new collection (folder). Optionally place it under a parent collection.

  • GETlist_collections

    List Metabase collections (folders that organize cards and dashboards).

Database, 2 operations

  • GETget_database

    Get a Metabase database connection by numeric ID. Returns engine, host, db settings, and tables when requested.

  • GETlist_databases

    List all configured database connections in the Metabase instance. Returns database IDs, names, engines, and basic metadata.

Card query, 1 operation

  • POSTrun_card_query

    Execute the query attached to a card and return its results as JSON. Optionally pass parameter values, bypass the cache, or attribute the run to a specific dashboard.

Collection items, 1 operation

  • GETlist_collection_items

    List the items (cards, dashboards, sub-collections, models, ...) inside a specific collection.

Content, 1 operation

  • GETsearch

    Search across Metabase content (dashboards, cards, models, tables, collections, ...).

Current user, 1 operation

  • GETget_current_user

    Get the profile of the currently authenticated Metabase user. Returns user ID, email, first/last name, common name, and superuser flag.

Database metadata, 1 operation

  • GETget_database_metadata

    Get the full metadata of a database, including all tables, fields, foreign-key relationships and field-level metadata.

Dataset query, 1 operation

  • POSTrun_dataset_query

    Execute an ad-hoc native SQL or MBQL query without saving it as a card.

Table, 1 operation

  • GETlist_tables

    List all tables visible to the authenticated user across all databases. Returns table IDs, names, schemas, and parent database IDs.

Table query metadata, 1 operation

  • GETget_table_query_metadata

    Get metadata about a table useful for running queries. Returns the parent database, all fields with their types, foreign-key references, and field values.

Use Metabase from Claude Code, Cursor or Codex

Connect Metabase in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Metabase operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Metabase

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Metabase once

    Add your Metabase connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Metabase integration FAQ

What can you do with the Metabase integration?
LiveContext exposes 25 operations on Metabase, covering card, dashboard, user and collection. Common uses include build data dictionary, browse saved questions and rename a saved question.

Popular integrations

Browse the whole catalog