MCP server that lets Claude (Desktop) design pages directly in the KoralPaper app running in a browser. Provides a stdio MCP interface and a local HTTP bridge for tool execution.
KoralPaper MCP has well-structured schemas for most tools (draw, update, delete, list, etc.) with detailed parameter descriptions. However, several tools lack output schema documentation, and some descriptions are generic. The draw tool has excellent parameter detail (30+ fields documented), but tools like status, clear, and newPage have minimal descriptions (under 50 chars). Error handling guidance is absent, tools do not explain recovery paths or categorize failures. Naming is clear and verb-forward (draw, update, delete, list, newPage, setPage, renamePage, deletePage), following the verb_noun pattern well. Parameter descriptions are generally present but inconsistent in depth across tools.
Clear all elements from the active page.
Delete elements by id. Pass an array of element ids to remove from the active page.
Delete a page by id. Cannot delete the last page.
Draw elements (shapes, text, arrows, lines) on the active page. Pass an array of element objects with id, type, position, size, styling, and content. Types: rect, diamond, ellipse, polygon, chip, text, arrow, line. Stroke colors: ink, gdark, gmid, glight, white, coral, blue, green, plum, none, or any #hex. Fill colors: none, cream, white, coral, terracotta, blush, periwinkle, sage, butter, sky, glight, gmid, gdark, ink, or any #hex.
List all elements on the active page.
List all pages in the document with their ids and names.
Create a new page with a given name. Returns the new page id.
Output schemas not documented. Tools like list, listPages, status, and newPage do not specify what fields they return. LLMs cannot plan downstream tool calls or extract required IDs without knowing response structure.
Minimal descriptions on discovery and utility tools. clear (0 chars), list (0 chars), listPages (0 chars), status (0 chars) lack actionable descriptions. LLMs cannot determine when to call these tools instead of alternatives.
No error handling guidance. Tools do not explain what happens on failure (e.g., 'KoralPaper app not connected' for status, 'page not found' for setPage). Agents cannot self-correct or retry intelligently.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
Rename a page by id.
Switch to a page by id. The active page is where draw/update/delete/list/clear operate.
Check if the KoralPaper app is connected to the bridge.
Update existing elements by id. Pass an array of {id, ...patch} objects with the fields to change. Only specified fields are updated; omitted fields remain unchanged.
update tool schema incomplete. The 'updates' array items accept 'additionalProperties: true' but do not document which fields are patchable. LLMs must guess which element properties can be updated.
No confirmation or dry-run for destructive operations. delete, clear, and deletePage are irreversible but lack a confirmation step or dry-run mode. Agents can accidentally destroy work.