Figma MCP Server

Created By
ihiteshsharmaa year ago
Overview

What is Figma MCP Server?

Figma MCP Server is a tool that connects Claude, an AI assistant, with Figma, enabling users to create and edit designs directly through natural language instructions.

How to use Figma MCP Server?

To use Figma MCP Server, install the Figma plugin, configure the server settings in Claude, and then interact with Claude to create or edit designs in Figma.

Key features of Figma MCP Server?

  • Create new designs by describing them to Claude.
  • Edit existing designs with simple instructions.
  • Generate wireframes and UI elements.
  • Export designs as images.

Use cases of Figma MCP Server?

  1. Designing user interfaces for web and mobile applications.
  2. Creating wireframes for project proposals.
  3. Rapid prototyping of design concepts.

FAQ from Figma MCP Server?

  • Can I use Figma MCP Server without Figma?

No, Figma MCP Server requires the Figma Desktop app to function.

  • Is there a cost associated with using Figma MCP Server?

Figma MCP Server is free to use, but you need a Figma account.

  • What should I do if Claude can't connect to Figma?

Ensure the Figma plugin is running and the configuration file is set up correctly.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ihiteshsharma
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago