Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that use Figma + AI coding workflows and want agents to read design context instead of relying on manual copy-paste.
Who should use it
Who should skip it
Skip GLips/Figma-Context-MCP for now if you are only tracking items with a 'try now' verdict.
About this signal
GLips/Figma-Context-MCP is tracked by RepoRadar as a developer tool in the Radar section. It was first seen on 2026-06-17 and last updated on 2026-06-17. The current verdict is 'watch' with a Silver tier and moderate setup difficulty. The standout signals for GLips/Figma-Context-MCP are workflow potential (9.2) and open-source/build quality (8.4), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned GLips/Figma-Context-MCP a composite score of 8.4 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 90.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Requires design-file access token and project scope; keep MCP permissions scoped to needed files; Could expose design-sensitive content if token scope is too broad.