Every action that runs over MCP is a tool whose name starts with deck_. For example, deck_get_info is the tool for deck.info. A tool takes the same input as its action and returns the same result. The action reference names the tool of every action.
turboslide mcp --deck decks/my-presentationAdd this command to the server list of your MCP client. The server works on the folder that --deck names.
A hosted studio serves MCP at /mcp with the streamable HTTP transport.
Initialize
Send the JSON-RPC
initializerequest withPOST /mcp. Name the presentation with?deck=<id>. A session that names no presentation reads the example deck, and the server refuses its write tools. A share or publish tool acts on the presentation of the session. If itsidnames another presentation, the server refuses the call with 400. On a hosted studio, sendAuthorization: Bearer <key>. The owner of the API key is the author of every write. Thex-turboslide-authorheader only labels the run.Keep the session
The response carries an
mcp-session-idheader. Send this header on every later request.Call tools
tools/listlists the tools, andtools/callruns one tool.GET /mcpopens the stream of notifications.DELETE /mcpends the session.
Each session is bound to one presentation and one caller. The initialize request sets both.
deck_goto_slide runs the action view.goto in an open page. The page must be visible. It can be the editor, or a /deck, /present or /embed page opened with ?agent=1. A page that is hidden for 10 seconds detaches. The call then returns 404 until the page is visible again.