Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 48,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

Local MCP bridge that exposes the ChatGPT Figma connector to OpenCode without launching Codex, using the existing authenticated session.

README.md

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.

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_AUTH_FILE | ~/.codex/auth.json | | CHATGPT_CONNECTORS_MCP_URL | https://chatgpt.com/backend-api/wham/apps | | CHATGPT_AUTH_TOKEN_URL | https://auth.openai.com/oauth/token | | CODEX_CLIENT_ID | Codex ChatGPT OAuth public client id | | CHATGPT_FIGMA_MCP_DEBUG | unset |

Development

npm run check
npm run smoke
npm run pack:dry

npm 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.

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Developer Tools servers.