dsh-figma-mcp
Bridges the official Figma MCP server over stdio, exposing Figma's 47 tools with unmodified schemas so MCP clients can interact with Figma and the Figma plugin API using reusable OAuth credentials.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
dsh-figma-mcp
Figma MCP over stdio, for DeepSeek Harness and any other MCP client.
Upstream |
|
Downstream | stdio, MCP |
Tools exposed | 47 — Figma's list, unmodified schemas |
LLM turns per call | 0 — the bridge talks HTTP directly |
Credentials | reused from the host that already authorized Figma |
Why this exists
DSH's @deepseek-ai/dsh-mcp-client speaks stdio and streamable-http with a static header set. Figma's MCP needs an OAuth bearer token that expires, and a proxy cannot mint one:
$ curl -X POST https://api.figma.com/v1/oauth/mcp/register -d '…'
Forbidden # HTTP 403 — no dynamic client registration
$ curl -X POST https://api.figma.com/v1/oauth/token \
-d 'grant_type=refresh_token&refresh_token=…&client_id=…'
{"error":"Client ID and client secret are required"} # no secret to sendBoth were measured against the live service. A refresh_token grant with a bare client_id is refused, and the registration endpoint is closed, so a new client cannot bootstrap itself. The only working path is to reuse the credential an already-authorized client stored — which is exactly what this bridge does, then republishes Figma's tools over stdio with a token it can refresh-by-reconnect.
The alternative in most setups is pointing an agent CLI at Figma and paying a model turn per call. Here a use_figma push costs zero tokens.
Related MCP server: Figma Bridge
Install
git clone https://github.com/yoobinkim541/dsh-figma-mcp.git
cd dsh-figma-mcp
npm install
node bin/dsh-figma-mcp.js doctordoctor prints every credential it can see and then calls whoami upstream:
credentials
keyring:Codex MCP Credentials/Figma|d39d3b62 access=figu… refresh=yes expires in 90d client=pADEsf…
upstream https://mcp.figma.com/mcp
ok: 47 tools, user yoobin kimNo build step. No native compilation — the keyring binding ships prebuilt binaries for Linux, macOS and Windows.
Getting a credential
The bridge reads, in order:
DSH_FIGMA_TOKEN(orFIGMA_MCP_TOKEN) — an access token, for CI.~/.dsh-figma-mcp/credentials.json— written bydsh-figma-mcp login.The OS keyring entry
Codex MCP Credentials/Figma|*— whatcodex mcp login Figmawrites.~/.claude/.credentials.jsonand~/.claude.json— Claude Code / desktopmcpOAuthentries.
Any one is enough. The most common setup is to authorize Figma once in a host that stores an OAuth token:
codex mcp login Figma # once; the bridge then reuses that credentialIf you already have a token, store it directly and skip the keyring entirely:
DSH_FIGMA_TOKEN=figu_… node bin/dsh-figma-mcp.js loginlogin verifies the token against the live server before writing it, so a stored credential is never one that fails at the first call.
Discovery is read-only: it never writes into another tool's store.
Connect to DeepSeek Harness
Append to ~/.dsh/cordis.patch.yml (all profiles) or ~/.dsh/profiles/<name>/cordis.patch.yml:
- insert:
- id: figma-mcp
name: "@deepseek-ai/dsh-mcp-client"
config:
serverName: figma
transport: stdio
# Absolute path: DSH scrubs the ambient environment, so a bare `node`
# from a version manager may not resolve.
command: /usr/bin/node
args:
- /absolute/path/to/dsh-figma-mcp/bin/dsh-figma-mcp.js
toolCallTimeoutMs: 120000
failOnStartupError: trueRestart the harness. Each Figma tool appears as mcp__figma__<tool>:
$ dsh headless "Call mcp__figma__whoami and report the handle."
- Handle: yoobin kim · Plan: … (student, Full seat, admin)Two configuration notes that cost real debugging time:
failOnStartupError: true— without it a credential problem leaves the harness running with zero Figma tools and no error in the tool list. The model then reports "no Figma MCP server is connected", which is technically true but hides the cause.No
env:block —dsh-mcp-clientvalidatesenvvalues as strings, and!!js … || undefinedproducesundefined, which fails schema validation at load. Credentials come from discovery, so the block is unnecessary.
Other MCP clients
The bridge is a plain stdio server, so the same command works anywhere:
// Claude Code / Claude Desktop ~/.claude.json
{
"mcpServers": {
"figma": {
"command": "node",
"args": ["/absolute/path/to/dsh-figma-mcp/bin/dsh-figma-mcp.js"]
}
}
}# Codex ~/.codex/config.toml
[mcp_servers.figma]
command = "node"
args = ["/absolute/path/to/dsh-figma-mcp/bin/dsh-figma-mcp.js"]CLI
dsh-figma-mcp run the stdio bridge
dsh-figma-mcp doctor credentials + upstream reachability
dsh-figma-mcp tools print the 47 upstream tool names
dsh-figma-mcp login verify and store a tokenVariable | Meaning |
| access token; overrides discovery |
| optional refresh token to pair with it |
| upstream URL (default |
| where |
| extra discovery paths |
How it works
MCP client ──stdio──▶ dsh-figma-mcp ──HTTPS+Bearer──▶ mcp.figma.com/mcp
│
├── credentials.js discover + normalize every store
├── upstream.js connect, list, call, reconnect on 401
└── server.js expose tools verbatim + provenanceThree behaviours are deliberate:
Tool schemas pass through untouched. Only a one-line provenance prefix is added to each description. Rewriting use_figma's arguments would break the Figma plugin-API contract, and the nodeId strings the rest of the tool set expects are exact.
A 401 reconnects once, then retries. The SDK's streamable transport takes a static requestInit, so there is no per-request hook to refresh mid-flight; reconnecting with a freshly discovered credential is the equivalent. The retry is safe because an auth failure means the request never reached a tool.
Errors surface as MCP errors. A failed call throws with a hint; nothing is turned into a silent empty result, which would look to the model like a tool that succeeded with no output.
Limitations
No dynamic registration.
POST /v1/oauth/mcp/registeris 403, sologinneeds a token you already obtained. There is no browser-based "click to authorize" flow in this package.Token lifetime is the host's. With a token from
codex mcp login Figma, the bridge inherits its ~90-day lifetime. When it expires, re-authorize in that host; the bridge picks up the new value on the next start.refresh_tokenis unused. Figma requires a client secret alongside it, and no supported store keeps one. ArefreshTokenis carried throughnormalize()for future use but never spent.Resources and prompts are empty. Figma exposes tools only; those two namespaces answer with empty lists.
Linux keyring needs a running Secret Service. On a headless box use
DSH_FIGMA_TOKEN;doctorsays so when discovery comes up empty.
Tests
npm test # 10 checks: normalization, auth detection, stdio handshake
DSH_FIGMA_SKIP_LIVE=1 npm test # skip the live handshake (no network / no credential)The live check spawns the real binary over stdio and asserts the initialize handshake, so a broken entry point fails the suite rather than shipping.
Upstream
DeepSeek Harness does not accept external pull requests at the moment (CONTRIBUTING.md: "we cannot accept external pull requests at the moment"). The supported route is the ecosystem: this repository is tagged dsh-plugin so it is discoverable, and the harness README's own guidance is to treat the official repo as a source of inspiration rather than a gate.
If the upstream policy changes, src/ is dependency-light and framework-agnostic; server.js is ~120 lines over the MCP SDK.
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Toolstile is a managed MCP gateway that connects remote MCP servers behind one endpoint, with per-agent permissions, shared accounts and activity logs. Connect at https://mcp.toolstile.com/mcp over Streamable HTTP with OAuth; sign in at https://toolstile.com, select a workspace and connect your upstream servers. Available tools, resources and prompts depend on that workspace and the agent's granted access.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables local MCP clients to access tools from a remote FastMCP server over stdio, handling OAuth authentication and Streamable HTTP communication.-
- AlicenseNot gradedqualityBmaintenanceConnects an MCP client such as Claude Code to the Figma file open in the desktop app, letting the agent create frames, write text, apply styles, import images and SVGs, take screenshots, and run arbitrary Figma Plugin API code. Commands travel through a local development plugin instead of Figma's web API, so there are no tokens, quotas, or rate limits.50 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables a stdio-capable MCP client to connect through a local OAuth bridge to Canva's official MCP server, forwarding tool and resource requests using read-only scopes and per-user credentials.49 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables Cursor and Claude Desktop to connect to a remote host daemon over stdio and invoke its MCP tools, including device listing and single-tool calls.MIT