List every workspace this connection can act in. Returns each workspace's id, slug, name, your role, and which one is the default (the workspace used when a tool is called without space). Call this FIRST when the user mentions a workspace by name, or when you are not sure which workspace the work belongs in — then pass the id as space on the tool you actually want. A connection scoped to a single workspace returns just that one.

List diagrams in the configured Space (every folder, newest first by default). Use this BEFORE create_diagram to check whether a diagram with the target purpose already exists — if it does, prefer update_diagram over creating a duplicate. Filter with q (case-insensitive substring on title, description, or code) when looking for a named diagram (e.g. q: 'schema' or q: 'infra'). Sort with sort: 'updated' to find the most recently changed diagrams, or sort: 'relevance' when q is set so a title hit ranks above a description or code hit.

List every folder in the configured Space, ordered by name. Returns id and full path (e.g. 'Infra/AWS' for a nested folder). Use this BEFORE create_diagram or update_diagram when you want to place a diagram in a meaningful folder — agents should match by name (e.g. find a folder named 'Schemas' and pass its id as folderId). Folders are at most two levels deep. Creating folders is currently human-only.

Fetch one diagram by id. Returns its title, description (the agent's brief), mermaid source code, and its URL in the app — which only members of this Space can open. If the diagram already has a public link, that link is reported separately on a Share (public, read-only): line; a public link is minted by a person, from the diagram's Share button. Read the description before editing — it tells you what the diagram is for and when to update it.

Create a new diagram in the Space. Returns its id and its URL in the app, which only members of this Space can open — it is NOT a shareable link. To show the diagram to anyone outside the Space, someone in the Space opens it in DiagramZu and uses its Share button, which mints a public read-only link. See this server's instructions for diagram-type selection and class role names (edge/core/data/accent/muted) for color-grouping.

Update an existing diagram's title, description, mermaid source, visual style preset, and/or layout style options. When rewriting the source, keep or restore class assignments using the role names from this server's instructions so the diagram stays color-grouped. In a workspace with proposal review enabled, your change is recorded as a proposal pending human approval rather than applied to the live diagram — in that case tell the user you've proposed the change and share the review URL.

Analyze a stored flowchart diagram's structure (nodes, edges, subgraphs) and return actionable findings — orphan nodes, over-connected hubs, cycles, disconnected clusters, and grouping suggestions. Flowchart diagrams only. Set postAsComments: true to also persist each finding as a comment on the diagram (node-pinned where the finding names a single node) so a human reviewer sees them on the diagram surface.

List manual snapshots of a diagram, newest first. Returns id, label, title, createdAt, and createdBy for each.

Fetch one snapshot by id. Returns its title, mermaid source code, and metadata. Read-only — restore is human-only in the UI.

List comments on a diagram, oldest first. Returns id, parentId (null for a top-level comment), nodeId (the pinned node, if any), author, resolved state, and a body snippet. Use nodeId to fetch only the thread pinned to one node.

Post a comment on a diagram. Pass nodeId to pin it to a specific node, or parentId to reply to an existing top-level comment (threads are one level deep). The author is the API token's owner. Use this to leave structured review findings a human will see on the diagram.

List presentation decks in the configured Space, newest-edited first. A deck is an ordered set of existing diagrams shown as a slideshow. Returns each deck's id, title, and slide count.

Fetch one deck by id. Returns its title, description, and the ordered list of slides (each slide is a diagram id + title in presentation order).

Create a presentation deck from existing diagrams. Pass slides as the complete ordered list of diagram ids — the deck plays them as a slideshow in that order. Typical flow: create_diagram for each slide, collect the returned ids, then create_deck with those ids in presentation order. Returns the deck id and the present URL, which only members of this Space can open — it is NOT a shareable link. To share the deck outside the Space, someone in the Space opens it in DiagramZu and uses its Share button, which mints a public read-only presentation link. Diagram ids must already exist in this Space (use list_diagrams to find them).

Update a deck's title, description, and/or slide order. slides is DECLARATIVE: pass the complete desired ordered list of diagram ids — reorder, add, and remove are all expressed by sending the new full list (any id omitted is removed from the deck; new ids are appended in the order given). Returns the deck id and the present URL, which only members of this Space can open — it is NOT a shareable link. To share the deck outside the Space, someone in the Space opens it in DiagramZu and uses its Share button, which mints a public read-only link.

List the workspace's Markdown pages, most recently edited first. Returns each page's id, title, revision, last-edit time, who edited it, and a short snippet — never the full body; call get_page for that. Filter with q, a case-insensitive substring over title and body that works in Chinese and Japanese too, and pass sort: 'relevance' with it so a title hit ranks first. Call this BEFORE create_page to see whether a page on the topic already exists — prefer update_page over writing a second one.

Fetch one Markdown page by id. Returns its body, its revision — pass that as baseRevision when replacing the whole body — its language, who edited it last, and its URL in the app, which only members of this workspace can open. To let somebody outside the workspace read it, a person in the workspace opens the page in DiagramZu and uses its Share button, which mints a public read-only link. For a long document prefer outline: true (the heading tree, with an anchor per heading) and then section: '<heading text or anchor>' for just the part you need.

Create a Markdown page in the workspace — a design write-up, a decision record, a runbook, the prose a diagram cannot carry. The title comes from the body (front-matter title, else the first top-level # heading), so begin the body with a heading rather than passing title. Embed a stored diagram by putting its id inside a fenced diagramzu block; an inline mermaid block is for a throwaway sketch nobody will revisit. Returns the page's id, its revision and its URL in the app, which only members of this workspace can open. To let somebody outside the workspace read it, a person in the workspace opens the page in DiagramZu and uses its Share button, which mints a public read-only link.

Update a Markdown page. EXACTLY ONE body mode, and edits is the one to reach for: each edit replaces an oldText that must appear exactly once in the page, so a change to one paragraph never sends — or silently reverts — the rest of the document. If somebody else edits the page first, YOUR edits are re-applied on top of THEIR text, and the call is refused outright if they changed the very span you are editing. The other mode is baseRevision plus body, which replaces the whole document and needs the revision get_page reported. Changing only metadata (title, folderId, lang) needs neither. Returns the page's new revision and its URL in the app, which only members of this workspace can open. To let somebody outside the workspace read it, a person in the workspace opens the page in DiagramZu and uses its Share button, which mints a public read-only link.