figjam-context-mcp
Exposes tools to ingest FigJam boards, retrieve context summaries, and answer free-form questions about the board content.
README
figjam-context-mcp
MCP server that turns a FigJam board into queryable context for LLMs — read directly via the Figma REST API, no manual PDF-export detour. It exposes four tools:
- ingest_board — reads a FigJam/Figma file, clusters its content
spatially, verifies and labels each cluster with a vision model, and
caches the result under a
boardId(= the Figma file key). - get_board_context — returns a compact, paste-ready context block plus the underlying clusters for an ingested board, optionally scoped to a topic.
- answer_from_board — answers a free-form question about an ingested board, citing the clusters the answer was derived from.
- diagnose_llm_config — runs small text + vision JSON checks against the active model setup and reports actionable failures.
How it works
FigJam boards are spatially chaotic: rotated stickies, overlapping shapes, embedded screenshots, no reading order. The pipeline therefore combines geometry with vision:
fetchFileTree+flattenNodeTree— pull the raw node tree and flatten it into normalized nodes (position, size, rotation, text, image refs), dropping empty structural noise.geometricPreCluster— rotation-aware distance clustering into coarse groups.refineClusterWithVision— per cluster, node screenshots + extracted text go to a vision model in one request; it confirms which nodes belong together, labels the group, describes embedded images, and writes a 3–5 sentence summary.mapToDoubleDiamond(optional,docStructureHint: "double_diamond") — assigns each cluster to Discover / Define / Develop / Deliver (or "unclear").- Results are cached in-memory per file key;
get_board_contextandanswer_from_boardread from the cache.
Setup
npm install
cp .env.example .env
Fill in .env:
FIGMA_ACCESS_TOKEN — log in at figma.com, go
to Settings → Security → Personal access tokens, generate a token. (Can
also be passed per-call via the figmaAccessToken input on ingest_board.)
LLM_BASE_URL / LLM_API_KEY / LLM_MODEL_PRESET — any
OpenAI-compatible endpoint. Free options:
- OpenRouter (default in
.env.example): get a key at openrouter.ai/keys. The defaultstudent-freepreset uses explicit free models for each role:google/gemma-4-26b-a4b-it:freefor vision andqwen/qwen3-next-80b-a3b-instruct:freeplusnvidia/nemotron-nano-9b-v2:freefor text/Q&A.openrouter/freeremains a last-resort fallback, not the primary model. - GitHub Models: free with any GitHub account — create a token at
github.com/marketplace/models,
set
LLM_BASE_URL=https://models.github.ai/inference.
Optional overrides:
LLM_VISION_MODELS— comma-separated vision model candidates.LLM_TEXT_MODELS— comma-separated text/Q&A candidates.LLM_FAST_TEXT_MODELS— comma-separated small/fast text candidates.- Legacy
LLM_VISION_MODEL/LLM_TEXT_MODELstill work as first-candidate overrides.
Run
npm run dev
This starts the MCP server over stdio using tsx watch. To try the tools
interactively:
npx @modelcontextprotocol/inspector npx tsx src/index.ts
Note: don't pass plain
npm run devto the Inspector (or any MCP client) — npm prints a> figjam-context-mcp@0.1.0 devbanner to stdout before the server starts, which corrupts the JSON-RPC stream the client expects there. Either invoketsxdirectly as above, or add--silent:npx @modelcontextprotocol/inspector npm run dev --silent.
MCP UI timeouts
ingest_board can be slow because it calls Figma and a vision LLM for board
clusters. If the MCP UI shows MCP error -32001: Request timed out, the client
gave up before those external calls finished.
The server now keeps provider calls bounded by default:
FIGMA_REQUEST_TIMEOUT_MS=15000LLM_REQUEST_TIMEOUT_MS=20000LLM_RATE_LIMIT_RETRIES=1LLM_ANSWER_MAX_OUTPUT_TOKENS=800INGEST_BOARD_VISION_BUDGET_MS=35000FIGMA_SCREENSHOT_DOWNLOAD_CONCURRENCY=3
ingest_board defaults to ingestMode: "balanced": text-rich clusters use
deterministic summaries, while image-heavy or low-text clusters use vision
within the budget. max_speed skips vision; max_quality attempts vision for
every cluster. Finished ingests are persisted under .cache/figjam-mcp/, keyed
by file state, node hash, model preset, document hint, and ingest mode.
Run diagnose_llm_config after changing model env vars. It checks text JSON,
vision JSON, and fallback setup without ingesting a board.
Usage example
Paste in a Figma board link and ingest it:
// tool: ingest_board
{
"figmaFileUrl": "https://www.figma.com/board/AbC123XyZ456/Semester-Project-Research",
"docStructureHint": "double_diamond"
}
// → { "boardId": "AbC123XyZ456", "clusterCount": 5,
// "summary": "Ingested board AbC123XyZ456: 5 clusters — \"User interview quotes\", \"Problem framing\", …" }
The boardId is the file key itself — re-running ingest_board on the same
file refreshes the cache entry. Then pull context, optionally scoped to a
topic:
// tool: get_board_context
{ "boardId": "AbC123XyZ456", "topic": "user research" }
// → contextText:
// FigJam board AbC123XyZ456 — 2 of 5 clusters (topic: user research):
//
// ## User interview quotes [discover]
// Sticky notes with verbatim quotes from six student interviews about exam
// stress. Two embedded screenshots show survey results (bar charts of study
// habits). Main pain points: unclear requirements and late feedback. …
The contextText block is deliberately token-lean — paste it straight into
a documentation-writing chat (e.g. for a semester report). Or ask directly:
// tool: answer_from_board
{ "boardId": "AbC123XyZ456", "question": "What were the main user pain points?" }
// → { "answer": "Unclear requirements and late feedback …",
// "citedClusters": ["User interview quotes", "Problem framing"] }
Scripts
npm run dev— run the server withtsx watch(auto-restart on change).npm run build— compile TypeScript todist/.npm start— run the compiled server fromdist/.npm test— run the Vitest test suite.
Project layout
src/
├── index.ts # stdio entrypoint
├── server.ts # McpServer setup + tool registration
├── tools/ # tool handlers (ingest pipeline, context, Q&A)
├── schemas/ # Zod input/output schemas per tool
├── lib/ # Figma API, node tree, clustering, vision, LLM, cache
└── types.ts # shared domain types
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。