Figma Codex Bridge (xiaobai59/figma-codex-bridge) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 7 tools. No publisher has claimed this listing.

C
Emerging
74/100

Figma Codex Bridge

Enables Codex and other MCP clients to read design context from Figma Desktop via a local bridge, providing design tokens, component trees, and screenshots without an API token.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

xiaobai59

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: FIGMA_LOCAL_MCP_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 1 credential: FIGMA_LOCAL_MCP_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes7 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

figma_status

Check whether the local Figma Desktop plugin is connected and report the active file/page.

figma_get_file_metadata

Read metadata for the Figma file currently open in Figma Desktop.

figma_get_page_structure

Read the top-level nodes on a Figma page. Defaults to the current page.

figma_get_selection

Read the current Figma selection, including layout, text, fills, and a bounded child tree.

figma_get_node

Read one Figma node by ID, including its bounded child tree.

figma_get_design_context

Build an implementation-ready context pack for the current selection or a Figma node, including bounded structure, tokens, components, variables, styles, assets, and an optional screenshot.

figma_get_screenshot

Export the current selection or a Figma node as a PNG image for visual comparison.

// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configFIGMA_LOCAL_MCP_PORT
🔐 secretFIGMA_LOCAL_MCP_TOKEN
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

7/7 tools missing one or more hints — figma_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); figma_get_file_metadata (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); figma_get_page_structure (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/xiaobai59/figma-codex-bridge)](https://m8ven.ai/mcp/xiaobai59/figma-codex-bridge)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: b2968c649534be04946ffe053d6bc4e20a63fe69
code hash: ba0f56448af147894d6846a891e59395341d7ae73da04ff23ca6e881ae1e0de5
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client