MCP server docs

Connect your AI

Dailies runs an MCP server. Connect an AI app to it and the app can read your Projects, edit Shots and render frames to check its work, as you, in one workspace you choose.

Server URL

https://dailies.design/mcp

Streamable HTTP. Sign-in is OAuth 2.1 with PKCE (S256). An app registers itself with Dynamic Client Registration or a Client ID Metadata Document, so there is nothing to set up on our side first.

Set up your AI

Every client uses https://dailies.design/mcp and signs in with OAuth. Pick yours.

Claude

Settings > Connectors > Add custom connector. Paste the URL, click Add, then Connect. Works on web, desktop and phone.

Claude Code

claude mcp add --transport http dailies https://dailies.design/mcp

Then run /mcp and pick dailies to sign in.

ChatGPT

Settings > Connectors > Advanced: turn on Developer mode. Create a connector, paste the URL, choose OAuth.

Codex

codex mcp add dailies --url https://dailies.design/mcp

Then codex mcp login dailies.

Cursor

~/.cursor/mcp.json

{ "mcpServers": { "dailies": { "url": "https://dailies.design/mcp" } } }

Or Add to Cursor. Cursor opens the sign-in.

VS Code

.vscode/mcp.json

{ "servers": { "dailies": { "type": "http", "url": "https://dailies.design/mcp" } } }

Start the server from that file, then sign in.

Other

Any client with Streamable HTTP and OAuth. No OAuth? Use a token from Settings, sent as Authorization: Bearer.

The sign-in page names the app, where it sends you back, and who is signed in. You pick the workspace, then click Allow. Dailies only sends you back to an address the app registered on Claude, ChatGPT, VS Code, Cursor, or an app on your own computer.

Check it works

Ask your AI to call get_stage_health. Renders and previews run in a Dailies editor tab, so it tells your AI whether one is open. If none is, ask your AI to call list_shots and give you the link to the Project, then open it and keep the tab open while you work.

What your AI can do

Read: Projects, Shots, Storyboards, assets, comments, guides.
Edit: Shots, components, assets, comment replies.
Check: render frames and filmstrips, stage health.
Media: import and probe files, analyze audio.

It never touches billing, members or workspace settings. Each tool says whether it reads or changes something, so your client can ask you before a change.

Permissions

One workspace per connection. You pick it at sign-in. To use another workspace, connect again and pick that one.
It acts as you. The app can do what your role allows and no more. A viewer's app can read but not edit. The Billing role cannot connect apps.
The AI edits switch. Each workspace has a switch, "AI can edit", in Settings, Connect your AI. Owners and Admins can change it. While it is off, connected apps can read but not change anything. A client that connected before the switch changed may need to reconnect to see the new list of tools (in Claude Code, run /mcp).
Disconnecting. Revoke an app in Settings, Connect your AI, under Connected apps. It loses access on its next call. Leaving or being removed from the workspace cuts off your apps there too.
How long sign-in lasts. An app stays signed in while you use it, and needs to sign in again after 90 days without use.

Clients that need a token

For scripts, CI and tools without OAuth. Make a token in Settings, Connect your AI, under Clients that need a token, and send it with every request:

Authorization: Bearer <token>

A token acts as you in one workspace, under the same permissions and AI edits switch as an app. Keep it secret, and revoke it there when you are done.

Local studio (dailies dev)

Running the studio on your own computer? In that folder, run npx dailies-studio connect. It writes a .mcp.json that points your AI at the local studio while npx dailies-studio dev is running. There is no sign-in: the local server only answers your own computer. Edits stay off until you run connect with --write.