What is the key difference between Lumify and OddsRelay?

Lumify belongs to the Sports category with local stdio execution, while OddsRelay belongs to the Sports category with local stdio execution.

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

Lumify operates under a Free / Open Source model (No auth required). OddsRelay operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Lumify lists 28 tools with 1 views and 9 GitHub stars. OddsRelay lists 7 tools with 1 views and 0 GitHub stars.

Can I use both Lumify and OddsRelay 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

Lumify vs OddsRelay

In-depth architectural comparison of the Lumify and OddsRelay 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

Lumify

Sports · Local stdio

Quality: 61/100 (Good) | Auth: No auth required

OddsRelay

Sports · Local stdio

Quality: 57/100 (Good) | Auth: API Key required

Verdict Summary: Choose Lumify if you need specialized Sports tools running via a local process. Choose OddsRelay if your workspace requires Sports integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Lumify 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).
You have access to required keys: LUMIFY_API_KEY.
Primary tools included: list_sports, list_events, get_event.

Explore Lumify Details

Choose OddsRelay when:

You need dedicated capabilities in the Sports 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: ODDSRELAY_KEY.
Primary tools included: sports, events, bookmakers.

Explore OddsRelay Details

Feature & Specification Comparison

Specification	Lumify lumifyai Sports	O OddsRelay Sports
Summary
Category & Scope	Sports	Sports
Quality signal

Tools & Capabilities Breakdown

Lumify Tools (28)

list_sports

List supported sports with their leagues and current season. Returns each sport's id, slug, name, team-sport flag, and its leagues (each with its current_season). Use list_seasons with current_only=false for historical seasons.

list_events

List events (schedules and live scores), paginated by id (after_id). Filter by sport, league, status, date range, season, or team_id (resolve teams via list_teams / get_team). Returns event id, name, sport/league, start time, status, and venue for each; pass include_scores to also inline participants + scores (intended for small result sets — use get_event for one event's full detail, or query_events for free-text/natural-language filters instead of structured params). include_scores shares the 20/min score-poll budget with get_live_score; prefer the SSE stream for live boards.

get_event

Get a single event with participants and venue. Optionally inline current odds and/or bet intelligence (same 1 credit as the event call). Raises a not-found error if event_id doesn't exist. Use list_events / query_events to discover ids first, or batch_get_events to fetch several ids in one call.

batch_get_events

Get multiple events by id in one call — for agents that already have a list of ids and want full detail for each without one call per event. Max 25 ids. Returns full detail for every id that exists plus a not_found list for any that don't (never billed). Use get_event for a single id, or list_events / query_events to discover ids first.

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

Lumify Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "lumifyai-lumify": {
      "command": "npx",
      "args": [
        "-y",
        "@lumifyai/mcp"
      ],
      "env": {
        "LUMIFY_API_KEY": "YOUR_LUMIFY_API_KEY_HERE"
      }
    }
  }
}

OddsRelay Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "oddsrelay": {
      "command": "npx",
      "args": [
        "-y",
        "oddsrelay-mcp"
      ],
      "env": {
        "ODDSRELAY_KEY": "YOUR_ODDSRELAY_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

Lumify is categorized under Sports and uses a local stdio subprocess. In contrast, OddsRelay belongs to Sports using local stdio subprocess. Select Lumify when you need capabilities focused on sports and OddsRelay when you require tools for sports.

More alternatives to Lumify More alternatives to OddsRelay Sports category hub