knitto-mcp-server-channel
A Node.js server that runs a WebSocket relay and AI bridges (Cursor and OpenRouter) to integrate Figma with MCP agents.
README
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 |
|---|---|---|
FIGMA_WS_HOST |
0.0.0.0 |
Host bind WebSocket |
FIGMA_WS_PORT |
3055 |
Port WebSocket di dalam container |
FIGMA_WS_PUBLISH_PORT |
FIGMA_WS_PORT |
Port yang di-publish ke host |
FIGMA_WS_SERVER |
localhost |
Host socket untuk bridge (dalam container) |
CURSOR_API_KEY |
— | API key Cursor (opsional, bisa dari plugin) |
OPENROUTER_API_KEY |
— | API key OpenRouter (opsional, bisa dari plugin) |
KNITTO_BRIDGE_CWD |
/app/bridge-workspace |
Working directory agent bridge |
KNITTO_BRIDGE_MAX_CONCURRENT |
1 |
Job paralel per channel |
KNITTO_BRIDGE_JOB_TIMEOUT_MS |
600000 |
Timeout per job (ms) |
KNITTO_BRIDGE_MODEL |
auto |
Model Cursor agent |
GITHUB_TOKEN |
— | Auth GitHub Packages saat Docker build |
Menjalankan (Docker)
- Salin environment (wajib isi
GITHUB_TOKEN):
cp .env.example .env
- Build & jalankan:
docker compose up -d --build
- Cek 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=4000
Lalu restart:
docker compose up -d
Client (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=8080
Build 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 down
Troubleshooting bridge
Setelah mengubah kode, wajib rebuild image:
docker compose up -d --build
Cek 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 credentials - Plugin 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 dev
Konfigurasi client
Plugin Figma
- Install plugin dari
node_modules/@knittotextile/knitto-mcp-figma/dist/knitto-figma-mcp-plugin.zip - Tab 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] --> Socket
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。