opencode-figma-for-actually-codex
Provides tools for interacting with Figma via the ChatGPT Figma connector, enabling design-related operations such as accessing and manipulating Figma files.
Click on "Deploy 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., "@opencode-figma-for-actually-codexList all frames in the current Figma file"
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.
opencode-figma-for-actually-codex
Local MCP bridge that exposes the ChatGPT Figma connector to OpenCode without launching Codex.
This package is useful when OpenCode cannot complete Figma's remote MCP OAuth flow directly, but the same Figma connector is already authenticated in the ChatGPT/Codex account file.
How it works
Reads the existing ChatGPT auth file from
~/.codex/auth.json.Calls ChatGPT's connector MCP endpoint directly.
Filters the upstream tool list to the Figma connector only.
Exposes those tools over stdio as a local MCP server for OpenCode.
Refreshes the ChatGPT access token from the same auth file when it is close to expiry.
It does not start Codex, call codex mcp-server, or require the Codex app to be
running.
Related MCP server: codex-chatgpt-bridge
OpenCode config
From GitHub:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"figma": {
"type": "local",
"command": [
"npx",
"-y",
"github:kargnas/opencode-figma-for-actually-codex"
],
"enabled": true,
"timeout": 60000
}
}
}After publishing to npm, the command can be shortened to:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"figma": {
"type": "local",
"command": ["npx", "-y", "opencode-figma-for-actually-codex"],
"enabled": true,
"timeout": 60000
}
}
}For local development:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"figma": {
"type": "local",
"command": [
"node",
"/path/to/opencode-figma-for-actually-codex/bin/chatgpt-figma-mcp.mjs"
],
"enabled": true,
"timeout": 60000
}
}
}Prerequisites
The default auth source is ~/.codex/auth.json, and it must contain a ChatGPT
login with tokens.access_token. The Figma connector must already be connected
to that ChatGPT account.
Supported environment variables:
Variable | Default |
|
|
|
|
|
|
| Codex ChatGPT OAuth public client id |
| unset |
Development
npm run check
npm run smoke
npm run pack:drynpm run smoke connects to the live ChatGPT connector endpoint and verifies
that Figma tools can be listed.
Security
Do not commit ~/.codex/auth.json, exported account files, token caches, or
debug logs that contain credentials. This package reads the local auth file at
runtime and does not need secrets in opencode.jsonc.
This server cannot be deployed
Maintenance
Related MCP Connectors
- QuallaaOAuthcom.quallaa
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
MCP connector that lets ChatGPT list, search, and run your Apple Shortcuts via a local Mac agent
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
The OpenRouter MCP server plugs OpenRouter into the AI tools you already use. Once connected, your assistant can pull live OpenRouter data (models, prices, your credits, rankings, and docs) and send quick test messages, all without leaving your editor.
Related MCP Servers
- AlicenseAqualityBmaintenanceBridges OpenAI Codex CLI to any MCP client, allowing headless Codex sessions via tools like codex and codex-reply.217 npm1MIT
- AlicenseNot gradedqualityBmaintenanceLocal MCP bridge enabling ChatGPT web to access approved local files and execute tasks via local Codex.7MIT
- FlicenseCqualityBmaintenanceLocal bridge enabling AI agents to inspect and edit the currently open Figma Desktop file through the Figma Plugin API.291-
- AlicenseBqualityBmaintenanceLocal MCP server connecting AI clients to the Figma desktop app for inspecting and editing Figma documents via the Plugin API.16253 npm1MIT