Developer documentation
Eddie AI API
Eddie AI exposes its video editor as a Model Context Protocol server. Connect an MCP client, sign in with your Eddie account, and every editing action becomes a typed tool call.
What the API is
The Eddie AI API is a Model Context Protocol server. It is not a REST API. You do not build request paths or read response bodies. You connect a client, and Eddie’s editing actions arrive in that client as typed tools with names, descriptions and JSON Schema parameters.
One endpoint serves the whole surface. The client opens a session there, lists the tools, and calls them. Anything an MCP client can do — Claude, ChatGPT, Claude Code, an agent framework, or a script you write against an MCP library — works against this server.
https://mcp.heyeddie.ai/api/mcp
The mental model
Almost every call takes a shareId. A share is a project. It holds the media you imported, and it holds the edits built from that media. Two nouns carry the model:
- Sources are the media in the share. Each one has an id, a name and a roll type.
- Edits are cuts assembled from those sources. Each one has a name. A share can hold several.
Work moves in one direction. Sources are imported and analysed. An edit is built from them. Refinements — captions, music, trims, cutaways — change one edit and leave the sources and the other edits alone. Delivery turns an edit into a file.
Core concepts covers each noun in detail, including transcripts, the A-roll and B-roll split, and multicam groups.
What you can build
- An assistant that reads a project’s transcripts, finds the moments a brief asks for, and builds a cut to a named length.
- A pipeline that takes a finished edit and delivers it — a rendered file, or an interchange file an editor opens in their NLE.
- A review step that reads an edit back, segment by segment, and reports what it contains before anyone opens it.
- A desk assistant inside Claude or ChatGPT that answers questions about footage you have already imported.
The endpoint at a glance
- Endpoint
https://mcp.heyeddie.ai/api/mcp- Protocol
- Model Context Protocol
- Transport
- Streamable HTTP, at
/api/mcponly. The older server-sent-events transport is not served. - Methods
POST,GETandOPTIONS.- Authentication
- OAuth. The client discovers the sign-in itself. How it works.
- Cross-origin
- Allowed from any origin. No cookies are involved; the bearer token carries the identity.
- Tool catalogue
https://mcp.heyeddie.ai/api/mcp-catalogue— the same list your client sees, as JSON, with no sign-in. It is what the tool reference renders.
Where to go next
- QuickstartConnect Claude, ChatGPT, Claude Code or your own client.
- AuthenticationOAuth discovery, sign-in, and project access levels.
- Core conceptsShares, sources, A-roll, B-roll, transcripts and edits.
- Errors and limitsHow failures surface, and what to retry.
- Tool referenceEvery tool, its description and its parameters.
- ChangelogChanges to the API and to these documents.
Building against Eddie from a shell or your own backend instead? Eddie for agents covers the command line and the software development kit.