knitto-mcp-server-channel
Provides tools for interacting with Figma via a WebSocket relay and AI bridges (Cursor and OpenRouter), enabling AI agents to perform design actions and manage Figma files.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@knitto-mcp-server-channelconnect Figma plugin to Cursor bridge on channel knitto"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
knitto-mcp-server-channel
Aplikasi Node.js (TypeScript) untuk menjalankan stack @knittotextile/knitto-mcp-figma di server:
WebSocket relay (
knitto-mcp-figma-socket)AI bridge Cursor (
knitto-mcp-figma-bridge-cursor)AI bridge OpenRouter (
knitto-mcp-figma-bridge-openrouter)
Prasyarat
Docker & Docker Compose
GitHub Personal Access Token dengan scope
read:packages(GITHUB_TOKEN)
Variabel | Default | Fungsi |
|
| Host bind WebSocket |
|
| Port WebSocket di dalam container |
|
| Port yang di-publish ke host |
|
| Host socket untuk bridge (dalam container) |
| — | API key Cursor (opsional, bisa dari plugin) |
| — | API key OpenRouter (opsional, bisa dari plugin) |
|
| Working directory agent bridge |
|
| Job paralel per channel |
|
| Timeout per job (ms) |
|
| Model Cursor agent |
| — | Auth GitHub Packages saat Docker build |
Related MCP server: Talk to Figma MCP
Menjalankan (Docker)
Salin environment (wajib isi
GITHUB_TOKEN):
cp .env.example .envBuild & jalankan:
docker compose up -d --buildCek status:
docker compose ps
docker compose logs -f knitto-mcp-channel
curl http://localhost:${FIGMA_WS_PUBLISH_PORT:-3055}/Health check HTTP: GET http://<server-host>:<port>/ → Knitto Figma WebSocket server running
Mengganti port
Ubah di .env:
FIGMA_WS_PORT=4000Lalu restart:
docker compose up -dClient (plugin Figma / Cursor MCP) harus mengarah ke port yang sama, contoh FIGMA_WS_PORT=4000.
Jika port host berbeda dari port container:
FIGMA_WS_PORT=4000
FIGMA_WS_PUBLISH_PORT=8080Build manual tanpa Compose:
DOCKER_BUILDKIT=1 docker build \
--secret id=github_token,env=GITHUB_TOKEN \
-t knitto-mcp-server-channel:latest .
docker run -d \
--name knitto-mcp-channel \
-p "${FIGMA_WS_PORT:-3055}:${FIGMA_WS_PORT:-3055}" \
-e FIGMA_WS_PORT="${FIGMA_WS_PORT:-3055}" \
--env-file .env \
knitto-mcp-server-channel:latest
GITHUB_TOKENhanya dipakai saat build (via Docker secret) dan tidak dicetak di log build.
Stop container:
docker compose downTroubleshooting bridge
Setelah mengubah kode, wajib rebuild image:
docker compose up -d --buildCek bridge sudah terdaftar di log:
docker compose logs knitto-mcp-channel | grep "Bridge registered"Harus muncul:
Bridge registered: cursor-... (Cursor)
Bridge registered: openrouter-... (OpenRouter)Jika job Agent gagal:
Isi
CURSOR_API_KEY/OPENROUTER_API_KEYdi.env, atau simpan di plugin tab Agent → Bridge credentialsPlugin Connection harus connect ke host server yang sama (bukan
localhostdari mesin lain)Channel di plugin harus sama dengan yang dipakai saat submit job
Development lokal (opsional)
cp .npmrc.example .npmrc # isi GITHUB_TOKEN
pnpm install
pnpm rebuild sqlite3 # wajib untuk bridge-cursor (@cursor/sdk)
pnpm devKonfigurasi client
Plugin Figma
Install plugin dari
node_modules/@knittotextile/knitto-mcp-figma/dist/knitto-figma-mcp-plugin.zipTab Connection → isi Channel (contoh:
knitto)Isi WebSocket host = hostname/IP server ini
Klik Connect
Tab Agent → pilih bridge Cursor atau OpenRouter → Submit
API key bridge bisa diisi di .env atau disimpan lewat panel Bridge credentials di plugin.
Cursor IDE (mcp.json) — opsional
Jika tidak memakai tab Agent di plugin, MCP bisa dihubungkan langsung dari Cursor:
{
"mcpServers": {
"figma": {
"command": "npx",
"args": ["-y", "@knittotextile/knitto-mcp-figma@latest"],
"env": {
"CHANNEL_ID": "knitto",
"FIGMA_WS_SERVER": "your-server-host",
"FIGMA_WS_PORT": "3055"
}
}
}
}Catatan: Matikan MCP figma di Cursor saat memakai bridge dari plugin (atau gunakan channel terpisah) agar tidak bentrok.
Arsitektur
flowchart LR
PluginUI --> Socket
Socket --> BridgeCursor[Bridge Cursor]
Socket --> BridgeOR[Bridge OpenRouter]
BridgeCursor --> MCP["knitto-mcp-figma MCP"]
BridgeOR --> MCP
MCP --> Socket
CursorMCP[Cursor IDE MCP] --> SocketThis server cannot be deployed
Maintenance
Related MCP Connectors
Real-time chat hub for AI agents — Claude Code, Cursor, Cline, Codex over MCP or REST.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Real-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA server implementation that enables interaction with Figma API through Model Context Protocol (MCP), supporting plugin and widget development with WebSocket communication capabilities.1,225 npm3MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to interact with Figma designs for tasks like reading document info, creating elements, and managing auto layouts. It facilitates real-time design automation via a custom Figma plugin and WebSocket server integration.860 npmMIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI agents to programmatically create, modify, and manage Figma documents via a WebSocket bridge and Figma plugin.116MIT
- AlicenseAqualityDmaintenanceLocal-first MCP server that connects AI coding agents to the currently open Figma file through a local plugin bridge, requiring no Figma API token.8MIT