English Français العربية

Betsapi

Official registry Games, sports and entertainment

BetsAPI MCP — wraps BetsAPI (betsapi.com) sports events + odds.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http betsapi 'https://gateway.pipeworx.io/betsapi/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "betsapi": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/betsapi/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-betsapi
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

mcp-betsapi

BetsAPI MCP — wraps BetsAPI (betsapi.com) sports events + odds.

Part of Pipeworx — an MCP gateway connecting AI agents to 1875+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
betsapi_inplayLive in-play sport matches happening right now, with running score and match clock. Pass a sport_id (${SPORT_IDS}). Example: betsapi_inplay({ sport_id: "1", _apiKey: "your-key" })
betsapi_upcomingUpcoming (scheduled) sport events for a sport, optionally for a given day. Pass a sport_id (${SPORT_IDS}) and optionally day=YYYYMMDD. Example: betsapi_upcoming({ sport_id: "1", day: "20260704", _apiKey: "your-key" })
betsapi_event_oddsBookmaker odds for a single event across markets (moneyline, spreads, totals). Odds are deeply nested by market, so the full structure is returned under raw. Get an event_id from betsapi_inplay or betsapi_upcoming first. Example: betsapi_event_odds({ event_id: "12345678", _apiKey: "your-key" })

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "betsapi": {
      "url": "https://gateway.pipeworx.io/betsapi/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/betsapi/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1875+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/betsapi_inplay. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "betsapi": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-betsapi"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-betsapi

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Betsapi data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Frequently asked questions

What is Betsapi?

BetsAPI MCP — wraps BetsAPI (betsapi.com) sports events + odds.

How do I install Betsapi?

It runs as a remote server. In Claude Code: claude mcp add --transport http betsapi 'https://gateway.pipeworx.io/betsapi/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Betsapi need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Betsapi open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Betsapi?

It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.