What is the key difference between Metabase MCP and Nutriref API?

Metabase MCP belongs to the Data Platforms category with local stdio execution, while Nutriref API belongs to the Data Platforms category with local stdio execution.

How do I install Metabase MCP or Nutriref API 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 Nutriref API free or paid?

Metabase MCP operates under a Free / Open Source model (API Key required). Nutriref API operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Metabase MCP lists 6 tools with 4 views and 5 GitHub stars. Nutriref API lists 6 tools with 2 views and 1 GitHub stars.

Can I use both Metabase MCP and Nutriref API 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 Nutriref API

In-depth architectural comparison of the Metabase MCP and Nutriref API 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: 55/100 (Good) | Auth: API Key required

Nutriref API

Data Platforms · Local stdio

Quality: 47/100 (Fair) | Auth: API Key required

Verdict Summary: Choose Metabase MCP if you need specialized Data Platforms tools running via a local process. Choose Nutriref API if your workspace requires Data Platforms integration with local subprocess execution. 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 Nutriref API when:

You need dedicated capabilities in the Data Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: USDA_API_KEY, USDA_BASE_URL, REDIS_URL, X402_NETWORK, X402_RECEIVER_ADDRESS, X402_FACILITATOR_URL, CDP_API_KEY_ID, CDP_API_KEY_SECRET.

Feature & Specification Comparison

Specification	Metabase MCP 1luvc0d3 Data Platforms	Nutriref API Younghef 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.	USDA FoodData Central nutrition for AI agents — pay-per-call in USDC on Base via x402. Four tools (search, detail, compare, recipe) at $0.001–$0.005 per call. No signup, no API keys; MCPB-packaged for one-click install.
Category & Scope

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

Nutriref API Tools (6)

Four endpoints: search, detail, compare, recipe

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"
      }
    }
  }
}

Nutriref API Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "younghef-nutriref-api": {
      "command": "uvx",
      "args": [
        "nutriref-mcp"
      ],
      "env": {
        "USDA_API_KEY": "YOUR_USDA_API_KEY_HERE",
        "USDA_BASE_URL": "YOUR_USDA_BASE_URL_HERE",
        "REDIS_URL": "YOUR_REDIS_URL_HERE",
        "X402_NETWORK": "YOUR_X402_NETWORK_HERE",
        "X402_RECEIVER_ADDRESS": "YOUR_X402_RECEIVER_ADDRESS_HERE",
        "X402_FACILITATOR_URL": "YOUR_X402_FACILITATOR_URL_HERE",
        "CDP_API_KEY_ID": "YOUR_CDP_API_KEY_ID_HERE",
        "CDP_API_KEY_SECRET": "YOUR_CDP_API_KEY_SECRET_HERE"
      }
    }
  }
}

Frequently Asked Questions

Metabase MCP is categorized under Data Platforms and uses a local stdio subprocess. In contrast, Nutriref API belongs to Data Platforms using local stdio subprocess. Select Metabase MCP when you need capabilities focused on data platforms and Nutriref API when you require tools for data platforms.

More alternatives to Metabase MCP More alternatives to Nutriref API Data Platforms category hub

Related MCP Server Comparisons

Popular comparisons with Metabase MCP

Popular comparisons with Nutriref API

Nutriref API vs CorpusIQ