Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
BetsAPI MCP — wraps BetsAPI (betsapi.com) sports events + odds.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
PIPEWORX_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://gateway.pipeworx.io/betsapi/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"betsapi": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-betsapi"
],
"env": {
"PIPEWORX_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add --transport http betsapi https://gateway.pipeworx.io/betsapi/mcpclaude mcp add betsapi --env PIPEWORX_API_KEY=your-value -- npx -y @pipeworx/mcp-betsapiFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"betsapi": {
"url": "https://gateway.pipeworx.io/betsapi/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"betsapi": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-betsapi"
],
"env": {
"PIPEWORX_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"betsapi": {
"type": "http",
"url": "https://gateway.pipeworx.io/betsapi/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"betsapi": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-betsapi"
],
"env": {
"PIPEWORX_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://gateway.pipeworx.io/betsapi/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account pipeworx-io, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: PIPEWORX_API_KEY
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 7 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Fomu MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
BetsAPI MCP — wraps BetsAPI (betsapi.com) sports events + odds.
Part of Pipeworx — an MCP gateway connecting AI agents to 1863+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
| Tool | Description |
|---|---|
betsapi_inplay | Live 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_upcoming | Upcoming (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_odds | Bookmaker 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" }) |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": { "betsapi": { "url": "https://gateway.pipeworx.io/betsapi/mcp" } } }
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 1863+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.
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":"..."}.
@pipeworx/mcp-betsapi is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/betsapi/mcp endpoint shown above. It needs network access; there is no offline mode.
{
"mcpServers": { "betsapi": { "command": "npx", "args": ["-y", "@pipeworx/mcp-betsapi"] } } }
Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": " " } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.
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.
MIT