Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldMetabase MCPShortlist candidateRedis MCPMCP100 Recommended
Task fit
Best for
  • Let AI clients query and build against a user's own Metabase instance under existing permissions
  • Metabase users who need to let ai clients query and build against a user's own metabase instance under existing permissions.
  • Inspecting and manipulating Redis strings, hashes, lists, sets, sorted sets, streams, JSON, and search indexes
  • Development workflows using a dedicated local or test Redis database
  • Redis documentation search and operational investigation
Not ideal for
  • The endpoint is instance-specific: https://{your-metabase.example.com}/api/metabase-mcp. Query, SQL, write, and delivery scopes can expose or mutate sensitive analytics content; OAuth never grants more than the connecting user's Metabase permissions.
  • Read-only analytics when write-capable Redis tools cannot be disabled or constrained by ACL
  • Production databases shared with latency-sensitive applications
Avoid when
  • The endpoint is instance-specific: https://{your-metabase.example.com}/api/metabase-mcp. Query, SQL, write, and delivery scopes can expose or mutate sensitive analytics content; OAuth never grants more than the connecting user's Metabase permissions.
  • The Redis credential grants unrestricted access to production keys
  • TLS certificate verification is disabled for a remote Redis connection
  • The agent must not read, overwrite, publish, expire, or delete Redis data
Provenance
Provenance details

First-party MCP

Metabase · Publisher source ↗

First-party MCP

Redis · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Sep 21, 2026

Package: Not documented

Popularity evidence
GitHub starsNot documented

628

GitHub stars · checked 2026-09-24T04:14:26.347000Z

Shared repository stars

49,767

Shared repository stars (not MCP-specific) · checked 2026-10-20

Not documented
Client coverage
Client coverage detailsNot documented
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationOAuth 2.0 through the Metabase instance's embedded OAuth server.Supports Redis username/password URLs, individual credential options, TLS through `rediss://`, CA certificate verification, cluster mode, and Microsoft Entra ID authentication for Azure Managed Redis.
CostThe built-in MCP has no separately documented fee. Metabase has free Open Source and paid hosted/commercial plans; certain AI/usage features have separate usage pricing.The first-party server is open source and the PyPI package documents no MCP usage fee. Redis Cloud, infrastructure, network, container, and AI-client costs remain separate.
PermissionsThe MCP is scoped to the connecting user's Metabase permissions. Capability scopes include content read/write, query execution, SQL execution and delivery writes depending on authorization.The server can read and write Redis keys and data structures, operate streams and pub/sub, manage search indexes, and inspect server information according to the connected Redis user's ACL. Redis ACL configuration is the effective permission boundary.
Data handlingNot documented in the reviewed sources. The reviewed Metabase MCP page does not provide an MCP-specific retention or training statement. Queries can expose data accessible through the user's Metabase permissions.The stdio server runs locally and sends Redis query inputs and returned key values to the connected MCP client. It connects directly to the configured Redis deployment. Credentials can be supplied in a URI, CLI arguments, or environment variables; avoid embedding them in shareable config and logs.
Limitations
Tradeoffs
  • Official Metabase documentation establishes the built-in MCP server and distinguishes it from community implementations. Exact runtime tool inventory/context footprint remains instance/version dependent.
  • The server supports a wide Redis data surface, which is useful but makes the database credential the primary security boundary.
  • Running through uvx is simple but `@latest` is mutable; pin a reviewed release for repeatable deployments.
  • Connection URLs are convenient but can expose usernames and passwords in process arguments or client configuration.
Risk contextDepending on granted scopes, the MCP can run queries/SQL and create, edit or trash Metabase content, potentially exposing sensitive analytics or modifying shared dashboards/questions.A broad Redis tool set can expose or mutate application state, sessions, queues, cached records, and vector data. Use a dedicated database, a narrowly scoped ACL user, verified TLS, pinned releases, and backups. This review does not claim MCP100 execution testing.
Evidence date
Editorial review2026-10-192026-07-24
Candidate evidence2026-10-202026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →