MCP Server
Overview
The Groove MCP server exposes this entire documentation set — every endpoint, parameter, response and error code — as tools that an AI coding assistant (Claude Code, Cursor, Copilot, …) can call directly. Instead of reading these pages and hand-writing your integration, you connect your assistant to the MCP once and ask it.
It is a read-only oracle over the Groove integration specs. It serves documentation, computes and checks HMAC-SHA256 signatures, and generates code. It performs no wallet operations, holds no player data, and calls no Groove backend at runtime — so it is safe to point an AI assistant at while you build.
**Always pass `integration: "reverse"`** on every tool call. That scopes every answer to the reverse integration documented on this site.
What you can do with it
| Capability | Tools |
|---|---|
| Look up any endpoint’s full spec — parameters, responses, status codes | get_endpoint, list_endpoints |
| Search the docs by keyword | search_docs |
Compute the Authorization: HMAC-SHA256 Signature=… header for a request |
sign_request |
| Check whether an inbound signature is valid — the request checker | verify_signature |
| Get a runnable example for one endpoint in Go / Java / Python / TypeScript / curl | generate_snippet |
Generate a complete, startable project — /groove entry point, all 7 transaction ops, wallet seams |
generate_integration |
| Inspect the server itself | list_tools, get_server_info |
See the Tools Reference for every parameter, and Example Workflows for worked examples.
Endpoint at a glance
| Property | Value |
|---|---|
| URL | https://<groove-gateway>/mcp |
| Transport | MCP Streamable HTTP — JSON-RPC 2.0 over POST |
| Authentication | Authorization: Bearer <MCP access token> |
| Token lifetime | Constant — the token does not expire |
| Sessions | Stateless — no session id, every call is independent |
| Max body size | 4 MiB (larger requests are rejected with 413) |
| Tools served | 9 |
| Endpoints served | 19 — every reverse-integration page on this site |
Getting your access key
**Contact your Groove account manager** to receive: 1. Your **MCP access token** — the value you put in the `Authorization: Bearer` header. 2. The **gateway base URL** for your environment (staging and production differ). There is no self-service sign-up from the provider side: the token is issued by Groove. Treat it as a **shared secret** — store it in your secret manager, keep it out of source control, and tell your account manager immediately if it leaks so the signing key can be rotated.
How it fits together
Your assistant speaks MCP to the gateway; the gateway authenticates the bearer token and serves the tools in-process. Nothing you ask the MCP touches a live wallet, a player account or a real transaction.
Next steps
| Page | What it covers |
|---|---|
| Setup | Getting your token, the HTTP call, auth header, and client config |
| Tools Reference | Every tool, every parameter, with request and response examples |
| Example Workflows | End-to-end examples: verify a signature, generate a full project |