Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Descripción del creador (original en inglés)
Read-only AI video prices, clip costs, and deals from VidFare.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Funciona en Claude para web, escritorio y móvil:
https://mcp.vidfare.com/mcpEjecuta esto en tu terminal
claude mcp add --transport http vidfare https://mcp.vidfare.com/mcpPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"vidfare": {
"url": "https://mcp.vidfare.com/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"vidfare": {
"type": "http",
"url": "https://mcp.vidfare.com/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
ChatGPT solo se conecta a servidores en internet:
https://mcp.vidfare.com/mcpLos nombres de los menús pueden variar un poco según el plan y con el tiempo.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.
list_modelsList the AI video models VidFare tracks, with the cheapest current dollars per second for each.
get_model_pricesList current VidFare prices for one model. provider and resolution are optional filters. Prices the catalog does not contain are omitted rather than guessed.
estimate_costCost of one clip from the VidFare calculator. Credit-plan rows use plan price ÷ credits × credits per clip, then the percent of credits used. API rows are billed seconds times the stated dollars per second. A length, resolution, audio value, or input the vendor page does not stat
cheapest_optionsCheapest stated VidFare price for a clip length and resolution, overall and per model. Rows the vendor does not state for that length or resolution are omitted.
list_dealsList VidFare deals copied from vendor pages and official accounts. status is live, upcoming, ended, or all. Defaults to live. An end date is included only when the source stated one.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
Quien lo publicó (vidfare.com) no es el dueño del repo (SheepinBoots); puede que otra persona lo haya listado
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Respondió en 369 ms (HTTP 200)
No hace falta iniciar sesión
Leímos 5 descripciones de herramientas y no encontramos instrucciones ocultas para la IA
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 2 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.
El repo de GitHub cambió por última vez –, y la última versión (1.0.0) llegó al registro hoy.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
En la misma categoría: Figma Context MCP, Claude Real Video, Figma MCP Server
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
The Figma MCP server brings Figma design context directly into your AI workflow.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Public, read-only Model Context Protocol server for the VidFare price catalog. It speaks Streamable HTTP at /mcp, with no authentication. A client such as ChatGPT, Claude, or Cursor can list models, read prices, estimate a clip, and list deals. Every result includes the VidFare source URL, the last-checked date, and a vidfare.com page link. Those vidfare.com links also carry utm_source=mcp&utm_medium=tool&utm_campaign=vidfare_mcp.
The Worker is live at https://mcp.vidfare.com/mcp. Do not run wrangler login or wrangler deploy from this repository.
The Worker fetches only:
https://vidfare.com/data/prices.jsonhttps://vidfare.com/deals.json (the same JSON is also published at /data/deals.json)Responses are cached for 5 minutes. If a fetch fails, or the catalog does not state a price for the request, the tool says so and does not fill in a number.
| Tool | Arguments |
|---|---|
list_models | none |
get_model_prices | model (required), provider, resolution |
estimate_cost | model, seconds (required). Optional: resolution, audio (with, without, on, off), input (t2v, i2v, ref2v, v2v, extend, lip-sync), plan, provider, used (1–100, default 100), apply_deals (default false), window_seconds (default 60) |
cheapest_options | seconds, resolution (both required). Optional: audio, input, used, apply_deals |
list_deals | status: live (default), upcoming, ended, or all |
estimate_cost uses the same row filter as the credit calculator (scripts/variations.py) and the same plan math as the calculator script: plan price ÷ credits × credits per clip, divided again by the share of credits actually used. API rows are billed seconds times the stated dollars per second. scripts/test_mcp_parity.py checks that against the site code.
A tools/call writes one Workers Analytics Engine point: blob1 is the tool name (unknown if it is not one of the five tools), blob2 is success or error, and double1 is 1. The engine stores the time. The UTC day is that timestamp. The read script also prints when that UTC midnight falls in Pacific Time. Nothing else is stored: no arguments, prompt, IP address, user agent, session id, or country. There is no public stats URL.
Counts are tool requests, not unique people, visits, or sponsor impressions. A retry, a second call from the same person, and a client that does not send the test header each add one. Requests with X-VidFare-Test: 1, and POSTs to localhost or 127.0.0.1 (wrangler dev), are not written. initialize, tools/list, notifications, OPTIONS, and GET are not written. A crawler or someone else's test client that calls a tool is counted.
The write is not awaited and a failure is ignored, so a counter error does not change the tool response.
wrangler.jsonc binds USAGE to the dataset vidfare_mcp_usage. The dataset is created on the first write. Deploying that binding uses the existing Worker deploy token (Workers Scripts Edit or Workers Admin, Workers Routes Edit, and Zone Read). It does not need Analytics Read. Reading the counts does. Create a separate token with Account → Account Analytics → Read, scoped to the VidFare account, and run:
CLOUDFLARE_ACCOUNT_ID=... CLOUDFLARE_API_TOKEN=... python3 scripts/mcp_usage.py
Do not put that token in the repo.
cd mcp-server
npm install npm test npx wrangler dev
wrangler dev stays on this machine. It does not deploy.
Cursor can use mcp-server/.mcp.json. Put the same JSON in a project's .cursor/mcp.json. The URL is https://mcp.vidfare.com/mcp.
server.json is the MCP Registry document. The name is com.vidfare/vidfare. The remote is streamable-http at https://mcp.vidfare.com/mcp.
Namespace verification for com.vidfare is HTTP. The site serves the published proof record at https://vidfare.com/.well-known/mcp-registry-auth. The file is one line, v=MCPv1; k=ed25519; p= . The private key is not in this repo.
The site build copies the file into dist/.well-known/ and writes dist/.nojekyll. actions/upload-pages-artifact leaves dot paths out unless include-hidden-files is true. Both deploy workflows set that, so the URL answers 200 with no redirect.
Token, one Cloudflare account (the account that owns vidfare.com) and one zone (vidfare.com only):
| Scope | Permission | Why |
|---|---|---|
| Account, Workers product | Workers Admin | The first wrangler deploy creates the Worker. A token that can only edit an existing Worker cannot create this one. In the legacy token form this permission is still labeled Account → Workers Scripts → Edit; that legacy permission also creates scripts. If the new role picker is shown, choose Workers Admin on the Workers product, not Editor. |
Zone vidfare.com | Workers Routes → Edit | Attaches the custom domain mcp.vidfare.com. Current docs call this Workers Routes Write. |
Zone vidfare.com | Zone → Read | Wrangler looks up the zone id for vidfare.com. |
Do not add Workers KV, R2, Tail, Account Settings, DNS, or user membership permissions. The Worker has no bindings.
DNS record on vidfare.com, created in the dashboard (the token above does not edit DNS):
| Type | Name | Content | Proxy |
|---|---|---|---|
| AAAA | mcp | 100:: | Proxied |
That is the proxied hostname a Worker custom domain uses. wrangler.jsonc sets the route to custom domain mcp.vidfare.com. After the record exists, npx wrangler deploy from this directory publishes the Worker. It still needs CLOUDFLARE_API_TOKEN in the environment, not in the repo.