Analysis updated 2026-05-18
Connect ZCode to Figma's MCP server even though ZCode isn't on Figma's approved client list.
Manually inject OAuth tokens into ZCode's encrypted credentials file.
Re-authenticate with Figma's MCP server when saved access tokens expire.
Debug why ZCode's Figma MCP connection isn't showing as connected.
| darkgenius/zcode-figma-mcp | 0xmukesh/docusaurus-tutorial | a15n/andrewscheuermann | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | JavaScript | JavaScript | JavaScript |
| Last pushed | — | 2021-12-27 | 2015-01-11 |
| Maintenance | — | Dormant | Dormant |
| Setup difficulty | moderate | easy | moderate |
| Complexity | 3/5 | 2/5 | 1/5 |
| Audience | developer | developer | general |
Figures from each repo's GitHub metadata at analysis time.
Requires ZCode to have already attempted (and failed) a Figma MCP connection once before running this script.
zcode-figma-mcp is a small helper script that solves a specific compatibility problem between two developer tools. ZCode is a coding assistant that can connect to external services through something called MCP, a protocol that lets it use extra tools like Figma's design service. Normally, connecting to Figma's MCP server requires going through a login process, but Figma only allows a fixed list of approved application names to complete that login, and ZCode is not on that approved list, so the standard connection attempt fails before it even starts. This script works around the restriction by using a different, already approved application name during the login step, completing the full login process that way, and then taking the resulting access codes and saving them directly into ZCode's own local storage of login credentials. Once that is done, ZCode can use those saved credentials normally the next time it starts, without needing to go through its own blocked login attempt again. To use the script, you need Node.js version 20 or newer, and you must have already tried connecting ZCode to the Figma service at least once, even though that attempt fails, because ZCode needs to have recorded some initial information about the connection first. Running the script opens your web browser so you can approve the login through Figma's own website, then it captures the response, encrypts it using the same method ZCode already uses to protect its saved credentials, and writes it into ZCode's credentials file. It automatically makes a backup of that file first and double checks that what it wrote can be read back correctly before finishing. The saved login eventually expires, roughly every ninety days, at which point you simply run the script again and restart ZCode. The project also documents a handful of specific error messages and their fixes, covering things like browser connection issues on Mac computers and cases where the script cannot figure out which saved entry belongs to Figma.
A helper script that lets ZCode authenticate with Figma's MCP server by working around Figma's fixed list of approved client names, then saving the resulting login into ZCode's credentials file.
Mainly JavaScript. The stack also includes Node.js, JavaScript, OAuth.
No license information is stated in the README.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.