VIDMOATdevelopers
Developers /Documentation /Give your agent an editing timeline.Read as plain text ↗
Documentation

Give your agent an editing timeline.

MCP connects your client to Vidmoat’s editing and media tools. REST is useful for a fixed integration; MCP lets an agent choose tools as it works.

1. Connect your client

Add a remote HTTP MCP server using https://api.vidmoat.com/api/mcp. Use your client’s authentication flow if it supports Vidmoat OAuth, or supply a Vidmoat API key as a bearer token. Client configuration formats vary; the endpoint and header below are the connection details.

Endpoint: https://api.vidmoat.com/api/mcp
Authorization: Bearer YOUR_VIDMOAT_KEY
Keep keys in your client’s secret settings or server environment. Live API and MCP access require Studio. Plan features, ownership and credit checks still apply to individual tools.

2. Discover the current tools

Let your MCP client initialize the connection and call tools/list. Use the returned names and input schemas instead of a fixed tool count copied from an older example. Additional capabilities and installed plugins can be discovered through the discovery tools returned by the server.

curl --fail-with-body -sS https://api.vidmoat.com/api/mcp \
  -H "Authorization: Bearer $VIDMOAT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

3. Give it a usable brief

Use my product footage to make a 20-second vertical launch video.
Start with the product reveal, then show three benefits.
Use our orange brand accents and readable captions.
Keep music beneath the narration. Do not generate paid media
without telling me the cost. Preview the opening, each text
change and the ending before exporting.

Specify the audience, duration, aspect ratio, source media and any budget constraint. A style reference guides the edit; it does not have to appear in the finished video. Character references are optional: use them when continuity matters, and omit them when it does not.

4. Review, then export

Have the agent inspect the source, apply edits, review rendered frames and correct visible problems. A successful edit request is not proof that the composition looks right. Check the finished export as well. You can open the same project in the Vidmoat editor and adjust the timeline yourself.

Versioning. Additive changes ship into v1 — new fields, new endpoints, new enum values. Ignore unknown fields; a client that rejects them can break on a routine release. The Vidmoat-Version header defaults to 2026-08-01 and is echoed back; it is reserved for future versioning and does not currently select different behaviour.