Connect an AI agent to Doodaro

Which one to use

Find both in your dashboard: open AI Connect, in the Connect AI group of the sidebar below Your designs → My Templates.

Copy for AI

Copy for AI is text, not a server. It hands a coding agent everything it needs to call the API: who it is working for, the base URL, a key and the instructions.

1. Open AI Connect in your dashboard and click Copy for AI.
2. The dashboard creates a new API key named AI agent · <date>.
3. It fetches the public agent guide from https://app.doodaro.com/api/v1/agent-guide.
4. It puts a header with the base URL and the key on top of the guide, copies the text to your clipboard and shows it once, with a warning that it contains a secret.
5. Paste it into Claude Code, Codex, Cursor or another coding agent, then ask for a video. For example: "Make a 60-second portrait explainer about how planes fly in a chalkboard style."

What the text contains

The top of the text carries the base URL and the key. The rest is the agent guide, generated from the same operation list as the API, so it is always current. The shape looks like this:

# Doodaro API access
Base URL: https://app.doodaro.com/api/v1
API key: ddr_live_...   (secret, revoke it in Developer)

# Doodaro API guide for AI agents
...the agent guide from /api/v1/agent-guide follows...

The guide tells the agent:

• Who it is working for, the base URL and how to authenticate.
• The standard flow: list styles and voices → create a project with scenes → generate assets → poll → render → poll → return videoUrl and dashboardUrl.
• Every operation with method, path and body.
• The error format and polling advice (every 3 to 5 seconds).
• Rules: confirm with you before large generations or renders, never print the key back, never invent style or voice ids.

You can read the guide without a key at app.doodaro.com/api/v1/agent-guide. It contains no secret.

Security and revoking

• The copied text contains a live key. Treat it like a password. Do not paste it into shared docs, tickets or public chats.
• Every click creates a separate key, so you can revoke one agent session without breaking anything else.
• To revoke: open Developer in your dashboard, find the key named AI agent · <date> and click Revoke. The next request with it returns 401 unauthorized.
• Revoke the key when the task is done. You can always copy a fresh one.
• Coding agents may keep conversation history. If a session log could be shared, revoke the key it used.

Doodaro MCP

Doodaro MCP exposes the API as tools. Add the URL and your key header to your MCP client and the agent can call list_styles, create_project, render_video and the rest directly.

First create a key in Developer and export it in the shell your client starts from:

export DOODARO_API_KEY="ddr_live_..."

Client config syntax changes over time. If a format below has changed, check your client's MCP docs.

Claude Code

claude mcp add --transport http doodaro https://app.doodaro.com/api/mcp \
  --header "Authorization: Bearer $DOODARO_API_KEY"

Then run /mcp inside Claude Code to confirm doodaro is connected.

Codex

# ~/.codex/config.toml
[mcp_servers.doodaro]
url = "https://app.doodaro.com/api/mcp"
bearer_token_env_var = "DOODARO_API_KEY"

Codex reads the key from the DOODARO_API_KEY environment variable, so the secret never sits in the config file.

Cursor

// .cursor/mcp.json
{"mcpServers": {"doodaro": {"url": "https://app.doodaro.com/api/mcp",
  "headers": {"Authorization": "Bearer ${env:DOODARO_API_KEY}"}}}}

${env:DOODARO_API_KEY} reads the key from your environment. Do not commit a literal key into .cursor/mcp.json.

Transport and auth

• Transport: MCP Streamable HTTP, stateless. Each POST /api/mcp carries one JSON-RPC 2.0 message and the response is application/json. GET and DELETE return 405.
• Auth: the same API key as the REST API, in Authorization: Bearer. A missing or bad key returns 401 with WWW-Authenticate: Bearer.
• Methods: initialize, notifications/initialized, ping, tools/list, tools/call.

Tools

There is one tool per API operation, with the same name and the same JSON Schema input. Path parameters such as projectId become input fields. The discovery routes and get_media are not tools.

A successful tools/call returns the API response twice: as a JSON string in content[0].text and as an object in structuredContent. An API error returns isError: true with the same error object the REST API sends (code and message).

Test with curl

You do not need a client to check the endpoint. List the tools:

curl -X POST https://app.doodaro.com/api/mcp \
  -H "Authorization: Bearer $DOODARO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}'

Call a tool:

curl -X POST https://app.doodaro.com/api/mcp \
  -H "Authorization: Bearer $DOODARO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc": "2.0", "id": 2, "method": "tools/call",
       "params": {"name": "get_project", "arguments": {"projectId": "<projectId>"}}}'

{
  "jsonrpc": "2.0",
  "id": 2,
  "result": {
    "content": [{"type": "text", "text": "{\"id\":\"<projectId>\",\"title\":\"How planes fly\", ...}"}],
    "structuredContent": {"id": "<projectId>", "title": "How planes fly", "...": "..."}
  }
}

{
  "jsonrpc": "2.0",
  "id": 3,
  "result": {
    "isError": true,
    "content": [{"type": "text", "text": "{\"error\":{\"code\":\"not_ready\",\"message\":\"...\"}}"}]
  }
}

ChatGPT and Claude chat

Not yet. ChatGPT and Claude chat add custom connectors through a sign-in flow (OAuth), and Doodaro does not have that yet. It is phase 2.

When it ships, you will add https://app.doodaro.com/api/mcp as a custom connector and click Sign in with Doodaro instead of pasting a key. The tools will be the same. Until then, use Claude Code, Codex or Cursor with a key header, or Copy for AI.