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)
Claude Code / MCP skills for the dev pipeline: discover, spec, design, build, ship, operate.
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://opchain.dev/mcpRun this in your terminal
claude mcp add --transport http opchain-skills https://opchain.dev/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"opchain-skills": {
"url": "https://opchain.dev/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": {
"opchain-skills": {
"type": "http",
"url": "https://opchain.dev/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://opchain.dev/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.
Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.
list_skillsList every opchain skill (id, displayName, description, phases, commands). Call this first to see the concept→ship pipeline.
routeMap a request or an /oc-* command to the skill that should handle it, with the entry phase. Use when you're unsure which skill fits.
get_skillReturn the full SKILL.md (the instructions) for one skill id. Load it, then follow it. Read get_orchestrator once before your first get_skill in a session.
get_orchestratorReturn the shared orchestrator protocol (welcome flow, pipeline map, active-chaining rules). Read once at the start of a session.
create_checkpoint_sessionCreate a private server-issued session for checkpoint storage. Retain the returned sessionId and use it with read_checkpoint/write_checkpoint; never invent or share one.
read_checkpointRead a skill's saved session checkpoint (where you left off). sessionId must be a private token returned by create_checkpoint_session.
write_checkpointPersist a skill's session checkpoint so progress survives across sessions. Stores the object as given (any JSON object up to 64 KiB); it does not validate it against the opchain checkpoint protocol, so write the shape the protocol documents.
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 9, 2026
The registry name was verified with the GitHub account asfbay-bit, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 132 ms (HTTP 200)
No sign-in needed
Read 7 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 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 (2.1.0) 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:↓ 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.
Opchain 2.1.0 · 36 skills · released November 5, 2026.
A coordinated set of Claude skills covering the full software development pipeline — discover, spec, design, build, audit, ship, scale. One skill per phase. A shared JSON checkpoint protocol carries context across sessions and skills, so work resumes where you left off.
Site & docs: https://opchain.dev
Ships complete skills and plugin hooks for session context and suggestions. Run /oc-enroll in each repository to enable the Git commit gate. Installing the plugin alone does not enroll repositories or enable learning.
/plugin marketplace add asfbay-bit/opchain-skills
/plugin install opchain
curl -L https://opchain.dev/opchain-skills.zip -o opchain-skills.zip
unzip opchain-skills.zip -d .claude/skills/ claude
/oc-discover
Download complete skill ZIPs from Install, then use your host's supported skill upload flow. Keep references and runtime files with each skill. Local runtime commands require Node.js 22.13 or newer and a host that can execute them; a hosted chat without local tools cannot run those commands.
git add .claude/skills/
git commit -m "chore: add opchain skills" git push
For an existing repo installation, ask your coding agent to run:
/oc-update check
/oc-update
If you use 1.9 or earlier and the updater is missing, copy the upgrade prompt at the top of Install. It checks the host and published release, then installs the complete package. The updater preserves checkpoints, local tracking consent, usage history and unrelated skills, and backs up replaced Opchain files. Global plugin installations use the host's supported plugin update.
Open a new agent session afterward and run /oc-update check to verify the installed package. Learning remains off until explicitly enabled; provider access and an external reviewer must be configured separately.
| skill | what it does |
|---|---|
oc-app-architect | Discover → spec → build, with Generator/Evaluator QA loop |
oc-stack-forge | Stack advisor across Cloudflare, Vercel, AWS, Supabase, etc. |
oc-ux-engineer | Design Planner → Generator → Evaluator harness |
oc-dash-forge | Dashboards and dense-data UIs (spec + React prototype) |
oc-integrations-engineer | Third-party API integrations (Slack, Stripe, OAuth) |
oc-api-dev | First-party API design (OpenAPI, GraphQL, SDKs) |
oc-claude-api | Claude API apps: model routing, prompt caching, tool use |
oc-rag-forge | RAG systems: vector DBs, embeddings, chunking, retrieval eval |
oc-agent-forge | Claude Agent SDK apps: topology, tool budgets, harness loops |
oc-prompt-ops | Prompts as code: versioning, eval datasets, regression detection |
oc-qa-ops | Test-pyramid design: coverage budgets, contract-test matrix, load plans |
oc-data-ops | Data pipelines: ingestion, dbt layering, observable data contracts |
oc-signal-forge | Question → trustworthy metric: instrument, harvest, verify, wire |
oc-code-auditor | Auditor → Fixer → Verifier; 5-layer pre-deploy sweep |
oc-security-auditor | Threat modeling, OWASP hardening, attack-surface review |
oc-security-hardening | Executes the fixes + per-deploy hardening gate (/oc-harden) |
oc-compliance-ops | Control register + audit-ready evidence bundles at deploy time |
oc-bug-check | Pre-commit QA gate: types, lint, tests, anti-patterns, secrets |
oc-docs-forge | PR documentation packets, README/changelog/ADR upkeep |
oc-repo-ops | Repo hygiene + PR readiness gate: catalogs, generated files |
oc-git-ops | Branches, commits, PRs, sync |
oc-deploy-ops | Audit gate → staging → production with rollback |
oc-fleet-ops | Self-managed fleets: IaC, multi-container rollouts, day-2 ops |
oc-modularize-ops | Live-monolith decomposition with golden-fixture proof |
oc-monitoring-ops | Post-deploy observability — uptime, errors, alerts |
oc-scale-ops | Load tests, perf budgets, caching, capacity planning |
oc-migration-ops | DB / framework / auth / platform migrations |
oc-cost-ops | LLM cost attribution, budget gates, model-tier routing |
oc-telemetry-ops | Opt-in local usage metering, anonymized dashboard aggregates |
oc-reverse-spec | Reverse-engineer existing code into spec docs |
oc-release-ops | Version bumps, changelogs, release announcements |
oc-orchestrator | Cross-skill status and routing (/oc-ops) |
oc-checkpoint-protocol | Shared session-persistence schema (bundled in every skill) |
oc-update | Updates complete skill and runtime files while preserving local state |
oc-hindsight | Source-backed lessons, retrieval evaluation and external review |
oc-evolve | Task-tested rule proposals with regression checks and external approval |
Full descriptions, triggers, and examples: https://opchain.dev/skills
Every skill writes a JSON checkpoint to .checkpoints/ in your project. Skills read each other's checkpoints to make informed decisions — context flows forward without manual handoffs.
oc-deploy-ops reads oc-code-auditor — CRITICAL findings block deployoc-ux-engineer — grades frontend against the approved design specoc-git-ops reads oc-app-architect — names branches by sprintSchema lives in skills/oc-checkpoint-protocol/SKILL.md.
This is a public, force-push snapshot mirror of the skill source. The site, build system, and internal tooling live in a private upstream repo; only the product (this directory) is published here, refreshed on every change to main upstream.
See CONTRIBUTING.md for how issues and PRs flow back into the upstream repo.
Apache-2.0 — see LICENSE and NOTICE. Releases up to and including v1.8.2 were published under MIT.