MCP + Skill — live

Your AI copilot: an MCP and a Skill.

Two tools, one job — turn “build me a betslip” into correct, idiomatic BetChain code. The Skill knows how to build the BetChain way; the MCP knows the exact, current SDK. Both use the same license key — no extra credentials.

Get access Jump to setup

BetChain MCP

Knows the SDK. Always current.

Every SDK method, type and parameter — always current
Tells your agent where each value comes from, so it never invents ids
Plugs into any client that speaks the MCP protocol

BetChain Skill

Builds the BetChain way.

The BetChain conventions, gotchas and hasError handling baked in
Recipes for betslip, live odds, casino and CMS
Works in Claude Code, Cursor and your own agents

Prerequisites

One license key gates everything

The MCP and the Skill authenticate with the same license key as the npm install — there is nothing new to request. Generate it in the account page after signing in, then export it so your assistant and shell can read it.

.sh

export BETCHAIN_LICENSE_KEY=your-license-key

Same key as the package installIf you already configured the SDK on this machine, you can reuse the exact same BETCHAIN_LICENSE_KEY. See the installation guide.

Step 1

Connect the MCP

Point your AI client at the BetChain MCP endpoint over HTTP, authenticating with your license key.

.sh

claude mcp add --transport http betchain https://sdk.betconstruct.com/mcp \
  --header "Authorization: Bearer ${BETCHAIN_LICENSE_KEY}"

Verify it registered:

.sh

claude mcp list

Step 2

Install the Skill

Download the licensed Skill bundle and extract it into your assistant's skills directory.

.sh

curl -H "Authorization: Bearer ${BETCHAIN_LICENSE_KEY}" https://sdk.betconstruct.com/skill -o betchain-skill.tar.gz
mkdir -p ~/.claude/skills && tar -xzf betchain-skill.tar.gz -C ~/.claude/skills

It lands at ~/.claude/skills/betchain/SKILL.md. Restart your assistant so it re-scans the skills folder, and the Skill is ready.

Step 3

Use them together

With both installed, just ask in plain language. The Skill decides how to build; the MCP supplies the exact methods, types and ids — so you get correct, idiomatic code, not guesses.

›Build a betslip with cashout for the Swarm SDK.›Subscribe to live football odds and render a market.›Where do I get selectionId, and how do I place the bet?›Wire up login with 2FA and session restore.

Troubleshooting

Common issues

401 Unauthorized from the MCP or Skill

The license key is missing, wrong, expired or revoked. Make sure BETCHAIN_LICENSE_KEY is exported in the same shell, and copy a fresh key from your account page — keys expire after 30 days.

The MCP does not connect

Confirm the transport is http and the URL is exactly https://sdk.betconstruct.com/mcp, then run the verify command. In Cursor, check the Authorization header is present in mcp.json and that your shell expanded the variable.

The Skill is not picked up

It must extract into ~/.claude/skills (a betchain/ folder with SKILL.md inside). Re-run the install, then restart your assistant so it re-scans the skills directory.

Ready to let your agent build?

Get access