Figwright vs Filesystem

A side-by-side look at the Figwright and Filesystem MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Figwright logoFigwrightArchitecture & Design · Local subprocess (stdio)Bidirectional Figma server over a local WebSocket relay: turn a selection into framework-aware code (reusing your components and tokens), or author frames, text, styles, variables, and whole screens back onto the canvas. 92 tools, any MCP client, no Dev Mode seat or paid tier.69GreatAuth: no auth requiredFilesystem logoFilesystemFile Systems · Local subprocess (stdio)Secure file operations with configurable access controls.85ExcellentAuth: no auth required

Verdict: choose Figwright for architecture & design work as a local process; choose Filesystem for file systems as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Figwright logoChoose Figwright when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like Read, Write, Grounding.
Explore Figwright

Filesystem logoChoose Filesystem when

  • You need dedicated capabilities in the File Systems domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like path, head, tail.
Explore Filesystem

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFigwright logoFigwrightFilesystem logoFilesystem
CategoryArchitecture & DesignFile Systems
Quality signal69/100 · Great85/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars1,15591,512
Directory activity 6 views 0 installs 0 upvotes 11 views 0 installs 0 upvotes
Tools317

Tools & capabilities

Figwright tools 3

  • Readselection, document and node inspection, styles, variables, components, fonts, prototype reactions and flows, motion (animation) state, screenshots, original image-fill assets, PDF export, and video export of animated frames (MP4 / GIF / WebM); plus `list_files` / `use_file` for working across more…
  • Writecreate and edit frames, text, shapes (lines, polygons, stars, boolean operations, flattening), auto-layout, alignment and distribution, effects, images (as a new layer or into an existing layer's fill), styles, variables (including importing a team library's variables and styles, and switching a fr…
  • Grounding`get_design_context` for faithful, de-duplicated design context, and `component_map` / `token_map` / `icon_map`, which join Figma data to your codebase so codegen reuses what you already have; plus `design_diff`, which reports what changed in a design against a saved baseline so you update only the…

Filesystem tools 17

  • path
  • head
  • tail
  • paths
  • content
  • edits
  • oldText
  • newText
  • dryRun
  • sortBy
  • source
  • destination
  • +5 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Figwright

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "awdr74100-figwright": {
      "command": "npx",
      "args": [
        "-y",
        "@figwright/mcp@latest"
      ]
    }
  }
}

Filesystem

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem"
      ]
    }
  }
}

Frequently asked questions

Figwright is categorized under Architecture & Design and uses a local stdio subprocess. Filesystem belongs to File Systems and uses a local stdio subprocess. Pick Figwright for architecture & design work and Filesystem for file systems.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Figwright is listed as free. Auth: no auth required. Filesystem is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add awdr74100-figwright and filesystem as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Figwright has a quality signal of 69/100 (Great) with 6 views, 0 installs and 1,155 GitHub stars. Filesystem has 85/100 (Excellent) with 11 views, 0 installs and 91,512 GitHub stars.