Can AI agents automate Metabase?
Metabase · hybrid · business-intelligencedashboardsreporting
Metabase is automatable today through its unversioned REST API and, when an admin enables Admin > AI > MCP, through the versioned Agent API that powers the instance MCP server. Programmatic clients send X-API-Key (permissions follow the key's group) or X-Metabase-Session after POST /api/session. JWT Bearer authentication is documented on Pro and Enterprise. Metabase states the general API is not versioned and does not require AI features. Admins enable Agent API under the same Admin > AI > MCP setting as the MCP server. Agent API query pages are 200 rows. A first-party MCP at https://{instance}/api/metabase-mcp is available on all plans when AI features are on and an admin enables the MCP toggle. Connecting to a Metabase that is only reachable on localhost is a client constraint, not a second official MCP product. Clients authenticate with OAuth 2.0 against Metabase's embedded OAuth server, scoped to the connecting person's permissions. Tools include search, construct and execute query, read_resource, create or update question and dashboard, and optional execute_sql (admins can disable it). The MCP query tool pages 200 rows and caps at 2,000. Official CLI mb (@metabase/cli) needs Metabase 58 or later and authenticates with browser login or an API key; git-sync and some other command groups need Pro or Enterprise. This record excludes Tableau, Power BI, Looker, and Qlik Sense. Computer-use viability is unassessed. API and MCP score 8. API is the best path because the general REST surface does not require the AI or MCP admin toggles.
Best path today: api · Overall automatability: 8/10
Modalities
| Modality | Status | Detail |
|---|---|---|
| API | yes | restapi-keysession-tokenjwt coverage: partial · docs |
| SDK | unknown | official: unknown |
| MCP | yes | verdict: official |
| Integrations | unknown | |
| CLI | yes | |
| Extensibility | unknown | webhooks: unknown |
| Data access | export: json · import: json | |
| RPA / UI automation | unknown | web-dom No repeatable UI probe was run. Metabase's REST API, Agent API, instance MCP server, and official CLI cover query and content automation without browser control.
|
| Computer use | unknown | measured verdicts only — "unknown" means not yet probed by us |
Scores
| api | mcp | integrations | cli | rpa | computer use | overall |
|---|---|---|---|---|---|---|
| 8 | 8 | — | 7 | — | — | 8 |
Evidence
| Fact | Tier | Source | Date |
|---|---|---|---|
homepage | declared | source | 2026-09-17 |
license | declared | source | 2026-09-17 |
deployment | declared | source | 2026-09-17 |
modalities.api.exists | declared | source | 2026-09-17 |
modalities.api.kinds[0] | declared | source | 2026-09-17 |
modalities.api.auth[0] | declared | source | 2026-09-17 |
modalities.api.auth[1] | declared | source | 2026-09-17 |
modalities.api.auth[2] | declared | source | 2026-09-17 |
modalities.api.coverage | declared | source | 2026-09-17 |
modalities.api.docs | declared | source | 2026-09-17 |
modalities.mcp.first_party | declared | source | 2026-09-17 |
modalities.cli.exists | declared | source | 2026-09-17 |
modalities.data_access.export[0] | declared | source | 2026-09-17 |
modalities.data_access.import[0] | declared | source | 2026-09-17 |
modalities.agent_docs.llms_txt | declared | source | 2026-09-17 |
verdict.scores.api | declared | source | 2026-09-17 |
verdict.scores.mcp | declared | source | 2026-09-17 |
verdict.scores.cli | declared | source | 2026-09-17 |
freshness.watch[0].url | declared | source | 2026-09-17 |
freshness.watch[1].url | declared | source | 2026-09-17 |
freshness.watch[2].url | declared | source | 2026-09-17 |
freshness.watch[3].url | declared | source | 2026-09-17 |
freshness.watch[4].url | declared | source | 2026-09-17 |
Related tools
Other products in this database that share a category with Metabase.
Last verified 2026-09-17 · volatility high · JSON record