Claude and the API

mado connects to Claude as a connector (the Model Context Protocol). From a chat you can find a demo, make a personal link for each prospect with their company name in it, see who opened theirs, and rewrite a demo’s text. It is part of the Pro and Team plans.

Connect the Claude app

  1. In Claude, open Customize, then Connectors, then Add custom connector.
  2. Name it mado and paste https://studio.mado.show/api/mcp.
  3. Claude opens mado. Sign in, pick the workspace Claude may use, and click Allow. Only workspaces on Pro or Team can be picked.

The connection acts as you, with your role in that workspace. If your role changes or you leave the workspace, the connection changes with it. Owners and admins see every connected app in Studio, under Settings, API & Claude, and can disconnect any of them.

Connect Claude Code

claude mcp add --transport http mado https://studio.mado.show/api/mcp

Then type /mcp in Claude Code, choose mado and sign in the same way.

What Claude can do

  • list_demos — Your demos, with their status and share links.
  • get_demo — One demo’s words step by step, its end card, and which placeholders it fills, such as {company}.
  • create_personal_link — A tracked link of a published demo for one prospect, with their name filled into the placeholders.
  • list_personal_links — Who opened their link, how far they got, whether they clicked the end card’s button, and when.
  • get_demo_stats — Views, viewers, completion, where viewers leave and end-card clicks.
  • update_demo_text — Change titles, tooltips and end-card text in the draft. Nothing goes live until you publish in Studio.

Claude cannot publish, delete or change pictures, steps or narration. Text it edits lands in the demo’s draft, and you publish it from Studio after looking at it.

Personal demo links

A placeholder like {company|your team} in a demo’s text shows the value from the link, or the text after the bar when there is none. Ask Claude, for example: “Make a link of our onboarding demo for Acme, Globex and Initech, with their names in it.” Each link is tracked: opens show under that name in the demo’s analytics, and Slack or email alerts fire if you set them up. The filled-in values travel in the link and are not stored by mado.

Scripts and other agents

Owners and admins can make an API key in Settings, API & Claude. Send it as Authorization: Bearer to the same URL; never put it in a URL. The tools are the same, called with JSON-RPC:

curl -s https://studio.mado.show/api/mcp \
  -H "Authorization: Bearer $MADO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_demos","arguments":{}}}'

401 means the key or sign-in is missing, wrong or revoked; 402 means the workspace is on Free; 429 means too many requests in a minute.