A side-by-side look at the BALLDONTLIE MCP Server and Odds Api MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose BALLDONTLIE MCP Server for sports work over a hosted endpoint; choose Odds Api 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 BALLDONTLIE MCP Server when
You need dedicated capabilities in the Sports domain.
No tool names declared yet. Check the project README from the listing page.
Odds Api tools
No tool names declared yet. Check the project README from the listing page.
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.
BALLDONTLIE MCP Server is categorized under Sports and uses a remote HTTP/SSE transport. Odds Api belongs to Sports and uses a local stdio subprocess. Pick BALLDONTLIE MCP Server for sports work and Odds Api 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.
BALLDONTLIE MCP Server has no declared pricing — check the project's own site. Odds Api has no declared pricing — check the project's own site. 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 mcp-183 and odds-api-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, BALLDONTLIE MCP Server has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 12 GitHub stars. Odds Api has 43/100 (Fair) with 2 views, 0 installs and 1 GitHub stars.