Figma Mcp Go

io.github.vkhanhquiPublished by GitHub account vkhanhquiv0.1.3Updated Oct 24, 2026

Figma MCP server with full read/write access via plugin — no API token, no rate limits. 73 tools.

The publisher's own server: Figma MCP Server

VerifiedSTDIODesktop onlyMedia & Design

Overview

AI-generated overview

A local Figma MCP server that gives an assistant full read and write access to Figma files through a plugin, without an API token or rate limits.

What you can do
Read and write Figma designs through a companion plugin, with no API token required and no rate limits reported. The server advertises 73 tools, but the input does not list them, so the exact operations are not documented here. It runs as a local process over stdio on the user's machine.
When to use it
Worth considering when an assistant needs to inspect or modify Figma designs directly and token-based Figma API access or rate limits are a problem. Because the tool list is not published, check the package's own documentation before relying on specific operations.
Requirements
Runs as a local process over stdio, installed from the npm package @vkhanhqui/figma-mcp-go, so Node.js is needed. It works through a Figma plugin, which must be set up on the Figma side. No environment variables, headers or authentication are declared.
Before you install
The server claims full write access to Figma files, so assistant actions can change or delete design content. It is desktop-only and not web-executable. No credentials are declared, but the plugin connection should be reviewed before granting access to shared or production design files.

Installation

In SourceWeft

  1. Open Figma Mcp Go in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Figma integrations