Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Description from the maker (original English)
Edit videos you already shot with plain words and reference photos. Framing and audio stay.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.aisma.ai/mcpRun this in your terminal
claude mcp add --transport http aisma https://api.aisma.ai/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"aisma": {
"url": "https://api.aisma.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"aisma": {
"type": "http",
"url": "https://api.aisma.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://api.aisma.ai/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain aisma.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Let any LLM watch a video locally — and search everything it has ever watched.
Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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
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}'
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.