Skip to main content
Glama
paragdesai1

Cursor Talk to Figma MCP

by paragdesai1

set_stroke_color

Change the stroke color of Figma design elements using RGB values and optional transparency settings.

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 Figma plugin implementation that sets the stroke color and optional weight on the specified node by updating node.strokes and node.strokeWeight.
    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 schema validation with Zod 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)
                  }`,
              },
            ],
          };
        }
      }
    );
  • Dispatch handler in Figma plugin's main command switch that routes set_stroke_color calls to the setStrokeColor implementation.
    case "set_stroke_color":
      return await setStrokeColor(params);
  • Zod schema for input validation of set_stroke_color tool parameters.
    {
      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"),
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a mutation operation ('Set'), which implies it modifies data, but provides no information about permissions required, whether changes are reversible, error conditions, or what happens if the node doesn't exist. For a mutation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 communicates the core purpose without any wasted words. It's appropriately sized for a straightforward tool and is front-loaded with the essential information. Every word earns its place in this concise formulation.

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?

Given this is a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address what the tool returns, error conditions, or behavioral constraints. While the schema covers parameters well, the overall context for using this tool safely and effectively is lacking, especially for a write operation in a design environment.

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 all parameters are documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema fields. According to scoring rules, when schema coverage is high (>80%), the baseline score is 3 even with no param info in the description, which applies here.

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 resource ('stroke color of a node in Figma'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like 'set_fill_color' or 'set_text_content', but the specificity of 'stroke color' provides inherent differentiation. The description avoids tautology by not just repeating the tool name.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when this operation is appropriate, what prerequisites might exist (like needing a valid node ID), or when to choose other color-related tools like 'set_fill_color'. The agent must infer usage purely from the tool name and parameter schema.

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/paragdesai1/parag-Figma-MCP'

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