Loading ToolBench

Reading the current corpus…

figma-cli MCP server · F · ToolBench

← Browse

figma-cli

github.com/BoltDoggy/figma-cli

Figma REST API CLI - Figma MCP Server proxy with command-line wrapper

2026-07-28+STDIO1 tools

39/100

Definition Quality45

Protocol Readiness50

Supportability21

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · detected: Dynamic Client Registration

Deprecated protocol patterns detected

Summary

This server is a proxy/CLI wrapper around an upstream Figma MCP server (https://mcp.figma.com/mcp). It does NOT define its own tools, it forwards tool definitions from upstream. The single tool 'use_figma' is inferred from CLI usage, not explicitly registered in the source. The tool has a basic description (48 chars) and a schema with three string parameters, but lacks critical details: no enum constraints, no format specifications, no error recovery guidance, and no documentation of what 'Figma plugin JavaScript code' means or what outputs to expect. The description does not explain prerequisites, failure modes, or when to use this vs other Figma operations.

Tools (1)

use_figmawriteauthsource verified45/100

Execute JavaScript design operations in a Figma file

Issues (5)

CRITICALtool ↗

Tool definition is inferred from CLI code, not explicitly registered in MCP server. No explicit tool registration with schema visible in src/mcp/server.ts, tools are proxied from upstream without local definition.

use_figma

HIGHtool-description ↗

Description lacks actionable context. 'Execute JavaScript design operations in a Figma file' (48 chars) does not explain what 'design operations' means, what the code parameter should contain, what outputs to expect, or when this tool is appropriate vs other Figma operations.

use_figma

HIGHresponse-shaper ↗

No output schema documented. The tool returns content as an array of objects with 'type' and 'text' fields, but this structure is not declared in the tool definition. LLMs cannot plan downstream operations without knowing the response shape.

use_figma

HIGHconstrained-input ↗

Parameter 'code' lacks format/constraint documentation. No guidance on what constitutes valid Figma plugin JavaScript, required APIs, or common patterns. LLMs will hallucinate invalid code.

Recommendations

Explicitly register the 'use_figma' tool in src/mcp/server.ts with a full JSON Schema definition including output schema. Do not rely on upstream proxy, define it locally with complete metadata.
Expand tool description to 100-150 chars: 'Execute custom JavaScript in a Figma file to read/modify design elements. Returns JSON result or error. Requires valid Figma file key and plugin-compatible code (see Figma plugin API docs).'
Add parameter descriptions: 'code' → 'Figma plugin JavaScript code (must use figma.* APIs; see https://www.figma.com/plugin-docs/). Common: figma.currentPage.selection, figma.createRectangle().' 'fileKey' → 'Figma file identifier (from URL: figma.com/file/{fileKey}/...). Must have edit access.'
Document output schema: 'Returns {success: boolean, result?: any, error?: string}. On success, result contains the return value of the code. On error, error field explains the failure (auth, invalid file, code exception).'
Add error recovery hints to description: 'If auth fails, run: figma auth oauth-login. If file not found, verify fileKey. If code fails, check Figma plugin API compatibility.'

Score history

Overall score trend

First recorded score · v2 rubric

39/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	39	2026-07-28+	v2