Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk

set_stroke_color

Set the stroke color of a Figma node by providing red, green, and blue values. Optionally adjust alpha and stroke weight for precise border control.

Instructions

Set the stroke color of a node in Figma (defaults: opacity 1, weight 1)

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)
strokeWeightNoStroke weight >= 0)

Implementation Reference

  • The main tool handler for 'set_stroke_color'. Registers the MCP tool with Zod schema for nodeId, r, g, b (required), a and strokeWeight (optional). Handler validates inputs, applies defaults (opacity=1, weight=1), and calls sendCommandToFigma with the command payload.
    // Set Stroke Color Tool
    server.tool(
      "set_stroke_color",
      "Set the stroke color of a node in Figma (defaults: opacity 1, weight 1)",
      {
        nodeId: z.string().describe("The ID of the node to modify"),
        r: z.coerce.number().min(0).max(1).describe("Red component (0-1)"),
        g: z.coerce.number().min(0).max(1).describe("Green component (0-1)"),
        b: z.coerce.number().min(0).max(1).describe("Blue component (0-1)"),
        a: z.coerce.number().min(0).max(1).optional().describe("Alpha component (0-1)"),
        strokeWeight: z.coerce.number().min(0).optional().describe("Stroke weight >= 0)"),
      },
      async ({ nodeId, r, g, b, a, strokeWeight }) => {
        try {
    
          if (r === undefined || g === undefined || b === undefined) {
            throw new Error("RGB components (r, g, b) are required and cannot be undefined");
          }
    
          const colorInput: Color = { r, g, b, a };
          const colorWithDefaults = applyColorDefaults(colorInput);
    
          const strokeWeightWithDefault = applyDefault(strokeWeight, FIGMA_DEFAULTS.stroke.weight);
    
          const result = await sendCommandToFigma("set_stroke_color", {
            nodeId,
            color: colorWithDefaults,
            strokeWeight: strokeWeightWithDefault,
          });
          const typedResult = result as { name: string };
          return {
            content: [
              {
                type: "text",
                text: `Set stroke color of node "${typedResult.name}" to RGBA(${r}, ${g}, ${b}, ${colorWithDefaults.a}) with weight ${strokeWeightWithDefault}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting stroke color: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
          };
        }
      }
    );
  • Input schema definition for the 'set_stroke_color' tool using Zod. Defines required parameters: nodeId (string), r, g, b (numbers 0-1), and optional: a (alpha 0-1), strokeWeight (>=0).
    {
      nodeId: z.string().describe("The ID of the node to modify"),
      r: z.coerce.number().min(0).max(1).describe("Red component (0-1)"),
      g: z.coerce.number().min(0).max(1).describe("Green component (0-1)"),
      b: z.coerce.number().min(0).max(1).describe("Blue component (0-1)"),
      a: z.coerce.number().min(0).max(1).optional().describe("Alpha component (0-1)"),
      strokeWeight: z.coerce.number().min(0).optional().describe("Stroke weight >= 0)"),
    },
  • Registration of the tool via server.tool('set_stroke_color', ...) as part of the registerModificationTools function. This registers the tool name, description, schema, and handler on the MCP server.
    server.tool(
      "set_stroke_color",
      "Set the stroke color of a node in Figma (defaults: opacity 1, weight 1)",
      {
        nodeId: z.string().describe("The ID of the node to modify"),
        r: z.coerce.number().min(0).max(1).describe("Red component (0-1)"),
        g: z.coerce.number().min(0).max(1).describe("Green component (0-1)"),
        b: z.coerce.number().min(0).max(1).describe("Blue component (0-1)"),
        a: z.coerce.number().min(0).max(1).optional().describe("Alpha component (0-1)"),
        strokeWeight: z.coerce.number().min(0).optional().describe("Stroke weight >= 0)"),
      },
      async ({ nodeId, r, g, b, a, strokeWeight }) => {
        try {
    
          if (r === undefined || g === undefined || b === undefined) {
            throw new Error("RGB components (r, g, b) are required and cannot be undefined");
          }
    
          const colorInput: Color = { r, g, b, a };
          const colorWithDefaults = applyColorDefaults(colorInput);
    
          const strokeWeightWithDefault = applyDefault(strokeWeight, FIGMA_DEFAULTS.stroke.weight);
    
          const result = await sendCommandToFigma("set_stroke_color", {
            nodeId,
            color: colorWithDefaults,
            strokeWeight: strokeWeightWithDefault,
          });
          const typedResult = result as { name: string };
          return {
            content: [
              {
                type: "text",
                text: `Set stroke color of node "${typedResult.name}" to RGBA(${r}, ${g}, ${b}, ${colorWithDefaults.a}) with weight ${strokeWeightWithDefault}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting stroke color: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
          };
        }
      }
    );
  • Helper utilities used by the stroke color tool: FIGMA_DEFAULTS (opacity=1, stroke weight=1), applyDefault (provides fallback value), and applyColorDefaults (fills in missing alpha with default opacity).
    import { Color, ColorWithDefaults } from '../types/color';
    
    export const FIGMA_DEFAULTS = {
      color: {
        opacity: 1,
      },
      stroke: {
        weight: 1,
      }
    } as const;
    
    export function applyDefault<T>(value: T | undefined, defaultValue: T): T {
      return value !== undefined ? value : defaultValue;
    }
    
    export function applyColorDefaults(color: Color): ColorWithDefaults {
      return {
        r: color.r,
        g: color.g,
        b: color.b,
        a: applyDefault(color.a, FIGMA_DEFAULTS.color.opacity)
      };
    }
  • Type definition for FigmaCommand, which includes 'set_stroke_color' as a valid command type for the Figma plugin WebSocket communication.
    export type FigmaCommand =
      | "get_document_info"
      | "get_selection"
      | "get_node_info"
      | "create_rectangle"
      | "create_frame"
      | "create_text"
      | "create_ellipse"
      | "create_polygon"
      | "create_star"
      | "create_vector"
      | "create_line"
      | "set_fill_color"
      | "set_stroke_color"
      | "move_node"
Behavior2/5

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

No annotations provided, so the description must disclose behavior. It mentions defaults but does not describe whether changes are additive, whether the node must have stroke enabled, error handling, or permanence. Critical behavioral details are missing.

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?

A single concise sentence with no redundancy or extraneous information. Every word earns its place.

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

Completeness3/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 output schema and no annotations, the description covers the basic purpose but omits error scenarios, return values, and prerequisites. It is minimally adequate but not fully complete.

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 coverage is 100%, so the description adds value by mentioning defaults for opacity and weight. This helps the agent understand what happens if optional parameters are omitted, but doesn't add beyond what the schema already conveys.

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 verb 'set' and the resource 'stroke color of a node in Figma', with defaults for opacity and weight. It distinguishes from sibling tools like set_fill_color by specifying stroke.

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 explicit guidance on when to use this tool versus alternatives like set_fill_color or set_stroke_weight. The description implies it's for setting stroke color with defaults but doesn't mention when not to use or prerequisites.

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