Buzzr Sports Engine vs OddsRelay
A side-by-side look at the Buzzr Sports Engine and OddsRelay MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
O
OddsRelaySports · Local subprocess (stdio)Read-only access to OddsRelay odds data for AI assistants: pre-match odds from UK and Irish bookmakers, bet365 included, matched to Betfair, Smarkets, Matchbook and BETDAQ lay prices, plus sport, event, bookmaker and coverage lists. The two tools that spend tokens ask for a quote first and refuse any call above the max_tokens cap you set.60GoodAuth: api key requiredVerdict: choose Buzzr Sports Engine for sports work as a local process; choose OddsRelay for sports as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Buzzr Sports Engine when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
OChoose OddsRelay when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ODDSRELAY_KEY. - You want tools like
sports, events, bookmakers.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | O OddsRelay | |
|---|---|---|
| Category | Sports | Sports |
| Quality signal | 37/100 · Fair | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | ODDSRELAY_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 7 |
| Full listing | View Buzzr Sports Engine | View OddsRelay |
Tools & capabilities
Buzzr Sports Engine tools
No tool names declared yet. Check the project README from the listing page.
OddsRelay tools 7
sportsnoneeventsnonebookmakersnonecoveragenoneoddspriced first, cappedevent_oddspriced first, cappedusagenone
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Buzzr Sports Engine
{
"mcpServers": {
"buzzr-sports-engine": {
"command": "npx",
"args": [
"-y",
"@buzzr/mcp@5.1.0"
]
}
}
}
OddsRelay
{
"mcpServers": {
"oddsrelay": {
"command": "npx",
"args": [
"-y",
"oddsrelay-mcp"
],
"env": {
"ODDSRELAY_KEY": "YOUR_ODDSRELAY_KEY_HERE"
}
}
}
}
Frequently asked questions
Buzzr Sports Engine is categorized under Sports and uses a local stdio subprocess. OddsRelay belongs to Sports and uses a local stdio subprocess. Pick Buzzr Sports Engine for sports work and OddsRelay for sports.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Buzzr Sports Engine has no declared pricing — check the project's own site. OddsRelay is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add buzzr-sports-engine and oddsrelay as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Buzzr Sports Engine has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. OddsRelay has 60/100 (Good) with 1 views, 0 installs and 0 GitHub stars.