Metabase
Official Metabase MCP server for searching data, building queries on the semantic layer, and visualizing results through MCP clients.Read full description
metabaseLABSCO SUMMARY
Inheriting the semantic layer is what separates this from pointing a model at a database.
The failure mode of natural-language analytics is a query that runs, returns a number, and means something different from what was asked — wrong join, wrong grain, wrong definition of 'active customer'. A semantic layer is where those definitions already live, and Dot querying through it rather than around it is the reason to prefer this over a generic SQL connector. Zero data retention with the model providers is the other reason it survives a security review.
What it is
Dot's endpoint over their data-analysis agent. Two regional addresses, US and EU. It queries your warehouse through Dot's existing semantic layer and permission model rather than issuing raw SQL.
What you get
Business-data questions — sales analysis, customer analysis, period-over-period comparison — answered with all of Dot's permissions applied. Neither the marketing page nor the developer docs enumerate tool names.
Requirements
OAuth by default, with a browser approval; clients that cannot do OAuth use an X-API-KEY header instead. EU accounts connect to the EU endpoint. Dot documents Zero Data Retention with its LLM providers — prompts are neither stored nor used for training.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Asking a business question directly
Query through the semantic layer so 'revenue' means what your company says it means.
02
Keeping analytics inside existing permissions
Dot's own permission model applies to the agent, so nobody sees more than they should.
03
Connecting from a client without OAuth
Use the API key header for ChatGPT or Raycast rather than going without.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- OAuth by default (browser approval in Claude, Cursor and Windsurf), or an X-API-KEY header for clients that cannot do OAuth; EU accounts use the eu.getdot.ai endpoint
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://app.getdot.ai/ai/mcpRequirements
- OAuth by default (browser approval in Claude, Cursor and Windsurf), or an X-API-KEY header for clients that cannot do OAuth; EU accounts use the eu.getdot.ai endpoint
