← Registry tracker

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
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
Category
Data & Analytics

The broad Category that contains the Primary Subcategory.

Primary Subcategory
Self-Serve BI & Conversational Analytics

The Primary Subcategory used for this profile’s headline score.

Secondary Subcategories
None listed

Other Subcategories where the Integration is listed.

Access
Unknown
First tracked
2026-08-13
Tool count
6
Geography
US

Claude Discoverability Score

Metabase (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.

No spam. Unsubscribe any time.

What the current score measures

Claude showing a list of relevant Connectors in a conversation

Remote Connectors Claude can surface from the Connector picker.

How this score is measured
Adobe Customer Journey Analytics11/100
Aleph7/100
Amplitude17/100
BasedashPending VerificationGet notified
BEEMPending VerificationGet notified
Metabase (Unofficial — Community)Local Extension · Not scored
Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.Read guide
Tools

6 tools agents can invoke

Metabase (Unofficial — Community) FAQ
How do I improve a Verified connector's 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.