Integrate excalidraw-mcp as a first-class diagramming feature
維護者通常 1 天內回覆
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 48/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 停滯
- 技術堆疊
- typescript
- 領域
- api, documentation, frontend
研究方向
Start with apps/app/src/app/api/copilotkit/route.ts:24-29 and inspect use-example-suggestions.tsx, then review the README. Done means the MCP server uses the descriptive ID, diagramming suggestions are visible, and the README explains the Excalidraw integration and its capabilities; local development support is optional.
由索引模型根據 Issue 內容生成。
描述
Summary
Deepen the integration with excalidraw-mcp beyond the current minimal config (a single remote URL in route.ts). The goal is to make diagram generation a showcase feature of this template — on par with the todo list — so developers see how MCP Apps work with CopilotKit's agent state pattern.
Current State
The runtime already points to https://mcp.excalidraw.com as a default MCP server (apps/app/src/app/api/copilotkit/route.ts:24-29), but:
- There's no UI affordance showing users they can ask the agent to draw diagrams
- No example prompts or suggestions mention diagramming
- The
serverIdis a generic"example_mcp_app"rather than something descriptive - No documentation on what the Excalidraw MCP integration enables
Proposed Changes
- Rename the MCP server ID from
"example_mcp_app"to"excalidraw"for clarity - Add diagramming-related chat suggestions in
use-example-suggestions.tsx(e.g. "Draw an architecture diagram of this app", "Sketch out a flowchart for the todo lifecycle") - Add a section to the README explaining the Excalidraw MCP integration and what users can do with it
- Optional: local dev support — add instructions or a script for running excalidraw-mcp locally via
npxor Docker, so the demo works offline / without the hosted endpoint
Why
This repo is a template for developers evaluating CopilotKit. Showing MCP Apps integration with a compelling visual tool like Excalidraw makes the demo significantly more impressive and helps developers understand the MCP Apps pattern.
References
- excalidraw-mcp repo: https://github.com/excalidraw/excalidraw-mcp
- Hosted endpoint:
https://mcp.excalidraw.com
- 主要語言
- TypeScript
- 星號
- 4.1k
- 分支
- 427
- 平均合併
- 4 小時
- 30 天內合併 PR
- 6
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
CopilotKit/OpenIntelligentUI 的其他 Issue
-
Script dedup key truncation may cause collisions可能已有人在做 @saschabuehrle 於 223 天前認領。 未關閉bug
難度 2/5 1-3 小時 新手友好度 72/100
CopilotKit/OpenIntelligentUI#37 ·
維護者通常 1 天內回覆
-
enhancement
難度 2/5 1-3 小時 新手友好度 72/100
CopilotKit/OpenIntelligentUI#29 ·
維護者通常 1 天內回覆
-
Self-host with Docker Compose and optional server-held keys可能已有人在做 @kannan983 於 23 天前認領。 未關閉
難度 4/5 3-5 天 新手友好度 18/100
CopilotKit/OpenIntelligentUI#98 ·
維護者通常 1 天內回覆
-
Support OpenAI-compatible gateways (OpenRouter) via vendor/model names可能已有人在做 @kannan983 於 23 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 25/100
CopilotKit/OpenIntelligentUI#97 ·
維護者通常 1 天內回覆
-
UI未關閉
難度 5/5 一週以上 新手友好度 8/100
CopilotKit/OpenIntelligentUI#96 ·
維護者通常 1 天內回覆
查看 CopilotKit/OpenIntelligentUI 的全部 Issue
相似的 Issue
-
🐛 bug
難度 2/5 1-3 小時 新手友好度 68/100
LibreChat-AI/LibreChat#17733 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 70/100
TypeStrong/typedoc#3150 ·
-
accessibility bug good first issue
難度 2/5 1-3 小時 新手友好度 85/100
維護者通常 1 天內回覆
-
Normalize image-source MIME types before SVG dispatch可能已有人在做 @HarsH-1877 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 75/100
tscircuit/image-utils#58 · 1 則留言 ·
-
難度 1/5 1 小時以內 新手友好度 74/100
維護者通常 2 天內回覆