Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk

get_svg

Export a Figma node to SVG markup by specifying the node ID. Returns the SVG string including all nested children.

Instructions

Export a single node as an SVG string from Figma. Returns the SVG markup including all nested children.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to export as SVG

Implementation Reference

  • The handler function for the 'get_svg' tool. It receives a nodeId, sends the 'get_svg' command to Figma via WebSocket with a 120s timeout, and returns the SVG markup string as text content.
      async ({ nodeId }) => {
        try {
          const result = await sendCommandToFigma("get_svg", { nodeId }, 120000);
          const typedResult = result as { svgString: string; name: string };
          return {
            content: [
              {
                type: "text",
                text: typedResult.svgString,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error exporting SVG: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
          };
        }
      }
    );
  • Registration of the 'get_svg' tool on the MCP server via server.tool(), including its description 'Export a single node as an SVG string from Figma' and its schema (nodeId: string).
    server.tool(
      "get_svg",
      "Export a single node as an SVG string from Figma. Returns the SVG markup including all nested children.",
      {
        nodeId: z.string().describe("The ID of the node to export as SVG"),
      },
      async ({ nodeId }) => {
        try {
          const result = await sendCommandToFigma("get_svg", { nodeId }, 120000);
          const typedResult = result as { svgString: string; name: string };
          return {
            content: [
              {
                type: "text",
                text: typedResult.svgString,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error exporting SVG: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
          };
        }
      }
    );
  • Input schema for 'get_svg': expects a single required 'nodeId' parameter of type z.string().
    {
      nodeId: z.string().describe("The ID of the node to export as SVG"),
    },
  • The sendCommandToFigma function that dispatches the 'get_svg' command over WebSocket to the Figma plugin and returns a promise that resolves with the result (including svgString).
    export function sendCommandToFigma(
      command: FigmaCommand,
      params: unknown = {},
      timeoutMs: number = 300000
    ): Promise<unknown> {
      return new Promise((resolve, reject) => {
        // If not connected, try to connect first
        if (!ws || ws.readyState !== WebSocket.OPEN) {
          connectToFigma();
          reject(new Error("Not connected to Figma. Attempting to connect..."));
          return;
        }
    
        // Check if we need a channel for this command
        const requiresChannel = command !== "join";
        if (requiresChannel && !currentChannel) {
          reject(new Error("Must join a channel before sending commands"));
          return;
        }
    
        const id = uuidv4();
        const request = {
          id,
          type: command === "join" ? "join" : "message",
          ...(command === "join"
            ? { channel: (params as any).channel, sessionId: SESSION_ID }
            : { channel: currentChannel }),
          message: {
            id,
            command,
            params: {
              ...(params as any),
              commandId: id, // Include the command ID in params
            },
          },
        };
    
        // Set timeout for request
        const timeout = setTimeout(() => {
          if (pendingRequests.has(id)) {
            pendingRequests.delete(id);
            logger.error(`Request ${id} to Figma timed out after ${timeoutMs / 1000} seconds`);
            reject(new Error('Request to Figma timed out'));
          }
        }, timeoutMs);
    
        // Store the promise callbacks to resolve/reject later
        pendingRequests.set(id, {
          resolve,
          reject,
          timeout,
          lastActivity: Date.now()
        });
    
        // Send the request
        logger.info(`Sending command to Figma: ${command}`);
        logger.debug(`Request details: ${JSON.stringify(request)}`);
        ws.send(JSON.stringify(request));
      });
    }
  • The registerTools() function that aggregates all tool registrations; registerSvgTools(server) is called at line 25.
    export function registerTools(server: McpServer): void {
      // Register all tool categories
      registerDocumentTools(server);
      registerCreationTools(server);
      registerModificationTools(server);
      registerTextTools(server);
      registerComponentTools(server);
      registerImageTools(server);
      registerSvgTools(server);
      registerVariableTools(server);
      registerFigJamTools(server);
      registerStyleTools(server);
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the burden. It states the return includes nested children but does not mention if the operation is read-only, permissions needed, or any side effects. For a read-like tool, this is acceptable but not fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences convey purpose and return format with zero redundancy. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, no-output-schema tool, the description adequately covers purpose and return. It could mention that the operation is non-destructive, but given the simplicity, it is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, baseline is 3. The description adds value by clarifying the parameter 'nodeId' refers to a single node and that the export includes nested children, exceeding the schema's minimal description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool exports a single node as an SVG string, specifying the return format ('SVG markup including all nested children'). It distinguishes from siblings like 'export_node_as_image' and 'set_svg' by focusing on SVG string export.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives (e.g., 'export_node_as_image', 'set_svg'). The description implies usage for SVG string export but lacks when-not or exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arinspunk/claude-talk-to-figma-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server