What is the key difference between Metabase and Specrun?

Metabase belongs to the Developer Tools category with local stdio execution, while Specrun belongs to the Developer Tools category with local stdio execution.

How do I install Metabase or Specrun 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 and Specrun free or paid?

Metabase operates under a Free / Open Source model (No auth required). Specrun operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Metabase lists 0 tools with 0 views and 49,126 GitHub stars. Specrun lists 0 tools with 0 views and 5 GitHub stars.

Can I use both Metabase and Specrun 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 vs Specrun

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

Developer Tools · Local stdio

Quality: 37/100 (Fair) | Auth: No auth required

Specrun

Developer Tools · Local stdio

Quality: 37/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Metabase if you need specialized Developer Tools tools running via a local process. Choose Specrun if your workspace requires Developer Tools 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 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 Metabase Details

Choose Specrun 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 Specrun Details

Feature & Specification Comparison

Specification	Metabase Developer Tools	S Specrun Developer Tools
Summary	Lets AI clients search, explore, query, and visualize data in a Metabase instance.	MCP server that converts OpenAPI specs into tools which can query API endpoints
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Metabase Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Specrun Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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 Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "metabase": {
      "command": "npx",
      "args": [
        "-y",
        "metabase"
      ]
    }
  }
}

Specrun Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "specrun": {
      "command": "npx",
      "args": [
        "-y",
        "with"
      ]
    }
  }
}

Frequently Asked Questions

Metabase is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Specrun belongs to Developer Tools using local stdio subprocess. Select Metabase when you need capabilities focused on developer tools and Specrun when you require tools for developer tools.

More alternatives to Metabase More alternatives to Specrun Developer Tools category hub