Skip to Content
TurboslideDocumentation
MCP in AgentsContents

MCP

Use Turboslide's actions as MCP tools, over standard input and output from the command line or over HTTP from a hosted studio.

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.

Over standard input and output

Shell
turboslide mcp --deck decks/my-presentation

Add this command to the server list of your MCP client. The server works on the folder that --deck names.

Over HTTP

A hosted studio serves MCP at /mcp with the streamable HTTP transport.

  1. Initialize

    Send the JSON-RPC initialize request with POST /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 its id names another presentation, the server refuses the call with 400. On a hosted studio, send Authorization: Bearer <key>. The owner of the API key is the author of every write. The x-turboslide-author header only labels the run.

  2. Keep the session

    The response carries an mcp-session-id header. Send this header on every later request.

  3. Call tools

    tools/list lists the tools, and tools/call runs one tool. GET /mcp opens the stream of notifications. DELETE /mcp ends the session.

Each session is bound to one presentation and one caller. The initialize request sets both.

Driving an open page

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.