Skip to main content
Turntable treats AI agents as first-class developers. Two integration surfaces, both derived from the same canonical contract that powers Turntable’s own in-app game generator — they can’t drift apart.

​
MCP server

A remote MCP server (Streamable HTTP, no auth) at: 
https://api.turntable.games/mcp

​
Connect from Claude Code

claude mcp add --transport http turntable https://api.turntable.games/mcp

​
Connect from anything else

Any MCP client that supports Streamable HTTP works — point it at the URL above. The server is stateless: plain JSON-RPC over POST.

​
Tools

ToolWhat it returns
get_sdk_referenceThe game document contract + the full window.Turntable SDK reference — read this before writing a game
get_api_referenceThe REST API reference
search_docs { query }The most relevant doc sections for a query
list_games { limit? }Published games (public metadata)
Action tools (generate_game, publish_game, job status) behind creator API keys are on the roadmap.

​
llms.txt

For agents that read the llms.txt convention:
  • https://api.turntable.games/llms.txt — index + key facts
  • https://api.turntable.games/llms-full.txt — the complete developer reference in one document

​
Writing games with your own Claude calls

If you’re calling the Claude API directly to generate Turntable games, fetch llms-full.txt and include it in your system prompt, then have the model produce a single self-contained HTML document per the game contract. That’s exactly how Turntable’s in-app generator works.