smartzan63/lucid-mcp-server
Developer tools이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
Model Context Protocol (MCP) server for Lucid App integration. Exports Lucid diagrams as images so a vision-capable client can interpret them, and creates new diagrams from Lucid Standard Import JSON.
개요
Model Context Protocol (MCP) server for Lucid App integration. Exports Lucid diagrams as images so a vision-capable client can interpret them, and creates new diagrams from Lucid Standard Import JSON. - 🔍 and metadata retrieval from LucidChart, LucidSpark, and LucidScale - 📑 for quick document structure overview - 🖼️ from Lucid diagrams, returned as an image content block for a vision-capable client to interpret - ✏️ from Lucid Standard Import JSON (flowcharts, org charts, UML, BPMN, cloud architecture), with assisted layout - 🗑️ (move to trash) - 📝 with full test coverage - 🔧 for easy testing The server is a thin bridge to the Lucid REST API. It does run any LLM of its own: - search-documents and get-document-tabs return JSON metadata from the Lucid API. - get-document with analyzeImage: true exports the requested page as a PNG and returns it as an MCP image content block. - create-diagram packages the Lucid Standard Import JSON you provide into a .
README
원문 README의 일부입니다. 원문 보기.
Lucid MCP Server
Model Context Protocol (MCP) server for Lucid App integration. Exports Lucid diagrams as images so a vision-capable client can interpret them, and creates new diagrams from Lucid Standard Import JSON.
Table of Contents
- Features
- How It Works
- Client and Model Compatibility
- Prerequisites
- Installation
- Usage
- Contributing
- References
- License
Features
- 🔍 Document discovery and metadata retrieval from LucidChart, LucidSpark, and LucidScale
- 📑 Lightweight tab metadata for quick document structure overview
- 🖼️ PNG image export from Lucid diagrams, returned as an image content block for a vision-capable client to interpret
- ✏️ Diagram creation from Lucid Standard Import JSON (flowcharts, org charts, UML, BPMN, cloud architecture), with assisted layout
- 🗑️ Document deletion (move to trash)
- 📝 TypeScript implementation with full test coverage
- 🔧 MCP Inspector integration for easy testing
How It Works
The server is a thin bridge to the Lucid REST API. It does not run any LLM of its own:
search-documentsandget-document-tabsreturn JSON metadata from the Lucid API.get-documentwithanalyzeImage: trueexports the requested page as a PNG and returns it as an MCPimagecontent block.create-diagrampackages the Lucid Standard Import JSON you provide into a.lucidarchive and creates a new document via the Lucid API.delete-diagrammoves a document to the trash.
Diagram interpretation is delegated entirely to the model already driving your MCP client. This keeps the server free of any AI-provider dependency and reuses the (typically more capable) model running your session instead of a second, separately configured one. Likewise, the Standard Import JSON for create-diagram is authored by your session model, so the server needs no diagram-generation logic of its own.
Creating and deleting documents require a Lucid API key with document edit (write) scope. A read-only key can still search, read, and export. There is no in-place content editing in the Lucid REST API: to change a diagram, create a new one (optionally deleting the old). The exported JSON format and the Standard Import format are not interchangeable, so there is no download-edit-reupload round trip.
설치
npx -y lucid-mcp-server설정
{
"mcpServers": {
"lucid": {
"command": "npx",
"args": ["-y", "lucid-mcp-server"],
"env": {
"LUCID_API_KEY": "your-lucid-api-key"
}
}
}
}