What is the key difference between Metabase MCP and Avo?

Metabase MCP belongs to the Data Platforms category with local stdio execution, while Avo belongs to the Data Platforms category with cloud HTTP/SSE execution.

How do I install Metabase MCP or Avo in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Metabase MCP and Avo free or paid?

Metabase MCP operates under a Free / Open Source model (API Key required). Avo operates under a Free / Open Source model (OAuth 2.0).

Which MCP server has more tools and community activity?

Metabase MCP lists 6 tools with 3 views and 5 GitHub stars. Avo lists 6 tools with 63 views and 1 GitHub stars.

Can I use both Metabase MCP and Avo together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Metabase MCP vs Avo

In-depth architectural comparison of the Metabase MCP and Avo MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Metabase MCP

Data Platforms · Local stdio

Quality: 53/100 (Good) | Auth: API Key required

Avo

Data Platforms · Remote HTTP/SSE

Quality: 45/100 (Fair) | Auth: OAuth 2.0

Verdict Summary: Choose Metabase MCP if you need specialized Data Platforms tools running via a local process. Choose Avo if your workspace requires Data Platforms integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Metabase MCP when:

You need dedicated capabilities in the Data Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: METABASE_URL, METABASE_API_KEY.
Primary tools included: Metabase API-key authentication, Read, write, and full server modes, SELECT-only SQL guardrails.

Explore Metabase MCP Details

Choose Avo when:

You need dedicated capabilities in the Data Platforms domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
Primary tools included: Search, retrieve, and save tracking-plan items, Branch-based tracking-plan edits, Guided existing-plan design workflow.

Feature & Specification Comparison

Specification	Metabase MCP 1luvc0d3 Data Platforms	A Avo Data Platforms
Summary	MCP server connecting Claude to Metabase with 28 tools for natural language data analysis, dashboard management, SQL queries, and automated insights. Features SQL guardrails, rate limiting, and audit logging.	Define, ship & query your analytics tracking from one source of truth, trusted by humans and agents.
Category & Scope	Data Platforms

Tools & Capabilities Breakdown

Metabase MCP Tools (6)

Metabase API-key authentication

Read, write, and full server modes

SELECT-only SQL guardrails

Batch and chained workflow execution

Tiered rate limiting and audit logging

Optional Anthropic-powered analysis

Avo Tools (6)

Search, retrieve, and save tracking-plan items

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Metabase MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "1luvc0d3-metabase-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ai-1luvc0d3/metabase-mcp"
      ],
      "env": {
        "METABASE_URL": "YOUR_METABASE_URL_HERE",
        "METABASE_API_KEY": "YOUR_METABASE_API_KEY_HERE"
      }
    }
  }
}

Avo Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "avo": {
      "url": "https://mcp.avo.app/mcp"
    }
  }
}

Frequently Asked Questions

Metabase MCP is categorized under Data Platforms and uses a local stdio subprocess. In contrast, Avo belongs to Data Platforms using remote streaming HTTP/SSE transport. Select Metabase MCP when you need capabilities focused on data platforms and Avo when you require tools for data platforms.

More alternatives to Metabase MCP More alternatives to Avo Data Platforms category hub