Figma Context Cache MCP
An MCP server that provides cached, refreshable, and structured Figma context for AI coding assistants, reducing API calls and latency by storing node responses locally.
README
🎨 Figma Context Cache MCP
🇧🇷 Leia em português: README.pt-BR.md
Persistent design context for AI coding agents.
Build once. Cache locally. Reuse everywhere.
An MCP (Model Context Protocol) server that provides cached, refreshable and structured Figma context for AI coding assistants such as Codex, Claude Code, and other MCP-compatible clients.
Instead of querying the Figma API on every request, this server stores node responses locally and exposes tools to retrieve, inspect, synchronize and manage cached design context.
Why?
AI coding assistants frequently need information from Figma while implementing or maintaining frontend applications.
Without a cache layer, every request:
- calls the Figma API
- consumes rate limits
- increases latency
- downloads the same information repeatedly
This project introduces a persistent cache with explicit synchronization capabilities, making Figma context:
- ⚡ Faster
- ♻️ Reusable
- 📦 Persistent
- 🤖 AI-friendly
Architecture
AI Agent
(Codex / Claude Code)
│
▼
MCP Server
│
┌───────────┴───────────┐
│ │
▼ ▼
Local JSON Cache Figma REST API
│
▼
Persistent Design Context
Features
- ✅ Persistent local cache
- ✅ Configurable cache TTL
- ✅ Explicit cache synchronization
- ✅ Cache inspection
- ✅ Selective cache clearing
- ✅ Strongly typed
- ✅ Automated tests with Vitest
- ✅ MCP compatible
MCP Tools
| Tool | Description |
|---|---|
health_check |
Verifies that the MCP server is running |
get_figma_node |
Retrieves a node from cache or directly from Figma |
sync_figma_node |
Forces a fresh request to Figma and updates the cache |
list_cached_figma_nodes |
Lists cached nodes and their current status |
clear_figma_cache |
Removes cache entries selectively |
Cache Lifecycle
get_figma_node
│
▼
Cache Hit?
│
├── Yes ───────────────► Return cached node
│
└── No
│
▼
Query Figma API
│
▼
Store locally
│
▼
Return response
sync_figma_node
│
▼
Always query Figma
│
▼
Update cache
│
▼
Return fresh response
Example
Synchronize a node:
Use sync_figma_node with:
fileKey: wdva3WcsFmz54Sg5e6OWJl
nodeId: 4510-5941
depth: 1
Example response:
{
"message": "Node synchronized successfully.",
"metadata": {
"source": "figma",
"cacheUpdated": true
}
}
Subsequent requests:
Use get_figma_node...
Response:
{
"metadata": {
"source": "cache"
}
}
Project Structure
src/
├── cache/
├── figma/
├── server/
├── tools/
└── sync/
tests/
├── cache/
└── figma/
Testing
This project uses Vitest.
Current test coverage:
| Component | Coverage |
|---|---|
| CacheService | 90%+ |
| FigmaContextService | 100% |
| FigmaClient | In progress |
Run the test suite:
npm test
Generate coverage:
npm run test:coverage
Installation
git clone https://github.com/AysllaGomes/figma-context-cache-mcp.git
cd figma-context-cache-mcp
npm install
Configure your environment:
FIGMA_API_KEY=your-token
CACHE_TTL_SECONDS=3600
STORAGE_PATH=./storage
Start the server:
npm run dev
Roadmap
- [x] Persistent cache
- [x] Cache inspection
- [x] Cache synchronization
- [x] Automated unit tests
- [ ] Structured node metadata
- [ ] Component relationship graph
- [ ] Storybook integration
- [ ] Angular component mapping
- [ ] Design token indexing
- [ ] Semantic search
Vision
This project started as a cache for the Figma API.
Its long-term goal is to evolve into a Frontend Context Engine, capable of providing AI coding agents with rich, structured knowledge about design systems, frontend components and software architecture.
Instead of simply retrieving JSON from Figma, the server aims to understand relationships between components, design tokens, Storybook stories and frontend implementations, enabling AI agents to make better architectural and implementation decisions.
License
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。