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)
Look up APIKO image and video models, quote prices, generate media and track spend.
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.
APIKO_API_KEYLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"apiko": {
"command": "npx",
"args": [
"-y",
"apiko-mcp"
],
"env": {
"APIKO_API_KEY": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add apiko --env APIKO_API_KEY=your-value -- npx -y apiko-mcpCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"apiko": {
"command": "npx",
"args": [
"-y",
"apiko-mcp"
],
"env": {
"APIKO_API_KEY": "your-value"
}
}
}
}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": {
"apiko": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"apiko-mcp"
],
"env": {
"APIKO_API_KEY": "your-value"
}
}
}
}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ú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
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.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 9 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub tong0619453646-dev, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
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ó 1 de 1 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.
Debes completar: APIKO_API_KEY
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.1.1) llegó al registro hace 13 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
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:↓ Descargas por semanai★ 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.
Use APIKO image and video models from Claude Code, Codex, Cursor, Claude Desktop and other MCP clients. The server runs locally over stdio with your own APIKO API key: the agent can look up models and request fields, quote a list price, generate images and videos, follow tasks, check what the key has spent, and upload reference images.
Generation is billed to your APIKO balance at API prices. The server tells the agent to quote first and wait for your approval before every paid call.
Overview, supported models and prices: APIKO MCP server.
Any client that can start a local stdio MCP server can run npx -y apiko-mcp.
| Client | How to add it | Tested by us |
|---|---|---|
| Claude Code (CLI and desktop app) | claude mcp add (below) | yes |
| Codex (CLI, IDE extension, desktop app) | codex mcp add or ~/.codex/config.toml (below) | yes |
| Cursor | ~/.cursor/mcp.json (below) | config follows Cursor's docs |
| Claude Desktop | claude_desktop_config.json (below) | config follows the MCP docs |
| Other stdio clients (Windsurf, Cline, VS Code agent mode, ...) | command npx, args -y apiko-mcp, env APIKO_API_KEY | no |
The rows marked "follows the docs" use each client's documented mcpServers format with the same command that is tested in Claude Code and Codex. If one of them does not work for you, please open an issue.
The server is published on npm as apiko-mcp and runs with npx -y apiko-mcp. To run it from source instead:
git clone <this repo> apiko-mcp
cd apiko-mcp npm install npm run build # writes dist/index.js
and replace npx -y apiko-mcp below with node /absolute/path/to/apiko-mcp/dist/index.js.
claude mcp add apiko --scope user -e APIKO_API_KEY=sk-... -- npx -y apiko-mcp
--scope user stores the server in ~/.claude.json, which the Claude Code desktop app (Code tab) also loads. Run /mcp in Claude Code to check that apiko is connected.
codex mcp add apiko --env APIKO_API_KEY=sk-... -- npx -y apiko-mcp
or add this to ~/.codex/config.toml, which the Codex CLI, the IDE extension and the ChatGPT desktop app share:
[mcp_servers.apiko]
command = "npx" args = ["-y", "apiko-mcp"] env = { APIKO_API_KEY = "sk-..." }
Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json in a project root:
{
"mcpServers": { "apiko": { "type": "stdio", "command": "npx", "args": ["-y", "apiko-mcp"], "env": { "APIKO_API_KEY": "sk-..." } } } }
Settings → Developer → Edit Config opens claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows). Add the server and restart the app:
{
"mcpServers": { "apiko": { "command": "npx", "args": ["-y", "apiko-mcp"], "env": { "APIKO_API_KEY": "sk-..." } } } }
If a desktop app reports that node or npx cannot be found, use the full path from which node.
Add APIKO_MCP_READ_ONLY=1 to the server's env (-e APIKO_MCP_READ_ONLY=1 or --env APIKO_MCP_READ_ONLY=1). The generate and upload tools are then hidden; model lookup, quotes, task checks and the key's usage still work.
| Variable | Default | Meaning |
|---|---|---|
APIKO_API_KEY | required | Your APIKO key. Never paste it into a chat. |
APIKO_MCP_READ_ONLY | off | 1 hides generate_image, generate_video and upload_image. |
APIKO_BASE_URL | https://api.apiko.app | API base URL. |
APIKO_SITE_URL | https://apiko.app | Where the public price catalog is read from. |
HTTPS_PROXY, HTTP_PROXY, NO_PROXY | unset | Used only when set. Node's built-in fetch ignores them, so the server switches to a proxy-aware client when they are present. |
| Tool | Cost | What it does |
|---|---|---|
search_models | free | Lists the models your key can use, with category, list price and modes. Filter by query and category. |
get_model | free | One model's input_schema (fields, enums, defaults), endpoints, modes and price tiers. |
estimate_cost | free | Validates an input against the schema and quotes the list price without submitting. |
generate_image | paid | Generates, or edits when input.images has reference URLs. Runs async when the model supports it and waits up to wait_seconds (default 30). |
generate_video | paid | Submits a video task (POST /v1/videos) and returns its task_id. |
get_task | free | Status, progress, result URLs and failure reason of a task; can wait up to 45 s. |
check_balance | free | What this key has spent and its own spending limit, if any. |
upload_image | free | Uploads a local JPEG/PNG/WebP (or copies a public image URL) and returns a public img.apiko.app URL for reference fields. |
Typical flow: search_models → get_model → upload_image (if you have local references) → estimate_cost → you approve → generate_image / generate_video → get_task.
estimate_cost (and the generate tools' cost field) returns one of:
estimated: a number, when the price follows directly from the input: per-image tiers chosen by resolution (or by an explicit WxH size for gpt-image-2), flat per-image prices, and per-second video prices by resolution × duration, including reference videos once you pass reference_video_seconds.needs_input: something the price depends on is missing, usually the total length of reference videos. You also get the range and the amount held from your balance at submission (hold_usd), which is refunded down to the real charge when the task settles.token_billed: billed by tokens (GPT Image 2.5 Flare / Sunburst, text models). An indicative_usd figure may be shown, but it is not a quote.unknown: no published price or no reliable rule; never treat it as free.All figures are list prices in USD from the public catalog at apiko.app. The gateway's charge at settlement is final. Failed tasks are refunded automatically.
max_cost_usd on the generate tools refuses the call when the estimate, or its guaranteed upper bound, is above the cap, or when no reliable figure exists.
generate_* call creates a paid task. Calling it again to check progress would pay twice; use get_task.client_request_id stops a repeated call from being submitted twice while the same server process is running. If a submission times out, the server does not retry it: check https://apiko.app/dashboard/usage first.check_balance reads the key, not the account. Keys created on apiko.app have no limit of their own and draw on the account balance, which only the dashboard shows (https://apiko.app/dashboard/billing).search_models, but you call them through the OpenAI-compatible API at https://api.apiko.app/v1, not through this server.Codex gives each MCP tool call 60 seconds by default, so no tool here waits longer than 45 seconds; long tasks are followed with get_task. The rare sync-only image model can take longer: raise tool_timeout_sec under [mcp_servers.apiko] if you use one.
npm install
npm test # builds, then runs the tests against a local mock API
src/tools.ts holds the tool logic and src/server.ts builds an McpServer from it, independent of the transport; src/index.ts is the stdio entry point. The tests never call the production API.