Figma-Context-MCP
MCP server to provide Figma layout information to AI coding agents like Cursor
Runssource: GitHubhomepageTypeScriptMITcommit c083d65c7e00
TypeScript, MIT licensed. The project labels itself: ai, cursor, figma, mcp and typescript.
Figma-Context-MCP runs. An Argusic agent installed it in 6.2 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Figma MCP server installs, builds, type-checks, passes all 250 tests, and runs an HTTP MCP server that accepts initialize and tools/list requests on the configured port.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 94.7 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18.19.1 installed but project requires >=20.20.01.5 minutes
- pnpm not available in system0.5 minutes
- .npmrc set prefix=/home/runner/.npm-global but the directory did not exist, causing npm install errors0.2 minutes
- Install time
- 6 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pnpm test: 18 passed, 250 tests passed, 1 skipped (exit 0); pnpm build: tsup build success; pnpm type-check: no errors; curl POST to /mcp returned valid MCP responses
- Model tokens used
- 80,467
- Exact commit tested
- c083d65c7e00
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
exec /bin/sh -lc 'mv /work/repo/.npmrc.bak /work/repo/.npmrc 2>/dev/null; echo "restored"' in /work/repo succeeded in 0ms: restored All tests pass, the HTTP server responds correctly, and the build succeeds. Here's the summary: ``` ``` tokens used 80,467 All tests pass, the HTTP server responds correctly, and the build succeeds. Here's the summary: ``` ```
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Took 6.2 minutes to install, slower than the median of the 36 comparable projects Argusic has measured.
Of the 37 ai projects Argusic has installed and timed, Figma-Context-MCP was the 21st fastest to reach a running state, and 30 of 37 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 6.2 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 3/3 | Runs with mocks | 92.00 | 0.01 | |
| Argusic Runner | 2/3 | Runs | 100.00 | 0.02 | |
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.02 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/figma-context-mcp)Questions
- Does Figma-Context-MCP run?
- Yes. Figma-Context-MCP runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test Figma-Context-MCP?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c083d65c7e00. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Figma-Context-MCP?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Figma-Context-MCP take to install?
- 6.2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does Figma-Context-MCP need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Figma-Context-MCP?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Figma-Context-MCP compare with the alternatives?
- Of the 37 ai projects Argusic has installed and timed, Figma-Context-MCP was the 21st fastest to reach a running state, and 30 of 37 reached one at all.
- Where is the evidence for Figma-Context-MCP?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.