Provides tools for interacting with the Figma REST API, including reading design files and nodes, rendering node images, listing image fills, styles, and components, browsing team projects and project files, and reading or posting file comments.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
designport is a compatible client for the Figma REST API, packaged
as an MCP server and a small CLI. It is an independent client for
the same public upstream API (https://api.figma.com/v1) — it is
not a copy of Figma's hosted OAuth remote MCP server, and none of
that server's OAuth tool surface (design context, screenshots,
metadata, variable definitions, code-connect, FigJam, or
design-system rules) is reproduced here.
The subset covers reading design files: fetch a file or specific nodes, render nodes to images, list image fills, styles, and components, browse team projects and project files, and read or post comments on a file.
Authentication is a Figma personal access token, sent as the
X-Figma-Token header. Set FIGMA_PERSONAL_ACCESS_TOKEN before
starting the server; a call made without it fails with an error
naming the variable. The API base can be overridden with
FIGMA_API_BASE.
npx @reneturcios/designport get_file <file_key>
docker run -i ghcr.io/cloudcorprecords/designportRelated MCP server: Figma MCP Proxy Server
designport get_file <file_key> --depth 2
designport get_file_nodes <file_key> 1:2,3:4
designport get_images <file_key> 1:2 --format png --scale 2
designport get_file_styles <file_key>
designport get_team_projects <team_id>
designport list_project_files <project_id>
designport post_comment <file_key> "Looks good"
designport --versionExit codes: 0 success, 1 API error, 2 usage error.
npx -y @reneturcios/designport mcp{
"mcpServers": {
"designport": {
"command": "npx",
"args": ["-y", "@reneturcios/designport", "mcp"],
"env": { "FIGMA_PERSONAL_ACCESS_TOKEN": "your-token" }
}
}
}Tool | Input | Figma endpoint |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
node_ids is a comma-separated string of node IDs, sent as the
API's ids parameter. post_comment's optional client_meta is
a string containing a JSON-encoded object — for example
'{"x":10,"y":20}' — which is parsed and sent as the API's
client_meta object; keeping it a string keeps the tool schema
simple.
Out of scope for this subset: the variables API, dev resources, library assets and search, webhooks, activity logs, and payments.
npm install
npm run build
npm testTests run entirely on fake-fetch fixtures; no network and no real token are used.
MIT — see LICENSE.
This server cannot be deployed
Access and maintain design system docs, tokens, components, skills, and contexts across any project.
Notes, kanban tasks, and a capture inbox: read and create Flow data with a personal token.
Read-only access to your bank, investment, and crypto accounts: balances, transactions, holdings.
Access the GitHub API, enabling file operations, repository management, search functionality, and…
