| FMRS | 64 / 100 · C | 80 / 100 · B | 79 / 100 · B |
|---|
| Reliability | 7 / 20 | 14 / 20 | 12 / 20 |
|---|
| Security and permissions | 12 / 20 | 16 / 20 | 16 / 20 |
|---|
| Maintenance | 14 / 20 | 17 / 20 | 18 / 20 |
|---|
| Documentation | 17 / 20 | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 14 / 20 | 18 / 20 | 15 / 20 |
|---|
| Best for | - Product and frontend teams with paid Figma seats (Dev/Full) who frequently generate code from designs
- Teams with well-structured design systems using components, variables, and Auto Layout
- Teams using Code Connect to keep generated code consistent with real components
| - Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
- Scenarios wanting zero-config documentation lookup
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - Use cases requiring an offline or local stdio MCP server (this server is remote Streamable HTTP only)
- Starter plan users or View/Collab seat holders, who are capped at 6 tool calls per month
- Scenarios needing direct local filesystem access (this server provides Figma design data, not filesystem access)
| - Looking up internal/private codebase documentation (Context7 targets publicly published open-source libraries)
- Cases needing very high coverage of obscure, niche libraries (coverage depends on what Context7's platform has indexed)
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
|---|
| Required permissions | - Requires Figma account authentication (e.g. `/mcp auth figma` in Gemini CLI) to access files the user has permission to view
- The remote server can read design data (layers, variables, styles, screenshots) for selected Figma nodes
- The write-to-canvas feature (remote server only) can create/modify frames, components, variables, and Auto Layout in Figma files
| - Usable without an API key (subject to a free-tier rate limit); CONTEXT7_API_KEY is an optional credential for higher quota
- Read-only documentation lookup — no code execution or local filesystem access involved
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
|---|
| Risks and side effects | - Design data is processed through Figma's officially hosted remote server and your AI client, not run locally
- Write-to-canvas access could unintentionally modify real Figma files if an agent follows a bad instruction
- Read-type tool calls are rate limited per Figma plan/seat; Starter and View/Collab seat users are capped at just 6 calls per month
- Write-to-canvas is currently free during beta but is expected to become a usage-based paid feature
| - The free tier has limited quota — high-frequency use may hit rate limits
- Documentation content comes from Context7's platform index, so its accuracy and freshness depend on that platform's crawl cadence
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
|---|
| Supported clients | VS Code, Cursor, Claude Code, Gemini CLI | Claude Code, VS Code, Cursor, Cline, Amp | Claude Desktop, VS Code, Cursor, Smithery.ai |
|---|
| Tools | 4 | 2 | 19 |
|---|