FigmaExporterMcp
Allows inspection, export, and modification of Figma files through a development Figma plugin connected via WebSocket.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@FigmaExporterMcplist connected Figma files"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
FigmaExporterMcp
FigmaExporterMcp is a local bridge that lets Codex and other MCP clients inspect, export, and modify Figma files through a development Figma plugin.
Architecture
Codex / MCP client <--stdio--> MCP Server <--WebSocket :3066--> Figma Plugin
^
|
other Codex sessions proxy by HTTPThe first MCP server process owns the embedded relay on port 3066. Additional Codex sessions start normally, detect the occupied port, and proxy commands to the relay owner. This allows multiple Codex sessions to share one Figma plugin connection without port conflicts.
Related MCP server: figma-ui-mcp
Local Paths
Repository:
D:\LongWorkspace\FigmaExporterMcpMCP entry:
dist/server.jsServer source:
src/server.tsPlugin manifest:
figma-plugin/manifest.jsonPlugin code:
figma-plugin/code.jsPlugin UI:
figma-plugin/ui.html
Install and Build
cd D:\LongWorkspace\FigmaExporterMcp
npm install
npm run buildCodex Global MCP Config
Add this to C:\Users\chenlong\.codex\config.toml and restart Codex:
[mcp_servers.figma_exporter_mcp]
command = 'node'
args = ['D:\LongWorkspace\FigmaExporterMcp\dist\server.js']
startup_timeout_sec = 120
[mcp_servers.figma_exporter_mcp.env]
FIGMA_EXPORTER_RELAY_PORT = '3066'
FIGMA_EXPORTER_EXPORT_DIR = 'D:\LongWorkspace\FigmaExporterMcp\exports'Install the Figma Plugin
Open Figma.
Go to Plugins -> Development -> Import plugin from manifest.
Select
D:\LongWorkspace\FigmaExporterMcp\figma-plugin\manifest.json.Run the plugin in the Figma file you want Codex to access.
The plugin auto-connects to
ws://localhost:3066.
Multi-Session Usage
Use
get_connected_filesto list connected Figma files.Use
set_active_filewith a file name or channel keyword before mutating a design.Active file selection is scoped per Codex session, so sessions do not overwrite each other's active target.
If a session logs
Proxy mode, it is forwarding commands to the process that owns port3066; this is expected.
Development Notes
Modify
src/server.tsfor MCP tools, relay endpoints, proxy mode, and session routing.Modify
figma-plugin/code.jsfor Figma Plugin API command implementations.Modify
figma-plugin/ui.htmlfor connection UI, reconnect behavior, and WebSocket messaging.Run
npm run buildafter server changes and commit the regenerateddist/files.Keep
node_modules/,exports/, logs, andcopilot_temp/out of git.
Environment Variables
Variable | Default | Description |
|
| WebSocket/HTTP relay port |
|
| Local image export directory |
| auto-generated per MCP process | Optional stable session id for active-file routing |
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ChenLongbetterapp/FigmaExporterMcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server