Schema | figma-meta-mcp

figma-meta-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`FIGMA_MCP_HOST`	No	Bridge bind host (:: = dual-stack so Windows localhost works)	::
`FIGMA_MCP_PORT`	No	Bridge listen port	3851
`FIGMA_MCP_EXEC_TIMEOUT_MS`	No	Per-job timeout	30000

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
figma_healthA	Check whether the local Figma bridge is up and whether the Development plugin is connected.
figma_execA	Execute JavaScript inside the running Figma plugin main thread (like ae_exec / cocosmcp_exec / Blender execute_blender_code). The code runs with access to the global `figma` Plugin API. Write an async body; the final expression / return value is JSON-serialized back. Prefer plain data (id/name/type/x/y/width/height). Avoid returning live node proxies. Example: return figma.currentPage.selection.map(n => ({ id: n.id, name: n.name, type: n.type }));
figma_selection_infoA	Summarize the current page and selection (id/name/type/bounds).

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shinjiyu/figma_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server