
Remote MCP server and REST API for Aisma: edit videos you already shot with plain words and
Remote MCP server and REST API for Aisma: edit videos you already shot with plain words and reference photos.
·
Edit a video you already shot by describing the change in plain words, from any AI assistant, agent or script. Remove a person or an object, change an outfit, the background or a product, swap a face from your photos, restyle the clip or add an effect. Aisma keeps the original framing and audio and delivers a private 720p or 1080p result to your Aisma Library.
https://api.aisma.ai/mcphttps://api.aisma.ai/v1 (OpenAPI 3.1)ai.aisma/aismaThis repository holds documentation, the registry server.json and small client examples. The server
itself is hosted by Aisma; there is nothing to install or run.
Your client opens Aisma's sign-in page on first use: OAuth 2.1 with PKCE and dynamic client registration, so there is no client ID to copy. On the consent screen you choose what the connection may do and its monthly credit limit. You can change limits or disconnect at any time in Aisma under Profile → Settings & help → Connected apps and keys (https://aisma.ai/app/api-access).
Prefer a key? Create a personal API key on the same page and send it as Authorization: Bearer aisma_live_….
Each key has its own permissions and limits, adjustable per key on that page.
Claude Code
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 (~/.cursor/mcp.json or .cursor/mcp.json in a project)
{
"mcpServers": {
"aisma": { "url": "https://api.aisma.ai/mcp" }
}
}With a key, add "headers": { "Authorization": "Bearer aisma_live_…" } next to url.
VS Code (.vscode/mcp.json)
{
"servers": {
"aisma": { "type": "http", "url": "https://api.aisma.ai/mcp" }
}
}ChatGPT (custom MCP servers, where your plan and workspace allow them): open
chatgpt.com/plugins, choose + → Add custom MCP server, enter
https://api.aisma.ai/mcp, pick OAuth and sign in to Aisma.
Claude.ai and Claude Desktop: Settings → Connectors → Add custom connector → https://api.aisma.ai/mcp.
Other clients: any client that supports remote MCP servers over Streamable HTTP works. The server is
stateless and answers protocol revisions 2025-11-25, 2025-06-18 and 2025-03-26. An unauthenticated request
gets 401 with WWW-Authenticate: Bearer resource_metadata=…, which is how clients discover the sign-in.
Video files never travel inside MCP messages. create_upload returns a one-time HTTPS link and the
assistant uploads the file itself with an HTTP PUT. That works in assistants that can read your files and
run commands (Claude Code, Cursor, VS Code and other coding agents). A chat-only assistant (ChatGPT,
Claude.ai) can't upload a new clip this way; there it can re-edit videos that are already finished in your
Aisma Library (list_library → use_library_video).
| Tool | What it does | Spends credits |
|---|---|---|
create_upload | Returns a one-time HTTPS upload link and an asset id for a video or photo; the assistant PUTs the file itself | No |
get_asset | Status of an upload: uploading, checking, ready, failed or expired | No |
use_library_video | Uses one of your finished Aisma videos as the source of a new edit | No |
quote_edit | Prices an edit of a ready source with your instruction and optional photos, at 720p or 1080p; nothing is charged and the quote holds for 15 minutes | No |
start_edit | Starts a quoted edit and reserves its credits; marked destructive, and the assistant confirms with you first | Yes, after you confirm |
get_job | Status and progress of an edit | No |
list_library | Your Aisma Library, newest first, with each edit's status | No |
get_result_link | A private link to the finished video, valid for one hour | No |
get_account | Your credit balance and this connection's monthly limit and usage | No |
Every tool has a title, read-only or destructive hints and an output schema.
Send your key as a bearer token and a descriptive User-Agent header (for example my-app/1.0): some HTTP
libraries' default agents are refused by our edge network. Bodies are JSON, ids are UUIDs.
POST /v1/uploads returns uploadUrl, method (PUT) and headers. PUT the file there with those headers.GET /v1/assets/{id} until status is ready.POST /v1/quotes prices the edit. A 202 with retryAfterMs means the clip is still being checked; ask again after that delay.POST /v1/jobs with an Idempotency-Key header starts the quoted edit. A retry with the same key returns the same edit.GET /v1/jobs/{id} (no more often than every 10 seconds) or register a webhook, then POST /v1/jobs/{id}/result for a one-hour link.export AISMA_API_KEY=aisma_live_...
UA="my-app/1.0"
curl -s -X POST https://api.aisma.ai/v1/uploads \
-H "Authorization: Bearer $AISMA_API_KEY" -H "User-Agent: $UA" -H "Content-Type: application/json" \
-d '{"kind":"video","contentType":"video/mp4","bytes":12345678}'
# PUT clip.mp4 to uploadUrl with the returned headers, then wait for GET /v1/assets/ASSET_ID → ready
curl -s -X POST https://api.aisma.ai/v1/quotes \
-H "Authorization: Bearer $AISMA_API_KEY" -H "User-Agent: $UA" -H "Content-Type: application/json" \
-d '{"sourceId":"ASSET_ID","brief":"change the background to a snowy forest","quality":"720p"}'
curl -s -X POST https://api.aisma.ai/v1/jobs \
-H "Authorization: Bearer $AISMA_API_KEY" -H "User-Agent: $UA" -H "Content-Type: application/json" \
-H "Idempotency-Key: first-edit-0001" \
-d '{"quoteId":"QUOTE_ID"}'
curl -s -X POST https://api.aisma.ai/v1/jobs/JOB_ID/result \
-H "Authorization: Bearer $AISMA_API_KEY" -H "User-Agent: $UA"Complete scripts that upload, price, ask you to confirm, start and download:
examples/edit.sh (curl + jq)examples/edit.py (Python 3 + requests)examples/edit.mjs (Node.js 18+ fetch)Errors share one JSON shape, {"error": {"code", "message"}}, with readable messages. Webhooks
(job.completed, job.failed, job.settled) are signed per Standard Webhooks. Scopes, limits, webhooks
and the error table are documented at https://aisma.ai/developers.
Aisma is made by BEINTOUCH PTE. LTD., Singapore.
The examples and documentation in this repository are released under the MIT License. The Aisma service itself is governed by the Terms of Use above.
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add aisma --transport http https://api.aisma.ai/mcp{
"mcpServers": {
"aisma": {
"url": "https://api.aisma.ai/mcp"
}
}
}code --add-mcp '{"name":"aisma","url":"https://api.aisma.ai/mcp"}'Runs as a hosted service. Your client connects over the network and nothing is installed locally.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/aisma-mcp-server-and-api to learn what the "Aisma MCP server and API" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
claude mcp add --transport http aisma https://api.aisma.ai/mcp
claude mcp add --transport http aisma https://api.aisma.ai/mcp --header "Authorization: Bearer $AISMA_API_KEY"This server doesn't publish a machine-readable tool manifest, and it doesn't expose a public endpoint we could ask. Connect the server locally to see what it exposes.
We could not run this server: its endpoint did not list its tools to an anonymous client, which usually means it asks for an API key or a sign-in. The four checks that need a live server are left out, and the grade tops out at B until we can read its tools.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/aisma-mcp-server-and-api)Nothing comparable is listed yet.
No tagged releases on record.
Connect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "aisma-mcp-server-and-api" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.