Technical Preview (V1 Preview): local-first MCP server for managing, rendering, and checking PlantUML and Mermaid architecture diagrams alongside your codebase.
Strong naming conventions (verb_noun pattern across all 12 tools). All tools have descriptions (avg 85 chars, within 10-1024 range). Input schemas present with type definitions and parameter descriptions. Good error handling with sanitization and domain-specific error classes. Pagination support on list tools. However, output schemas are not explicitly documented in source, and some parameter descriptions lack constraint details (ranges, formats). Tool composition is clean, each tool has single responsibility. Risk annotations present but not formalized as toolAnnotations in MCP protocol.
Check consistency between diagram entities and codebase identifiers
Create a new diagram file with validation
Delete a diagram file
Show differences between two diagram versions
Export a diagram as an HTML bundle with embedded rendering
Generate a PlantUML or Mermaid diagram from codebase entities and relationships
Generate a sequence diagram from codebase function/method calls
Read a diagram file with optional window/range selection
Output schemas not documented in source code. LLMs cannot infer what fields each tool returns, forcing them to guess downstream field names and risk broken tool chains.
Parameter constraints lack explicit ranges and formats. E.g., 'limit' and 'offset' in diagrams_list state defaults but not validation rules; 'max_entities' and 'max_relations' in diagrams_generate state ranges (1-60) but not in parameter descriptions.
Tool descriptions do not explicitly state when tools modify state. E.g., diagrams_create, diagrams_update, diagrams_delete lack clear 'This creates/modifies/deletes a file' language, making it ambiguous to LLMs which calls are idempotent and which have side effects.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2025-06-18+ | v2 |
List diagrams in the diagrams directory with pagination support
Render a diagram to SVG or PNG format
Generate a starter diagram template with specified entities and relationships
Update an existing diagram file with validation
Error handling is robust internally (toolError.ts sanitizes paths, classifies errors) but error messages returned to LLM lack recovery guidance. E.g., 'DiagramNotFoundError' is caught but the response does not suggest 'Try diagrams_list() to see available diagrams.'
Tool annotations (readOnlyHint, destructiveHint, idempotentHint) are not declared in MCP protocol registration. Risk field in metadata is informational only; LLMs cannot parse it from tool definitions.