Video editing MCP server
for footage you already shot.

Aisma’s video editing MCP server lets Claude, Cursor and other AI agents edit a video you already shot. The agent sends the clip with a brief in plain words and optional reference photos, and Aisma returns the edited video privately to your Aisma Library.

Add https://api.aisma.ai/mcp to any client that supports remote MCP servers, then sign in with OAuth or send a personal API key.

Create an API key

Paid editing · Your Aisma credits · Price quoted before you start

Read the developer docsConnect a client
Actual Aisma result: The same hands holding the amber candle jar with a cork lid from Photo 1.
Real Aisma editswap the candle for the amber jar in the photo

What stays

  • Your clip’s framing, length and audio
  • Your account, credits and Library
  • The limits you set for each connection

What changes

  • Whatever the agent’s brief asks for
  • People, clothes, products and objects in the shot
  • The place around them, the style or an effect

What you bring

An MCP client, an Aisma account signed in with Google, Apple or email, credits, and a clip of 2 to 60 seconds. Reference photos are optional, up to 10.

How it works

From your agent
to an edited video.

  1. Connect your client

    Add https://api.aisma.ai/mcp as a remote MCP server, then sign in with Aisma or send your API key.

  2. Send a video and a brief

    The agent uploads a clip or picks one from your Library, writes what should change, adds up to 10 photos and gets a quote.

  3. Confirm and get the result

    You approve the quoted credits, start_edit runs the edit and the agent hands you a private link. The video waits in your Library too.

Connect

Connect Aisma to Claude,
Cursor and other MCP clients.

Any client that supports remote MCP servers over Streamable HTTP can connect, and dynamic client registration means there is no client ID to copy.

Claude Code

Run one of these in your terminal: the first signs in with OAuth, the second sends a personal API key.

claude mcp add --transport http aisma https://api.aisma.ai/mcp
# or with a personal API key
claude mcp add --transport http aisma https://api.aisma.ai/mcp --header "Authorization: Bearer $AISMA_API_KEY"

Cursor

In ~/.cursor/mcp.json, or .cursor/mcp.json inside a project. To use a key, add "headers": { "Authorization": "Bearer aisma_live_…" } next to url.

{
  "mcpServers": {
    "aisma": { "url": "https://api.aisma.ai/mcp" }
  }
}

VS Code

In .vscode/mcp.json:

{
  "servers": {
    "aisma": { "type": "http", "url": "https://api.aisma.ai/mcp" }
  }
}

Claude.ai and Claude Desktop

Open Settings → Connectors → Add custom connector and paste https://api.aisma.ai/mcp.

Prefer a key? Create one under Profile → Settings & help → Connected apps and keys and send it as Authorization: Bearer aisma_live_… from any client that lets you set headers.

Uploading a new clip takes a client that reads your files and runs commands, as Claude Code, Cursor and VS Code do: the agent PUTs the file to the link create_upload returns. Any client can reuse videos from your Library.

MCP tools

Tools the server exposes,
from upload to result.

The server lists nine tools that cover a whole edit. Each declares through MCP annotations whether it only reads or changes something, and answers with structured content that matches its output schema.

Calling start_edit again for the same quote returns the edit it already started, and from protocol revision 2025-06-18 get_result_link also returns the video as a resource link.

Aisma MCP server tools with their scopes
ToolWhat it doesScopeSpends credits
create_uploadA one-time HTTPS link and an asset id; the agent PUTs the video or photo there itself.media:writeNo
get_assetWhether an upload is uploading, being checked, ready, failed or expired.media:readNo
use_library_videoMakes a finished Library video the start of a new edit.media:writeNo
quote_editPrices this clip, brief, photos and quality. Nothing is charged; the quote holds for 15 minutes.jobs:writeNo
start_editStarts a quoted edit and reserves its credits. Marked destructive, so the agent asks you first.jobs:writeYes, once you approve
get_jobStatus and confirmed progress, then resultReady once the video is stored.jobs:readNo
list_libraryYour Library, newest first, with each video’s status and whether it can start a new edit.jobs:readNo
get_result_linkA private link to the finished video, good for one hour.media:readNo
get_accountThe balance in credits and what remains of each limit on this connection.account:readNo

Sign-in

OAuth or an API key.
You choose what it may do.

An MCP client signs in with OAuth 2.1: authorization code with PKCE, rotating refresh tokens and dynamic client registration. Aisma’s consent screen names the client and lets you pick its scopes and, if you like, a monthly credit limit.

Every scope the tools use is selected for you; webhooks:write, which only the REST API’s webhooks need, stays off.

A personal API key suits scripts and clients that can send a header. Create it under Profile → Settings & help → Connected apps and keys; it starts with aisma_live_ and is shown once.

Each connection and key has its own limits, from a monthly credit limit to how many edits run at once; get_account returns what is left. Change them under Connected apps and keys, where revoking a key or disconnecting an app stops it at once.

Use cases

What an agent
can edit.

Remove a person or an object

Name what should go by how it looks and where it is; Aisma fills the space from the scene. A real request: “remove the white SUV parked at the curb”.

Remove objects from video

Change an outfit

Swap a whole outfit or one garment, from words or a photo of the garment. A real request: “change his red puffer jacket to a denim jacket”.

AI video clothes changer

Swap a face

Send clear portrait photos, and the new face keeps the gestures and the camera. A real request: “replace the man with the guy from the photos”. Use photos of people who have agreed to it.

Video face swap

Replace a whole person

Put someone else in the shot, clothes and all, from photos or from words. A real request: “replace the man on the bench with an astronaut”.

Replace a person in a video

Change the background

Keep the person and the camera move, and change the place around them with no green screen. A real request: “change the gray wall behind him to a cozy home office”.

Video background changer

Swap a product

Put a different product in the same hands from one photo of it. A real request: “swap the bottle for the blue one in the photo”.

Product swap video

Restyle a video

Name a material or an art style, such as wool, paper or clay, and the motion stays as filmed.

AI video restyle

Add an effect

Describe one physical event in the frame rather than a filter. A real request: “make the petals fly off the flowers around her arm”.

AI video effects

What you get back

What you get back
when the edit is done.

The video
An MP4 with your clip’s framing, length and original audio, at 720p by default or 1080p.
Where it lands
Privately in the account’s Aisma Library, beside the edits made in the app.
The link
get_result_link returns a private link that works for one hour. Ask again whenever you need a fresh one.
Progress
get_job reports the status and confirmed progress, which reaches 100 only once the video is stored, then resultReady and a link to open the edit in Aisma.
Credits
get_job lists the credits reserved for the edit, any that came back and, once the edit is settled, the credits charged.
Refusals
A refused call returns a tool error in plain words; for a limit, it says which one, when to retry and where to change it.

Remote server

Remote server
(Streamable HTTP)

Endpoint
https://api.aisma.ai/mcp
Transport
Streamable HTTP without sessions: every POST carries one JSON-RPC message and gets its answer as JSON.
Protocol
Revisions 2025-11-25, 2025-06-18 and 2025-03-26, agreed at initialize.
Sign-in discovery
A call without a credential gets HTTP 401 with a WWW-Authenticate header that points to https://api.aisma.ai/.well-known/oauth-protected-resource/mcp, where OAuth begins.
Server card
https://api.aisma.ai/.well-known/mcp/server-card.json lists the server, its transport, sign-in and tools.
Registry
Listed in the MCP Registry (registry.modelcontextprotocol.io) as ai.aisma/aisma.
Docs and examples
The aisma-mcp repository on GitHub has the client setups, the registry file and example scripts in curl, Python and Node.js.
Hosting
Aisma runs the server; there is nothing to install.

Questions about the MCP server

Before you connect
your agent.

Do I need an Aisma account to use the MCP server?

Yes. Every connection and key belongs to an Aisma account signed in with Google, Apple or email, and each edit uses that account’s credits and lands in its Library.

Which MCP clients can connect?

Any client that supports remote MCP servers over Streamable HTTP with OAuth or an API key. The setups above cover Claude Code, Claude.ai, Claude Desktop, Cursor and VS Code.

How long can the video be?

A clip can run 2 to 60 seconds and weigh up to 500 MB, as an MP4 or MOV file. Each edit can carry up to 10 JPEG, PNG or WebP reference photos of up to 20 MB each.

Is the edited video private?

Yes. Uploads and results are private to your account, and every link to them is signed and short-lived. The privacy policy explains how your data is handled.

How is an edit priced?

Edits are priced by the second, in the connected account’s Aisma credits. quote_edit prices the exact edit before anything is charged, and unused credits go back to the balance. Rates, packs and plans are on the pricing page.

Will the agent spend credits without asking me?

Only start_edit spends credits, and its description tells the agent to confirm the price with you first. A connection can also carry a monthly credit limit and a limit per edit.

Can Aisma ask questions about an edit?

In the Aisma web app it can, when a request needs them. Over MCP an edit runs straight from the clip, brief and photos the agent sends, so the agent never waits on a person midway; name what should change and what must stay in the brief.

Can my agent edit a video it already made?

Yes. list_library shows which of the account’s videos can start a new edit, and use_library_video makes one the source of the next, so an agent can chain edits without uploading again.

Is there a REST API as well?

Yes. The same edits run over REST under https://api.aisma.ai/v1, with webhooks when an edit finishes. The developers page documents both, with a curl quickstart, the scopes and every error code.

Updated

Building an agent
on Aisma?

Write to support@aisma.ai about what you’re building or about higher limits.

The developers page has the full API reference, and the help center answers product questions.