Connect Your AI Agent (MCP)
Plug Claude Code, Codex, or any MCP client into Zonic. Your agent does the editing with Zonic's tools: footage understanding, the sequence editor, subtitles and render.
One Endpoint
Zonic is an MCP server. POST /api/mcp speaks MCP over Streamable HTTP (JSON-RPC 2.0), authenticated with the same x-api-key header as every other API endpoint. It is account-scoped: one connection covers all your projects, with each tool taking a pid argument.
Your agent is the editor. The tools it gets are the same ones Zonic's own agent uses: search the footage, read transcripts, stage and commit a sequence, subtitle it, render it. Your model does the thinking on your own plan; your Zonic credits pay only for what the tools themselves do (analysis, a vision model, a render). Nothing is charged for the model.
- Use
/api/mcpto let your agent operate Zonic across projects. - The per-project
/api/projects/{pid}/mcpendpoint remains for read-only retrieval pinned to a single project. - Open
https://zonic.tech/app/{pid}beside your agent: the thread shows every tool call as it happens, and the Sequences panel updates when it commits.
Connect A Client
Any MCP client that supports Streamable HTTP with custom headers works. The two most common:
claude mcp add --transport http zonic https://zonic.tech/api/mcp \--header "x-api-key: $API_KEY"# then, in any session:# "list my zonic projects"# "which clips show the keynote demo?"# "make a 60s recap from my latest project"
Use the API key from your Zonic account. The key authorizes exactly the projects you own — your agent cannot see or edit anyone else's footage.
Tools
Call tools/list to discover the current set: about a hundred tools, the same table Zonic's own agent runs. The server's initialize reply carries the editing rules your agent should read first; Claude Code adds them to its context on its own.
list_projects— entry point; every other tool takes apidfrom here.get_editing_rules,list_skills,load_skill— the sequence contract and the editorial rules for this kind of video. Call these before editing.- Footage understanding —
get_video_names,get_scenes_by_query,get_script_by_query,get_transcript,get_word_transcript,list_people,view_framesand more. - The sequence —
submit_sequence,edit_sequence,check_sequence,commit_sequence,list_sequences,get_sequence. Edits are staged and saved as one version when committed. - Finishing —
adjust_subtitles,translate_subtitles,select_music,render_sequence,list_outputs. generate_rough_cut/revise_sequence/get_job— hand the whole edit to Zonic's hosted agent instead (below).
Turn Hooks
The tools see your agent's calls and nothing else: not your question, not its reply. Register two hooks against the project you are editing and the thread in Zonic reads like an in-app conversation, question and answer included. Claude Code supports these natively; a client without hooks still has every tool call recorded.
{"hooks": {"UserPromptSubmit": [{ "hooks": [{ "type": "http","url": "https://zonic.tech/api/projects/YOUR_PID/hooks","headers": { "x-api-key": "YOUR_API_KEY" } }] }],"Stop": [{ "hooks": [{ "type": "http","url": "https://zonic.tech/api/projects/YOUR_PID/hooks","headers": { "x-api-key": "YOUR_API_KEY" } }] }]}}
Staged edits a client leaves behind without committing are committed for it once they have sat idle for half an hour, so nothing it did is lost.
Hosted Editing Jobs
You can also hand the whole edit to Zonic's hosted agent, Dekiru. That takes minutes, so these tools return immediately with a job_id while the agent works. Poll get_job every 15–30 seconds; on done it returns the agent's answer, the new sequence index, and a link to open the sequence in the Zonic editor. Unlike editing with the tools yourself, a hosted edit runs on Zonic's model and is charged to your credits.
curl -X POST "https://zonic.tech/api/mcp" \-H "x-api-key: $API_KEY" -H "Content-Type: application/json" \-d '{"jsonrpc": "2.0", "id": 1, "method": "tools/call","params": {"name": "generate_rough_cut","arguments": { "pid": "YOUR_PID", "brief": "60s energetic event recap, open on the venue" }}}'# → { "job_id": "...", "status": "running", ... } — then poll:curl -X POST "https://zonic.tech/api/mcp" \-H "x-api-key: $API_KEY" -H "Content-Type: application/json" \-d '{"jsonrpc": "2.0", "id": 2, "method": "tools/call","params": { "name": "get_job", "arguments": { "job_id": "JOB_ID" } }}'
A hosted edit runs on Zonic's servers and consumes your Zonic credits, exactly like edits made in the app. Your agent client never needs Zonic's editorial models or prompts: the intelligence stays server-side.
Project Modes
- Every tool works on a cloud or hybrid project. Frames and renders come from the footage in Zonic's cloud.
- A local-mode project keeps its footage and its agent on one machine. The Local Script serves the same tools at
http://localhost:8000/api/mcp; connect to that instead ofzonic.tech.