Figjam Context MCP Server
by ecestnrklio.github.ecestnrkl/figjam-mcpv0.5.0
Query FigJam board context, source-cited answers and snapshot changes through five local MCP tools.
context tax
pending
security
100/100
cold start
pending
freshness
Activetoday
Our reading of Figjam Context, from the data
Figjam Context is an MCP server from ecestnrkl, listed in the official MCP Registry.
We haven't measured its tool list yet, so its token cost is unknown.
Maintenance is active: the last public signal was in the last day (2026-10-18).
It runs locally on your machine over stdio and needs 2 secrets (FIGMA_ACCESS_TOKEN, LLM_API_KEY); use a scoped, least-privilege key.
Install Figjam Context MCP server
Install in Claude Code
claude mcp add figjam-context -e FIGMA_ACCESS_TOKEN='<figma-access-token>' -e LLM_API_KEY='<llm-api-key>' -- npx -y figjam-context-mcpInstall in Cursor
{
"mcpServers": {
"figjam-context": {
"command": "npx",
"args": [
"-y",
"figjam-context-mcp"
],
"env": {
"FIGMA_ACCESS_TOKEN": "<figma-access-token>",
"LLM_API_KEY": "<llm-api-key>"
}
}
}
}Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).
Install in Claude Desktop
{
"mcpServers": {
"figjam-context": {
"command": "npx",
"args": [
"-y",
"figjam-context-mcp"
],
"env": {
"FIGMA_ACCESS_TOKEN": "<figma-access-token>",
"LLM_API_KEY": "<llm-api-key>"
}
}
}
}Settings → Developer → Edit Config (claude_desktop_config.json), then restart.
Install in VS Code
{
"servers": {
"figjam-context": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"figjam-context-mcp"
],
"env": {
"FIGMA_ACCESS_TOKEN": "<figma-access-token>",
"LLM_API_KEY": "<llm-api-key>"
}
}
}
}Add to .vscode/mcp.json in your workspace.
Install in Windsurf
{
"mcpServers": {
"figjam-context": {
"command": "npx",
"args": [
"-y",
"figjam-context-mcp"
],
"env": {
"FIGMA_ACCESS_TOKEN": "<figma-access-token>",
"LLM_API_KEY": "<llm-api-key>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json.
Configuration
| Variable | Required | Secret | Description |
|---|---|---|---|
| FIGMA_ACCESS_TOKEN | — | yes | Figma token with file_content:read; file_metadata:read also enables cheap freshness checks. |
| LLM_API_KEY | — | yes | Key for the configured OpenAI-compatible provider; required for vision and answers. |
| LLM_BASE_URL | — | — | Explicit OpenAI-compatible provider base URL; .env.example uses OpenRouter. |
| FIGJAM_MCP_CACHE_DIR | — | — | Private local cache root; v4 snapshots are stored in a subdirectory. |
Security signals
100/100 — no known issues found as of 2026-10-19, from the checks below. This is not a guarantee of safety; review what a server can do before connecting it.
Deductions
No findings from the checks that ran.
Checks
- ✓Repository hygiene (archived, activity, license, security policy)
- ○Package metadata (install scripts, provenance) — pending
- ○Tool descriptions (prompt-injection and hidden-text heuristics) — pending
- ○Source scan (secrets, CVEs, risky code) by vectra-guard — pending
Scan it yourself before installing with vectra-guard, the open-source agent security CLI. Scoring rules
Freshness
Active — last maintenance signal today. The newest of the signals below sets the band.
Last commit (default branch)
2026-10-18 · today · GitHub
Latest release
2026-10-18 · today · GitHub · v0.5.0
Package published
no data · npm/PyPI
Registry entry updated
2026-10-18 · today · official registry · v0.5.0
FAQ
›How do I install the Figjam Context MCP server in Claude Code?
Run: claude mcp add figjam-context -e FIGMA_ACCESS_TOKEN='<figma-access-token>' -e LLM_API_KEY='<llm-api-key>' -- npx -y figjam-context-mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.
›Does Figjam Context require an API key?
Yes. It expects FIGMA_ACCESS_TOKEN, LLM_API_KEY, of which 2 are secrets.
›Can I use Figjam Context as a remote (hosted) MCP server?
No hosted endpoint is published; it runs locally over stdio.
›Is Figjam Context in the official MCP registry?
Yes, as io.github.ecestnrkl/figjam-mcp.
Sources and method
- Official MCP Registry entry
- updated 2026-10-18
- GitHub repository
- fetched 2026-10-19
- Package registry (npm / PyPI)
- listed
- Security signals, computed by us
- 2026-10-19
- Last checked against all sources
- 2026-10-19
The description, packages and links come from the maintainer's own published metadata. Token cost, security signals, freshness and the reading above are MCPSkillHub's own measurements; see the methodology. Spot an error? Request a correction or claim the listing.