Skip to main content
Glama
yhc984

Talk to Figma MCP

by yhc984

set_stroke_color

Change the stroke color of a Figma design element by specifying its node ID and RGB color values.

Instructions

Set the stroke color of a node in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to modify
rYesRed component (0-1)
gYesGreen component (0-1)
bYesBlue component (0-1)
aNoAlpha component (0-1)
weightNoStroke weight

Implementation Reference

  • Core handler function that executes the set_stroke_color logic: fetches the Figma node, sets its stroke paint to SOLID with given RGBA color and optional weight using Figma Plugin API.
    async function setStrokeColor(params) {
      const {
        nodeId,
        color: { r, g, b, a },
        weight = 1,
      } = params || {};
    
      if (!nodeId) {
        throw new Error("Missing nodeId parameter");
      }
    
      const node = await figma.getNodeByIdAsync(nodeId);
      if (!node) {
        throw new Error(`Node not found with ID: ${nodeId}`);
      }
    
      if (!("strokes" in node)) {
        throw new Error(`Node does not support strokes: ${nodeId}`);
      }
    
      // Create RGBA color
      const rgbColor = {
        r: r !== undefined ? r : 0,
        g: g !== undefined ? g : 0,
        b: b !== undefined ? b : 0,
        a: a !== undefined ? a : 1,
      };
    
      // Set stroke
      const paintStyle = {
        type: "SOLID",
        color: {
          r: rgbColor.r,
          g: rgbColor.g,
          b: rgbColor.b,
        },
        opacity: rgbColor.a,
      };
    
      node.strokes = [paintStyle];
    
      // Set stroke weight if available
      if ("strokeWeight" in node) {
        node.strokeWeight = weight;
      }
    
      return {
        id: node.id,
        name: node.name,
        strokes: node.strokes,
        strokeWeight: "strokeWeight" in node ? node.strokeWeight : undefined,
      };
    }
  • MCP server tool registration for 'set_stroke_color', including Zod input schema and handler that proxies the command to the Figma plugin via WebSocket.
    server.tool(
      "set_stroke_color",
      "Set the stroke color of a node in Figma",
      {
        nodeId: z.string().describe("The ID of the node to modify"),
        r: z.number().min(0).max(1).describe("Red component (0-1)"),
        g: z.number().min(0).max(1).describe("Green component (0-1)"),
        b: z.number().min(0).max(1).describe("Blue component (0-1)"),
        a: z.number().min(0).max(1).optional().describe("Alpha component (0-1)"),
        weight: z.number().positive().optional().describe("Stroke weight")
      },
      async ({ nodeId, r, g, b, a, weight }) => {
        try {
          const result = await sendCommandToFigma('set_stroke_color', {
            nodeId,
            color: { r, g, b, a: a || 1 },
            weight: weight || 1
          });
          const typedResult = result as { name: string };
          return {
            content: [
              {
                type: "text",
                text: `Set stroke color of node "${typedResult.name}" to RGBA(${r}, ${g}, ${b}, ${a || 1}) with weight ${weight || 1}`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting stroke color: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • Figma plugin's command dispatcher that handles incoming 'set_stroke_color' command by calling the setStrokeColor handler.
    async function handleCommand(command, params) {
      switch (command) {
        case "get_document_info":
          return await getDocumentInfo();
        case "get_selection":
          return await getSelection();
        case "get_node_info":
          if (!params || !params.nodeId) {
            throw new Error("Missing nodeId parameter");
          }
          return await getNodeInfo(params.nodeId);
        case "create_rectangle":
          return await createRectangle(params);
        case "create_frame":
          return await createFrame(params);
        case "create_text":
          return await createText(params);
        case "set_fill_color":
          return await setFillColor(params);
        case "set_stroke_color":
          return await setStrokeColor(params);
        case "move_node":
          return await moveNode(params);
        case "resize_node":
          return await resizeNode(params);
        case "delete_node":
          return await deleteNode(params);
        case "get_styles":
          return await getStyles();
        case "get_local_components":
          return await getLocalComponents();
        case "get_team_components":
          return await getTeamComponents();
        case "create_component_instance":
          return await createComponentInstance(params);
        case "export_node_as_image":
          return await exportNodeAsImage(params);
        case "execute_code":
          return await executeCode(params);
        case "set_corner_radius":
          return await setCornerRadius(params);
        default:
          throw new Error(`Unknown command: ${command}`);
      }
    }
  • TypeScript union type including 'set_stroke_color' for Figma command validation.
    type FigmaCommand =
      | 'get_document_info'
      | 'get_selection'
      | 'get_node_info'
      | 'create_rectangle'
      | 'create_frame'
      | 'create_text'
      | 'set_fill_color'
      | 'set_stroke_color'
      | 'move_node'
      | 'resize_node'
      | 'delete_node'
      | 'get_styles'
      | 'get_local_components'
      | 'get_team_components'
      | 'create_component_instance'
      | 'export_node_as_image'
      | 'execute_code'
      | 'join'
      | 'set_corner_radius';
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose whether this is a destructive operation, what permissions are needed, whether changes are reversible, what happens if the node doesn't exist, or what the response looks like. For a mutation tool with zero annotation coverage, this is insufficient.

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?

The description is a single, efficient sentence that gets straight to the point with zero wasted words. It's perfectly front-loaded and appropriately sized for this tool.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens on success/failure, what permissions are required, or how this operation fits into the broader Figma context. The agent would be left guessing about important behavioral aspects.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already fully documents all 6 parameters. The description doesn't add any additional meaning about parameters beyond what's in the schema. The baseline of 3 is appropriate when the schema does all the work.

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

Purpose4/5

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

The description clearly states the action ('Set') and target ('stroke color of a node in Figma'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'set_fill_color' or 'set_corner_radius' beyond the obvious difference in what property is being set.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing a valid node ID), when not to use it, or how it relates to similar tools like 'set_fill_color' or 'set_corner_radius'.

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/yhc984/cursor-talk-to-figma-mcp-main'

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