Let your agent keep score

Create a two-team scoreboard, update the score, and give everyone a link to follow along.

Connect your agent

Works with MCP clients and the REST API. Free boards include branding and 50 total spectator views.

Example scoreboard: Foxes 24, Owls 21
Actual scoreboard with Pro team colors. Your agent starts a new board at zero; people can customize it in the scoring controls.

Connect with MCP

Add this remote Streamable HTTP server in your agent client. Choose OAuth, then sign in to your Scorekeeper account and approve the requested permissions.

https://www.scorekeeper.co/api/mcp

Your client starts the connection. Opening the server address in a browser does not connect it. An existing non-guest Scorekeeper account is required. Manage your account or make a scoreboard yourself.

Try: “Create a scoreboard called Friday trivia for Foxes and Owls. Then give me the spectator link.”

The five tools create, read, list, update and hand off generic two-team scoreboards. They do not control tournament brackets, timers, sport-specific rules or billing.

Prefer a guest REST request?

A short-lived guest bearer token can create one board without an account. Save the token securely: it expires after seven days. Keep tokens out of public replies, links and browser code.

curl -X POST https://www.scorekeeper.co/api/v1/agent-sessions
curl -X POST https://www.scorekeeper.co/api/v1/scoreboards \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"requestId":"friday-trivia-001","title":"Friday trivia","teams":[{"name":"Foxes"},{"name":"Owls"}]}'

The response contains stable team IDs, a revision, spectator and overlay links. Use the spectator link for the audience. Management and handoff links are private.

Read the OpenAPI contract · Agent instructions and update examples

Keep every point safe

Send a unique requestId for each intended change. Retry the same ID with exactly the same body after a timeout; a changed body returns idempotency_conflict. Read the board first and send its expectedRevision when updating.

On revision_conflict, read the current board and decide whether your change is still needed before sending a new request. Use team IDs from the response, not array position. A 401 means reconnect or obtain a new guest session; it does not recover an expired guest connection. A 429 means wait for Retry-After.

Requests are limited to 120 per minute, including up to 60 writes; guest session creation has a separate lower limit. Free accounts can keep up to 10 boards; guests one. Current returned limits are authoritative. Have a person claim the board before the guest token expires if they need to continue scoring.

Hand the game to a person

Ask your agent to hand off the scoreboard. It returns a private link that opens the real scoring controls. Account handoff opens the owner’s controls. Guest handoff creates a private claim link valid for 15 minutes. Claiming transfers the board to the person and ends guest control. They can continue in the same browser without signing up, or sign in first for access across devices. The spectator link stays separate, so the audience cannot change the score.

Open the scoreboard maker · Get help connecting · Privacy · Terms