Chapter 7

MCP Server

MCP Server

The Groove MCP server turns this documentation into something your AI assistant can call directly.

Instead of reading the reference by hand, you connect an MCP-capable client — Claude Code, Cursor, or any tool that speaks the Model Context Protocol — to the Groove MCP endpoint. Your assistant can then look up any endpoint’s specification, compute and validate signatures, and generate integration code for you.

Access key

Access to the MCP server requires an access key. To obtain one, contact your account manager.

The key is issued per integration and is passed on every request as an Authorization: Bearer header.

What it can do

  • Look up the docs — the full specification of every endpoint documented on this site: parameters, responses, error codes, signature scheme and authentication. All 37 endpoints are covered, from Start Game and the Transaction API through Free Round Bonuses, Games from Sinatra, Tournaments and the appendices.
  • Sign requests — compute the exact X-Groove-Signature for a request, so you can compare it against what your implementation produces.
  • Verify signatures — check whether an inbound signature is valid, using the same logic Groove uses.
  • Generate code snippets — a runnable example for a single endpoint in Go, Java, Python, TypeScript or curl, with the signing and verification step shown explicitly.
  • Generate a full integration — the files of a ready-to-run project (a real /groove entry point, the documented responses and error catalogue, and wallet seams for you to fill in) in Go, Java, Python or TypeScript.

How it works

The MCP server is hosted by the Sinatra gateway and is reached over Streamable HTTP — plain JSON-RPC 2.0 over HTTPS POST. There is nothing to install and nothing to run on your side: you point your MCP client at the endpoint and supply your access key.

POST https://<sinatra-gateway>/mcp
Authorization: Bearer <your-access-key>
Content-Type: application/json

The server is read-only. It answers from an embedded snapshot of this documentation and calls no backend — it never touches your wallet, your players, or any live data.

Next steps

  • Setup — connect your AI client, or call the endpoint directly over HTTP.
  • Available Tools — the full tool list with parameters and examples.