Metarun vs Faf MCP

In-depth architectural comparison of the Metarun and Faf MCP 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?

M

Choose Metarun 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).
• Primary tools included: App Store Connect pricing management, App listing workflows, Screenshot management.

Explore Metarun Details

Choose Faf MCP 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).
• Primary tools included: Persistent project.faf context, Bi-directional context synchronization, AI-readiness scoring.

Explore Faf MCP Details

Feature & Specification Comparison

Specification	M Metarun Developer Tools	Faf MCP Wolfe-Jam Developer Tools
Summary	Run App Store Connect from your IDE: pricing, listings, screenshots, releases, AI visibility.	Universal persistent project context for Cursor, Windsurf, Cline, VS Code, and all MCP-compatible platforms (including Claude Desktop). IANA-registered format (application/vnd.faf+yaml). 17 native tools, AI-readiness scoring.
Category & Scope	Developer Tools

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": {
    "metarun-2": {
      "command": "npx",
      "args": [
        "-y",
        "metarun-2"
      ]
    }
  }
}

{
  "mcpServers": {
    "wolfe-jam-faf-mcp": {
      "command": "bunx",
      "args": [
        "faf"
      ]
    }
  }
}

Related MCP Server Comparisons