Rundida MCP vs Livetennisapi MCP

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

Choose Rundida MCP when:

• You need dedicated capabilities in the Sports domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: list_tools, get_tool, list_marathons.

Explore Rundida MCP Details

Choose Livetennisapi MCP when:

• You need dedicated capabilities in the Sports domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Freemium).
• You have access to required keys: LIVETENNISAPI_KEY.
• Primary tools included: get_live_matches, get_upcoming_matches, get_match.

Explore Livetennisapi MCP Details

Feature & Specification Comparison

Specification	Rundida MCP XWeaponX7 Sports	Livetennisapi MCP livetennisapi Sports
Summary	86 running calculators, 29 marathon events, pace/time/distance calculations, race time predictions (Riegel formula), and heart rate training zones (Karvonen method) for AI agents. No API key required.	Real-time tennis for ATP, WTA, Challenger and ITF — live scores, players, fixtures, model win-probability, and match-winner market prices. 12 read-only tools; a plan wall returns a plain-English explanation instead of a bare 403. Free tier, no card. npx -y livetennisapi-mcp
Category & Scope

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": {
    "xweaponx7-rundida-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rundida/mcp-server"
      ]
    }
  }
}

{
  "mcpServers": {
    "livetennisapi-livetennisapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "livetennisapi-mcp"
      ],
      "env": {
        "LIVETENNISAPI_KEY": "YOUR_LIVETENNISAPI_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons