Lucid App集成的模型上下文协议(MCP)服务器. 将Lucid图导出为图像,这样一个可视化客户端就可以对其进行解释,并从Lucid Standard Impire JSON中创建出新的图.

□ 目录

• 特征
• 如何运作
• 客户和模型兼容性
• 先决条件
• 安装
• 使用费
• 贡献
• 参考资料
• 执照

□ 特性

• 文件发现和从LucidChart、LucidSpark和Lucid比例检索元数据
• ** 用于快速文档结构概览的轻型分页元数据**
• ** PNG 图像导出** 从 Lucid 图表中返回,作为图像内容块,供具有视觉能力的客户端解释
• ** 数字创建**来自Lucid标准导入 JSON(流程图、正图、UML、BPMN、云架构),并附有辅助布局
• ** 删除文件**(移至垃圾桶)
• ** TypeScript 执行**,全测试覆盖
• ** MCP检查员整合** 方便测试

如何运作

服务器是连接Lucid REST API的一通瘦桥. 它不** 运行任何LLM自己的:

• [[T0] [T1] 从 Lucid API 返回 JSON 元数据.

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-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 .lucid archive and creates a new document via the Lucid API.
• delete-diagram moves 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.