November 2026 Summaries

Metabase’s MCP server enables AI assistants such as Claude, ChatGPT, Cursor, Codex, and custom in-app tools to answer questions using company data while enforcing each signed-in user’s existing Metabase permissions. Available on all Metabase plans, including Open Source, it exposes existing database connections, data models, metrics, definitions, and permissions so organizations do not need to build separate SQL tools or metric catalogs. MCP clients connect through OAuth, while custom applications can use OAuth on any plan or JWT-based headless access on Pro and Enterprise, with access tokens scoped to the user and limited to requested capabilities. Assistants can search content, inspect metadata and glossary definitions, run structured queries, and, where permitted, execute raw SQL, create content, or display inline charts linked back to Metabase for verification. The guidance emphasizes defining and documenting shared metrics and business terms, limiting assistants to read-only scopes when appropriate, using read-only database credentials, and controlling tool access through permissions, group settings, consent scopes, auditing, and activity logs.