TalkToFigma MCP
TalkToFigma: MCP integration between AI Agent (Cursor, Claude Code, Codex) and Figma, allowing Agentic AI to communicate with Figma for reading designs and modifying them programmatically.
Is TalkToFigma MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare TalkToFigma MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: TalkToFigma MCP scores 42.3/100 (Grade D), ranked #1120 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 1.6/10; 16% of recent commits are signed; last pushed 2026-07-26. Every point is earned from checkable signals — never paid placement. How scoring works →
How TalkToFigma MCP compares in MCP Servers
- #658 CleanSlice 42.4 +0.1
- #659 Multi Gmail MCP 42.3 ±0
- #660 TalkToFigma MCP 42.3 this agent
- #661 Openwebninja MCP 42.3 ±0
- #662 Gate DEX MCP 42.1 −0.2
Bars show each HVTrust score; the tick marks TalkToFigma MCP’s 42.3.
Where the 42.3 comes from
HVTrust dimensions vs the MCP Servers average
42.3 / 100 · 100.0% confidenceTalkToFigma MCP MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
53.0 / 100Supply Chain Trust
Common questions about TalkToFigma MCP
Does TalkToFigma MCP publish package provenance?
Does TalkToFigma MCP have an OpenSSF Scorecard?
Is TalkToFigma MCP actively maintained?
What license does TalkToFigma MCP use?
Are TalkToFigma MCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to TalkToFigma MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain TalkToFigma MCP?
For maintainers
HVTrust scores TalkToFigma MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/talktofigma-mcp)
<a href="https://hvtracker.net/agents/talktofigma-mcp"><img src="https://hvtracker.net/badge/talktofigma-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON