{"id":"hluaguo-metabase-mcp","name":"metabase-mcp","af_score":63.8,"security_score":47.8,"reliability_score":30.0,"what_it_does":"metabase-mcp is an MCP (Model Context Protocol) server that exposes Metabase functionality to MCP clients/AI assistants. It provides tools for listing databases/tables/fields, executing SQL (with parameter support/templating) and MongoDB-style native queries (with JSON conversion for aggregation pipelines), and managing Metabase cards (questions) and collections.","best_when":"You want an agent-to-database bridge where an MCP client can discover Metabase metadata and execute parameterized queries/cards in a controlled deployment where you manage Metabase credentials and network access.","avoid_when":"You cannot restrict who can call MCP tools (e.g., open HTTP transport without strong network controls), or you need documented idempotency/retry semantics for every operation.","last_evaluated":"2026-03-30T15:20:16.819348+00:00","has_mcp":true,"has_api":false,"auth_methods":["Metabase API key authentication (environment variables)","Session-based authentication via Metabase email/password (environment variables)"],"has_free_tier":false,"known_gotchas":["Be careful when using HTTP/SSE transports—README does not document authentication for the MCP transport itself, so network exposure could allow unintended tool execution.","Some tools perform state changes (creating cards/collections); without explicit idempotency/approval flows, agents may create duplicates on retries.","Query execution tools can be sensitive to SQL dialect/parameter/templating expectations of the connected Metabase databases."],"error_quality":null}