Metabase vs US Macro

In-depth architectural comparison of the Metabase and US Macro 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.

Which MCP Server Should You Choose?

Choose Metabase when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Metabase Details

Choose US Macro when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore US Macro Details

Feature & Specification Comparison

Specification	Metabase Developer Tools	US Macro Developer Tools
Summary	Lets AI clients search, explore, query, and visualize data in a Metabase instance.	US macroeconomic data from FRED: inflation, employment, growth, housing, rates, recession signals.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "metabase": {
      "url": "https://www.metabase.com"
    }
  }
}

{
  "mcpServers": {
    "us-macro": {
      "command": "uvx",
      "args": [
        "us-macro-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons