How to connect the BetsBeats MCP server to Windsurf

Windsurf reads MCP servers from mcp_config.json. Add a betsbeats entry under mcpServers with serverUrl https://api.betsbeats.com/mcp, save the file and refresh the MCP list in Cascade. No key is needed. Windsurf's documentation has moved recently, so the file path below comes from setup guides and should be confirmed in the app.

Checked against each client's documentation on 1 November 2026. Menus move between releases, so the endpoint URL is the one part that does not change.

Steps

1. Open Cascade and go to its MCP settings, which can open the config file. The usual path is ~/.codeium/windsurf/mcp_config.json.
2. Add the betsbeats entry shown below, keeping existing servers.
3. Save the file, then refresh or restart so Windsurf reloads its servers.
4. Open Cascade and run the test prompt below.

Config

{
  "mcpServers": {
    "betsbeats": {
      "serverUrl": "https://api.betsbeats.com/mcp"
    }
  }
}

Windsurf's docs now redirect to a new site that did not show the remote-server format when we checked. The serverUrl key and the path above are what several current third-party guides give. If Windsurf reports an invalid config, open the file from its MCP settings and compare.

Test it

Ask your assistant to use a tool whose answer you can check by hand.

Use the BetsBeats MCP server to convert odds of +150 to decimal and implied probability.

A working connection returns decimal odds of 2.5 and an implied probability of 0.4, which is 40 percent, from the convert_odds tool.

Questions

serverUrl or url?

The guides we checked use serverUrl for a remote server instead of command, so use that key.

Do I need OAuth or a header?

No. The endpoint is public, so there is no OAuth step and no header.

Other clients

• Claude Desktop
• Claude Code
• ChatGPT
• Cursor
• VS Code (GitHub Copilot)