Line9
Server Details
Render Mermaid with Line9 layout in your assistant.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
list_diagrams (discover), get_diagram (fetch a published diagram) and render_diagram (render arbitrary Mermaid source) have largely distinct targets and actions. The only soft boundary is that both get_diagram and render_diagram return a rendered diagram, so an agent must distinguish 'existing published diagram' from 'source I just wrote' — the descriptions make this clear, though not instantly.
All three tools follow a strict verb_noun, all-lowercase snake_case pattern: list_diagrams, get_diagram, render_diagram. The naming is fully predictable and readable.
Three tools is on the thin side but each covers a distinct step — discover, fetch, render — and the server's remit is deliberately narrow (viewing and rendering, no authoring). Nothing appears redundant or missing within that scope, though the surface is minimal enough that it borders on sparse.
For a read/render-only connector the lifecycle is covered: discovery, retrieval, and render-with-verdict validation. The absence of create/update/publish is an explicit, documented dead end handled via open_url, so agents can work around it, but there is no programmatic way to persist an edit.
Publisher details
- Operator
- Line9 · Publisher source
- Operator website
- https://line9.ai · Publisher source
- Vendor relationship
- First-party
- Documentation
- https://line9.ai/docs/mcp · Publisher source
- Privacy policy
- Not provided
- Trust center
- https://line9.ai/legal/privacy · Publisher source
- Restrictions
- No account or authorisation is needed to use the Line9 MCP connector. With an account, access to previously published diagrams is made available in your AI assistant UI.
Available Tools
3 toolsget_diagramGet a diagramARead-onlyIdempotentInspect
Fetch a published diagram's current Mermaid source by name or slug, and show it rendered. The returned source is stamped with the diagram's identity — keep the line9: frontmatter block when you edit it so that Line9 recognises the diagram when it is opened and published there instead of creating a new one. Requires Line9 sign-in. This connector cannot publish or save. To publish, the user opens the diagram in Line9 (the open_url link) and publishes there — not with the Line9 CLI.
Inputs: diagram (required). Returns: svg, path, plan, error, +25 more
list_diagramsList my diagramsARead-onlyIdempotentInspect
List the diagrams published in the user's Line9 workspace(s): name, visibility, version, last update and permalink. Use it to find a diagram before get_diagram. Requires Line9 sign-in.
Inputs: limit, query. Returns: svg, path, plan, error, +25 more
render_diagramRender diagramARead-onlyIdempotentInspect
Render Mermaid source with Line9's layout engine. Call this whenever you write or change Mermaid and the user should see the result. Flowcharts and sequence diagrams get Line9's layout; other Mermaid kinds are rendered with Mermaid's own layout and flagged as such. Returns a short verdict — kind, size, warnings, or a parse error with its line and column — plus an "Open in Line9" link. On a parse error, fix the named line and call again. Assistants that support MCP Apps show the diagram in a panel; there, do not paste the SVG or repeat the source in your reply. In an assistant with no panel (a terminal or editor), reply with the verdict line and the open_url link — that link is the only way the user sees the diagram. Write flowcharts as flowchart LR unless the user asks for top-to-bottom; chat panels are wide and short. No sign-in needed; renders carry a small Line9 mark unless the user is signed in to Line9 Pro. Set theme, orientation, spacing and legend in the source itself (line9: frontmatter; flowchart LR), never as arguments. This connector cannot publish or save. To publish, the user opens the diagram in Line9 (the open_url link) and publishes there — not with the Line9 CLI.
Inputs: source (required), plan. Returns: svg, path, plan, error, +25 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Generate dynamic Mermaid diagrams and charts with AI assistance. Customize styles and export diagr…
Draw architecture diagrams, UML, planning boards and clickable wireframes from your AI assistant.
Create and manage Mermaid.js flowcharts and diagrams with AI agents via MCP.
Make editable flowcharts, process charts, funnels, timelines and data models from plain language.
Related MCP Servers
- AlicenseAqualityCmaintenanceLets agents construct Mermaid diagrams from structured JSON IR and render them as PNG or SVG.3MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to generate and render Mermaid diagrams (flowcharts, sequence diagrams, etc.) as PNG/SVG images with local file saving and HTTP access URLs. Supports batch processing and intelligent caching for efficient diagram creation.168 npm1MIT
- AlicenseBqualityDmaintenance❤️ Generate mermaid diagram and chart with AI MCP dynamically.1902 npm649TypeScriptMIT
- AlicenseNot gradedqualityDmaintenanceRenders Mermaid diagrams in an interactive viewer with pan, zoom, and split-view source editing, enabling LLM hosts to create and edit diagrams through natural language and synchronize updates back to the conversation.63 npm1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.