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)
Create videos with prompts, and use Rendley’s video editor to adjust anything you need.
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.
AuthorizationYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http rendley https://mcp.rendley.com/mcp --header 'Authorization: Bearer {rendley_api_key}'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"rendley": {
"url": "https://mcp.rendley.com/mcp",
"headers": {
"Authorization": "Bearer {rendley_api_key}"
}
}
}
}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": {
"rendley": {
"type": "http",
"url": "https://mcp.rendley.com/mcp",
"headers": {
"Authorization": "Bearer {rendley_api_key}"
}
}
}
}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.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization HTTP headerThese 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 8, 2026
The registry name was verified with the GitHub account rendleyhq, which owns the repo
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 5 months 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:↓ Downloads per weeki★ 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.
The MCP server for Rendley. It gives an AI assistant a full video editor: connect it once, then create and edit video by describing what you want, in the same chat you already work in. Under the hood it drives the hosted Rendley editor in a browser and calls the hosted Rendley API on your behalf:
https://app.rendley.comhttps://api.rendley.com/v1The same agent is also reachable over plain HTTP (POST /v1/agent) for backends that don't speak MCP. See REST example.
There are two ways to use it:
https://mcp.rendley.com/mcp. Nothing to run. See Connect a client.📖 Full documentation, with step-by-step setup guides and screenshots: [docs.rendley.com/mcp](https://docs.rendley.com/mcp)
Any client that speaks remote MCP can connect. Point it at the endpoint and authenticate by signing in or with an API key:
https://mcp.rendley.com/mcp
Authorization: Bearer YOUR_RENDLEY_API_KEY header. Create one at Settings → API Keys; see Get an API key.Most clients accept a JSON config like this:
{
"mcpServers": { "rendley": { "url": "https://mcp.rendley.com/mcp", "headers": { "Authorization": "Bearer YOUR_RENDLEY_API_KEY" } } } }
For sign-in, drop the headers block and let the client run the browser flow.
The docs have illustrated, per-client walkthroughs:
mcp-remote bridge for local-only clients.For Claude Code specifically:
claude mcp add --transport http rendley https://mcp.rendley.com/mcp \
--header "Authorization: Bearer YOUR_RENDLEY_API_KEY"
Ask the client what it can do, then try a simple request:
What can Rendley do here?
List my projects.
If it lists the Rendley tools and your projects, you're connected. From there, describe the video you want and the assistant creates a project, builds the edit, and returns a link.
This repo is the MCP server only; it does not run the full Rendley stack locally. It talks to the hosted Rendley API and editor. When you self-host, point clients at your own https:// /mcp instead of https://mcp.rendley.com/mcp.
>= 1.1 (or Docker)git clone https://github.com/rendleyhq/rendley-mcp.git
cd rendley-mcp
bun install bun dev # http://localhost:8787
API_BASE_URL and APP_BASE_URL default to the hosted Rendley API and editor, so the server boots out of the box with no .env at all; copy .env.example only to point at a different stack. The server holds no credentials of its own: every request authenticates with the caller's own API key or OAuth token.
By default the server drives the editor with a local Chrome (BROWSER_MODE=local), so no extra infrastructure is needed. bun install downloads a bundled Chromium; with USE_CHROME_CHANNEL=true it prefers your installed Google Chrome and falls back to the bundled browser. Set HEADLESS=false to watch the editor in a visible window, and CPU_ONLY=true on machines without a usable GPU.
Verify it's up:
curl http://localhost:8787/health
docker compose up -d --build
curl http://localhost:8787/health
Use the same client steps as the hosted server, but swap the endpoint for your host (e.g. http://localhost:8787/mcp) and authenticate with your API key as a bearer token:
{
"mcpServers": { "rendley": { "url": "http://localhost:8787/mcp", "headers": { "Authorization": "Bearer YOUR_RENDLEY_API_KEY" } } } }
OAuth. OAuth sign-in is always on. Clients that support it (Claude connectors, ChatGPT, codex mcp login rendley) can sign in via the hosted login flow instead of pasting a key; the server advertises the authorization server through RFC 9728 protected-resource metadata. Set MCP_PUBLIC_URL to this server's public URL so discovery points at the right host.
For hosted deployments, set BROWSER_MODE=remote and point the server at a deployed remote browser worker. The server mints a short-lived editor session token and posts it to the worker, so the caller's credential never leaves this process:
BROWSER_MODE=remote
BROWSER_WORKER_URL=https:// BROWSER_WORKER_TOKEN=
All configuration is via environment variables; start from .env.example, which documents every option. The essentials:
| Variable | Default | Purpose |
|---|---|---|
API_BASE_URL | https://api.rendley.com/v1 | Rendley API root. Override for staging or a self-hosted stack. |
APP_BASE_URL | https://app.rendley.com | Rendley editor root. Override for staging or a self-hosted stack. |
MCP_PUBLIC_URL | none | This server's public URL, advertised for OAuth discovery. |
BROWSER_MODE | local | local = in-process Playwright Chrome; remote = remote browser worker. |
HEADLESS | true | Local mode only; false shows the browser window. |
USE_CHROME_CHANNEL | true | Local mode only; prefer installed Chrome over bundled Chromium. |
CPU_ONLY | false | Force software WebGL (SwiftShader) on hosts without a GPU. |
QUEUE_CONCURRENCY | 120 | Max concurrent browser-backed jobs per container. |
CORS_ORIGINS | none | CSV allowlist of browser origins. Empty disables CORS. |
| Method | Path | |
|---|---|---|
POST | /mcp | MCP Streamable HTTP transport |
POST | /v1/agent | Start an async edit job |
GET | /v1/jobs/:id | Poll a job |
GET | /health | Liveness |
You don't need an MCP client to drive the agent. The same agent is available over plain HTTP. Start a job, get an id back, and poll until the video is ready. Full reference: docs.rendley.com/mcp/api-access.
# Start a job (swap in http://localhost:8787 for a self-hosted instance)
curl -X POST https://mcp.rendley.com/v1/agent \ -H "Authorization: Bearer $RENDLEY_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "prompt": "Create a 9:16 slideshow from these files", "files": [ { "url": "https://cdn.example.com/photo1.jpg" }, { "url": "https://cdn.example.com/photo2.jpg" } ] }'
curl -H "Authorization: Bearer $RENDLEY_API_KEY" \ https://mcp.rendley.com/v1/jobs/
/health is healthy whenever the server can serve; browser launch failures surface on browser-backed requests.bun dev # watch mode, pretty logs
bun start # production start bun run typecheck
Apache License 2.0. © 2026 Rendley.