Skip to main content
Glama
Sanil-Gokarn

figma-flow

by Sanil-Gokarn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoThe port the WebSocket bridge listens on. Defaults to 3055; if changed, the port must also be updated in plugin/ui.html (SERVER_URL) and plugin/manifest.json (devAllowedDomains).3055

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
pingA

Check that the figma-flow MCP server is running. Returns 'pong'.

get_statusA

Report whether the figma-flow Figma plugin is connected to this server.

create_flowchartA

Draw a flowchart in the open Figma file.

Send only the structure: nodes (id, label, type) and edges (from, to, optional label). Never send coordinates or sizes. The server lays the chart out top to bottom, and the plugin sizes each shape to fit its label.

How to model a flow:

  • Begin with one "start" node. End every path at an "end" node.

  • Use "process" for actions and "input_output" for data going in or out, such as user input, a message shown to the user, or reading a file.

  • Every yes/no question or branch point is a "decision" node. Phrase its label as a question ("Password valid?") and give each outgoing edge a label ("Yes", "No").

  • Loops are fine: point an edge back to an earlier node.

Each call adds a new frame, named after the title, to the right of earlier charts. The figma-flow plugin must be running in Figma (check with get_status).

clear_canvasA

Remove every flowchart and shape the figma-flow plugin drew on the current Figma page. Everything else on the page is left alone.

draw_demo_flowchartA

Draw a sample login flowchart in the open Figma file. Useful to check the setup works end to end.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation4/5

create_flowchart, draw_demo_flowchart, and clear_canvas are clearly distinct in purpose. The main overlap is between ping and get_status, which both serve as health/connectivity checks, though get_status specifically reports plugin connection state.

Naming Consistency4/5

All names use snake_case consistently, which is good. However, the convention is not fully uniform: 'ping' is a bare verb, 'get_status' uses verb_noun, and the drawing tools mix 'draw_' and 'create_' as prefixes for similar operations.

Tool Count5/5

Five tools is well-scoped for a lightweight Figma flowchart plugin: health checks, connection status, chart creation, demo creation, and canvas clearing. Each tool has a clear role and none feels redundant.

Completeness3/5

The surface covers creating and clearing flowcharts, plus setup checks, but lacks operations to list, update, or delete individual existing flowcharts. The only removal tool clears the entire canvas, which is a notable gap for repeated editing workflows.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources