Figma Mcp Server

What is Figma Mcp Server?

The Figma Mcp Server is a WebSocket server that implements Figma’s Multi-Cursor Protocol (MCP) for managing real-time cursor presence across multiple users in collaborative applications. It is designed for developers building live cursors with metadata like color, name, or pointer style.

How to use Figma Mcp Server?

Install dependencies with bun install, then start the WebSocket server with bun socket. Ensure clients connect via ws:// or wss:// as appropriate.

Key features of Figma Mcp Server

• Implements Figma’s lightweight Multi-Cursor Protocol (MCP)
• Manages real-time cursor position broadcasting per user
• Supports optional metadata: username, color, avatar, etc.
• Uses rooms to scope user visibility (optional)
• Fast, simple, and extensible for collaborative environments

Use cases of Figma Mcp Server

• Add live cursors to a collaborative whiteboard or editor
• Show multiple users’ pointer positions in a design tool
• Broadcast cursor positions with custom metadata like name or color
• Scope visibility of cursors by logical room or session

FAQ from Figma Mcp Server

What is the Multi-Cursor Protocol (MCP)?

MCP is a lightweight protocol from Figma for real-time cursor presence. It defines how clients connect, broadcast cursor position, and disconnect, supporting metadata like color, name, or pointer style.

How do I install and run Figma Mcp Server?

Run bun install to install dependencies, then bun socket to start the WebSocket server. It requires Bun, a fast JavaScript runtime.

What are the key concepts of MCP?

Concepts include Session ID (unique client ID), Cursor Position (x, y coordinates), Metadata (optional info like username/color), and Rooms (optional groups to scope user visibility).

What dependencies or runtime does the server require?

The server runs on Bun (a JavaScript runtime). No other runtime dependencies are mentioned in the README.

How do clients connect and what transport is used?

Clients connect via WebSocket using ws:// or wss:// to the running server. The protocol handles real-time cursor broadcasting.