Integration · Research and analyze

Metabase and Meteor AI agents

Connect your Metabase to a Met: find questions and dashboards, run queries and save questions with the MCP built into your own instance.

Book a demo See every integration

How does Metabase connect to Meteor?

With the Metabase ready connector, your Met works with your own Metabase instance, with the permissions of the person who authorizes the connection. It searches questions, models, metrics and dashboards, browses collections and tables, runs a saved question and runs new queries with Metabase's query language or, if you turn it on, with SQL. It can also save questions, edit dashboards and schedule alerts by email or Slack: SQL and those write actions start turned off, because Metabase marks them as able to overwrite or delete. Your Metabase admin turns the MCP server on; Metabase does not need its own AI provider for this.

What it automates

What a Meteor Met does with Metabase

Answer with a question that already exists

You ask the Met about yesterday's sales. The Met finds the saved question that already measures that in your Metabase, runs it and replies with the result.

Query something new

If there is no saved question, the Met browses the tables and builds the query with Metabase's language, such as an order count by city for the month.

Save what worked

With writing turned on, the Met saves the query as a new question in the collection you name, so the team can use it again.

Schedule an alert

With alerts turned on, the Met schedules a saved question to be sent by email or to Slack when it returns results.

16 tools

Everything your Met can ask Metabase for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`search`	Searches questions, models, metrics, dashboards, collections and tables in your Metabase.
`browse_collection`	Browses a collection and lists its content or its tree of subcollections.
`browse_data`	Browses the databases, schemas and tables connected to your Metabase.
`get_content`	Returns the details of a question, a dashboard or other Metabase content.
`get_parameter_values`	Returns the possible values of a filter or parameter.
`glossary`	Checks the glossary of business terms defined in Metabase.
`run_saved_question`	Runs a saved question and returns its results.
`execute_query`	Runs a new query with Metabase's query language, such as counts, sums and filters.
`execute_sql`	Writes and runs its own SQL on your databases. Metabase marks it as able to overwrite or delete data. Starts turned off.
`question_write`	Creates or edits a saved question in Metabase. Starts turned off.
`dashboard_write`	Creates or edits a Metabase dashboard. Starts turned off.
`collection_write`	Creates or edits a Metabase collection. Starts turned off.
`duplicate_content`	Duplicates a question, a dashboard or other content.
`bookmark_content`	Bookmarks or unbookmarks a collection, dashboard, question or model. Starts turned off.
`alert_write`	Creates or edits an alert that sends a saved question by email or to a Slack channel. Starts turned off.
`subscription_write`	Creates or edits a subscription that delivers data by email or Slack on a schedule. Starts turned off.

The limits

What the Metabase integration does NOT do

We would rather say it here than have you find out during rollout.

It does not see more than the connected person. Every tool runs with that account's permissions, so the Met cannot reach data that person does not see in Metabase.
It does not work if the admin does not turn the server on. The MCP is turned on in Admin, AI, MCP, and stays off if all of Metabase's AI features are disabled.
It does not ask you for confirmation in the chat before writing. Custom SQL and the write tools that Metabase marks as able to overwrite or delete start turned off; the admin decides in Connections which ones to turn on.
It does not draw charts inside WhatsApp. Metabase's inline chart tools are for clients that show them on screen; the Met replies with the data.
It does not pay for your Metabase. The instance is yours and runs on your account; Meteor does not resell the service.

Before you start

What you need to connect Metabase

1

MCP server turned on in your Metabase

An admin of your Metabase goes to Admin, AI, MCP and turns the MCP server on. Metabase's AI features cannot all be disabled.
2

Your Metabase MCP server URL

It is the address of your own instance ending in /api/metabase-mcp. The admin can also copy it in Admin, AI, MCP, Settings, in the MCP server URL field.
3

Connect it in Met

In Met, open Connections → Metabase → Connect and paste that URL. A window of your Metabase opens so you sign in and authorize Met.

Frequently asked questions

Questions about Metabase and Meteor

No. Metabase states that its MCP server only provides the tools: MCP calls do not count against your Metabase AI connection.

Yes, if the SQL action is on and the connected account is allowed to write SQL. Metabase marks it as able to overwrite or delete data, so think it through.

Not necessarily. The MCP server comes with your Metabase, so the tools depend on the version you have installed.

You do, with your own instance and Metabase plan. Met does not charge for the queries your Met makes to Metabase.

Step by step