[Template] MCP Server

Created By
larryhudsona year ago
Overview

What is Figma MCP Server?

Figma MCP Server is a template for creating a server that utilizes the Model Context Protocol (MCP) to allow AI assistants to interact with external tools.

How to use Figma MCP Server?

To use this template, you need to add tool definitions in the src/index.ts file, update the README and package.json, build the server using npm run build, and publish it to npm.

Key features of Figma MCP Server?

  • Built with Model Context Protocol for AI interaction
  • TypeScript for enhanced developer experience
  • Easy setup with API key configuration

Use cases of Figma MCP Server?

  1. Creating custom AI tools that interact with Figma.
  2. Developing applications that require server-side processing with AI capabilities.
  3. Integrating with other MCP-compatible applications.

FAQ from Figma MCP Server?

  • What is the Model Context Protocol?

It is a framework that allows AI assistants to interact with external tools.

  • Is this template free to use?

Yes! The Figma MCP Server template is open-source and free to use.

  • What programming language is used?

The server is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
larryhudson
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
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.

8 hours ago