Metabase (Unofficial — Community)
A high-performance MCP server for Metabase analytics data access with response optimization and robust error handling.
View in the Claude registry- Brand
- Metabase
- Category
- Data & Analytics
- Primary Subcategory
- Self-Serve BI & Conversational Analytics
Integration details
Description
This MCP server provides AI assistants with optimized access to Metabase analytics data. Features up to 90% token reduction through response optimization, comprehensive error handling with structured responses, and tools for searching, listing, retrieving, and exporting data from Metabase instances. Includes concurrent processing, pagination support, and export capabilities for large datasets. Supports both API key and email/password authentication methods.
- Integration type
- Connector
- Verification status
Verified connector- Platform
- Claude
- Primary Subcategory
- Self-Serve BI & Conversational Analytics
- Secondary Subcategories
- None listed
- Brand
- Metabase
- Access
- Unknown
- First tracked
- 2026-08-13
- Tool count
- 6
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Agent DiscoverabilityClaude Discoverability ScoreMetabase (Unofficial — Community) isn’t discoverable through Claude’s Connector picker
It runs as a local Claude Desktop Extension, so Claude cannot surface or score it there today.
No spam. Unsubscribe any time.
What the current score measures
Remote Connectors Claude can surface from the Connector picker.
Get alerts for Metabase (Unofficial — Community)
Get updates when Metabase (Unofficial — Community)’s Discoverability Score or category rank changes.
6 tools agents can invoke
Metabase (Unofficial — Community) Claude Connector FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve Metabase (Unofficial — Community)'s Claude Connector discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.