MrDynasty/dsh-figma-local-mcp

dsh-figma-local-mcp wires the harness-provided MCP client to the local Figma Desktop MCP server at 127.0.0.1:3845: it needs no Figma token and reads the currently open file, the selection and asset exports, exposes mcpfigmaget_design_context, get_screenshot, get_metadata, get_variable_defs, get_motion_context and get_figjam in every agent mode, and adds a global figma-design-to-code skill that adapts Figma output to the target repository.

dsh-figma-local-mcp is a global integration between DSH and the local Figma Desktop MCP server, with design-to-code guidance for every agent preset. It needs no Figma token and does not use the Figma REST API - it connects the harness-provided MCP client to the server Figma Desktop itself exposes at http://127.0.0.1:3845/mcp with auto-reconnect and non-blocking behavior when Figma is closed - so it can read the currently open file, the current selection and export assets. A global routing prompt sends any Figma URL, current selection, design-to-code request or asset-export request to the mcpfigma* tools (get_design_context, get_screenshot, get_metadata, get_variable_defs, get_motion_context, get_figjam) in every agent mode, and a global figma-design-to-code skill adapts Figma output to the target repository's conventions. Enabling the server is a one-time Figma Desktop step: open the file, switch to Dev Mode, open the MCP Server section and toggle Enable desktop MCP server.

Tools & Capabilities ★ 2
View on GitHub ↗

Install

dsh plugin --profile web add dsh-figma-local-mcp

Copied verbatim from the README's Install block; the README notes to restart the DSH web process afterwards and open a new conversation.

Compatibility

Requires macOS or Windows with Figma Desktop installed and signed in, and the DSH web process and Figma Desktop must run on the same machine because the MCP server listens on 127.0.0.1:3845. The plugin declares no npm dependency on @deepseek-ai/dsh-mcp-client - it only configures the host's own copy through the bundled cordis.patch.yml, so it always runs against the version DSH ships. 'missing peer @deepseek-ai/...' lines in the dsh plugin output are expected in every DSH plugin because profiles set autoInstallPeers: false and host packages are provided at runtime through the profile module fallback.

Details

Alternatives

1321928757/dsh-api-kit · 1321928757/dsh-mysql · 1624318455/dsh-plugin-tavily

More plugins in Tools & Capabilities

Browse more in Tools & Capabilities

Guides for Tools & Capabilities plugins