> ## Documentation Index
> Fetch the complete documentation index at: https://developers.demosmith.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect an AI assistant

> Ask Claude, ChatGPT, Claude Code or Cursor to make demo videos for you.

Demosmith runs an MCP server, so an AI assistant can check a task, create a demo, follow it and hand you the video link, all from a conversation.

```text MCP server URL theme={null}
https://mcp.demosmith.ai/mcp
```

Assistants that support sign-in (Claude, ChatGPT, Claude Code) ask you to sign in to Demosmith and allow access. Tools without sign-in (Cursor) use an [API key](https://developers.demosmith.ai/authentication.md#api-keys). Either way, demos are created in your organization and use your plan's minutes.

> [tab] Claude
>
> 1. In Claude, open **Customize → Connectors**, choose **Add**, then **Add custom connector**.
>
> 2. Name it **Demosmith** and paste the MCP server URL.
>
> 3. Select **Connect**, sign in to Demosmith, and allow access.
>
> > [!NOTE]
> >
> > On a Claude Team or Enterprise plan, only an organization owner can add a custom connector.

> [tab] ChatGPT
>
> 1. In ChatGPT, open **Plugins**, choose **Add**, then **Add custom MCP server**.
> 2. Name it **Demosmith**, paste the MCP server URL and keep **OAuth**. For the icon, upload the [Demosmith icon](https://developers.demosmith.ai/images/demosmith-icon.png).
> 3. Create it, sign in to Demosmith when asked, and allow access.
>
> Then pick **Demosmith** in a chat (type `@Demosmith`) and ask for a demo.

> [tab] Claude Code
>
> Add the server, then type `/mcp` in Claude Code to sign in:
>
> ```bash theme={null}
> claude mcp add --transport http demosmith https://mcp.demosmith.ai/mcp
> ```
>
> Or use an API key instead of signing in:
>
> ```bash theme={null}
> claude mcp add --transport http demosmith https://mcp.demosmith.ai/mcp \
>   --header "Authorization: Bearer YOUR_API_KEY"
> ```

> [tab] Cursor
>
> Add this to `~/.cursor/mcp.json`, with an API key from the Developers page:
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "demosmith": {
>       "url": "https://mcp.demosmith.ai/mcp",
>       "headers": { "Authorization": "Bearer YOUR_API_KEY" }
>     }
>   }
> }
> ```

## Try it

Ask something like:

> Make a Demosmith demo of [https://cal.com](https://cal.com) showing how to book a 30-minute meeting.

The assistant checks the task first, confirms the details with you, creates the demo and checks back until the video is ready. A demo keeps going even if you close the conversation; ask about it later and the assistant picks it up.

## What the assistant can do

| Tool | What it does |
| - | - |
| `list_demo_options` | Languages, voices, tones, music and resolutions |
| `check_demo_prompt` | Check a task before creating a demo (free) |
| `create_demo` | Create and start a demo |
| `get_demo_status` | Where a demo is, and when to check again |
| `answer_demo_question` | Answer a question the agent asked |
| `get_demo` | A finished demo, with its video links |
| `list_demos` | Your demos, newest first |
| `cancel_demo` | Cancel a demo |

## Logins stay out of the chat

An assistant never asks for, or accepts, a password or a verification code. If the agent reaches a sign-in page, the assistant gives you a secure link to the demo's page in Demosmith, and you type the login there. The chat, and the assistant's provider, never see it. See [When the agent needs an answer](https://developers.demosmith.ai/questions.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.