Canvs

Server Details

AI-powered diagrams, mind maps, flowcharts on a free unlimited collaborative whiteboard

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Last Tested: 2026-09-06 08:33
Transport: Streamable HTTP
URL

Available Tools

6 tools

add_elementsAdd elements to the board or create a new oneAInspect

Creates elements on a canvas. Creates a new canvas if room_id is omitted, or adds to the existing canvas if room_id is provided. Use cases: wireframes, UI mockups, freeform illustrations, standalone shapes, and manual layouts that Mermaid does not cover well. For diagrams Mermaid can express, use add_elements_from_mermaid instead. Element types: rectangle, ellipse, diamond, arrow, line, freedraw, text, image. Rich text: the text field supports limited HTML for text elements and rectangle/ellipse/diamond shape labels. Supports the rich-text plugin HTML subset: /, /, , , /, //, , , and . Use textAlign for left/center/right alignment; avoid unsupported HTML/CSS. TEXT IN SHAPES: use containerId on text element pointing to shape id. ARROWS: Position at EDGE of source shape. Auto-bound within 30px. Colors: strokeColor, backgroundColor (hex).

ParametersJSON Schema

Name	Required	Description	Default
`room_id`	No	Room ID of an existing canvas to add to. If the user is continuing a canvas already referenced in this conversation (by room_id, or a URL like ?room=[room_id] or /gdrive?id=[room_id]), pass it here. Omit to create a new canvas.
`elements`	Yes	Array of element definitions to create

Output Schema

ParametersJSON Schema

Name	Required	Description
`url`	Yes	Canvas room URL
`isNew`	Yes	Whether a new canvas was created
`room_id`	No	Canvas room ID
`appState`	Yes	Canvas app state (viewBackgroundColor, etc.)
`elements`	Yes	All elements currently on the canvas
`collabUrl`	Yes	Collaboration server URL for Socket.IO

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations only indicate non-readonly and non-destructive, which is consistent with the description's 'creates' language. The description adds meaningful behavioral context beyond the annotations: the room_id behavior, arrow auto-binding within 30px, rich-text HTML subset, and color handling. This goes well beyond the minimal hints, though it doesn't cover every edge case.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is fairly long but well-structured with clear section headers (Rich text, TEXT IN SHAPES, ARROWS, Colors). The main purpose is front-loaded. Some redundancy exists with the schema (e.g., the HTML subset is repeated), but each section provides useful guidance. Overall, it earns its length without being bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (multiple element types, rich text, arrow binding, canvas creation), the description covers key aspects well: usage context, element types, rich-text constraints, arrow positioning, and color format. An output schema exists, so return values are not needed. Minor gaps include lack of coordinate system explanation and the textAlign reference without a schema parameter, but the description is still highly complete for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description enriches this by explaining when room_id should be used, elaborating on the element types and their inferred defaults, explaining containerId for bound text, and detailing arrow binding behavior. It adds value over the schema descriptions, though some details (like textAlign) are mentioned in the description but not present as a schema property.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates elements on a canvas and distinguishes between creating a new canvas or adding to an existing one via room_id. It explicitly names the sibling tool add_elements_from_mermaid and explains when to use that instead, making the purpose and scope unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit 'when to use' guidance with concrete use cases (wireframes, UI mockups, freeform illustrations, etc.) and directly says 'For diagrams Mermaid can express, use add_elements_from_mermaid instead.' It also explains when to pass room_id versus omit it, giving clear alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

add_elements_from_mermaidCreate a diagram from Mermaid, or add one to the boardAInspect

Creates diagram elements from a Mermaid definition. Creates a new canvas if room_id is omitted, or adds to the existing canvas if room_id is provided. Preferred over add_elements for new diagrams and large changes to existing diagrams whenever the content can be represented in Mermaid. Supports: flowchart, graph, flowchart-elk, sequenceDiagram, classDiagram, classDiagram-v2, stateDiagram, stateDiagram-v2, erDiagram, journey, gantt, pie, gitGraph, mindmap, timeline, C4Context, C4Container, C4Component, C4Dynamic, C4Deployment, sankey, sankey-beta, quadrantChart, xychart, xychart-beta, requirement, requirementDiagram, kanban, architecture, block, block-beta, packet, packet-beta, radar-beta, treemap, info. Example: "flowchart TD\n A[Start] --> B{Decision}\n B -->|Yes| C[OK]\n B -->|No| D[Cancel]"

ParametersJSON Schema

Name	Required	Description
`config`	No	Optional Mermaid rendering config. flowchart.curve is handled automatically.
`mermaid`	Yes	Mermaid diagram definition. Prefer converting compatible user requests into Mermaid instead of using add_elements.
`room_id`	No	Room ID of an existing canvas to add to. If the user is continuing a canvas already referenced in this conversation (by room_id, or a URL like ?room=[room_id] or /gdrive?id=[room_id]), pass it here. Omit to create a new canvas.
`timeout`	No	Room lifetime in seconds (default: 3600, max: 86400). Only used when creating new canvas

Output Schema

ParametersJSON Schema

Name	Required	Description
`url`	Yes	Canvas room URL
`isNew`	Yes	Whether a new canvas was created
`room_id`	No	Canvas room ID
`appState`	Yes	Canvas app state (viewBackgroundColor, etc.)
`elements`	Yes	All elements currently on the canvas
`collabUrl`	Yes	Collaboration server URL for Socket.IO
`pendingMermaid`	No	Mermaid definition pending client-side rendering

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description goes beyond the annotations by disclosing that a new canvas is created if room_id is omitted, but elements are added to an existing canvas if room_id is provided. It also notes that config.curve is handled server-side. This adds meaningful behavioral context beyond the minimal readOnly/destructive hints. It does not mention error handling or whether elements are appended vs. replaced, but key behavior is covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized: a clear first sentence, a preference statement, a list of supported diagram types, and an example. The list is long but necessary given the many Mermaid diagram types. No filler, but it could arguably be trimmed (e.g., move the full list to a separate reference). It earns a 4, not a 5, due to the length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the tool's purpose, when to use it, conditional behavior (new vs. existing canvas), supported Mermaid diagram types, and includes an example. An output schema exists, so return values need not be detailed. It misses error-handling and edge cases (e.g., invalid Mermaid), but it is fairly complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The tool description adds a few useful notes (e.g., 'prefer converting compatible user requests into Mermaid') but mostly repeats what the schema already states for parameters like room_id and timeout. It does not significantly enrich parameter understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool 'creates diagram elements from a Mermaid definition' and explains the key conditional behavior (new canvas vs. existing canvas based on room_id). It distinguishes itself from the sibling add_elements by specifying that this tool works from Mermaid and is preferred for certain cases.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly names an alternative (add_elements) and states when this tool is preferred: 'for new diagrams and large changes to existing diagrams whenever the content can be represented in Mermaid.' However, it does not explicitly state when NOT to use it (e.g., for small edits), so it falls just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

delete_elementsDelete elements from the boardA

Destructive

Inspect

Delete elements from a canvas. Requires room_id from a previous Canvs tool result. Pass ids array of element IDs to delete.

ParametersJSON Schema

Name	Required	Description	Default
`ids`	Yes	Array of element IDs to delete
`room_id`	Yes	Room ID from a previous Canvs tool result. If you only have a URL, extract it from https://[host]/?room=[room_id] or https://[host]/gdrive?id=[room_id].

Output Schema

ParametersJSON Schema

Name	Required	Description
`url`	Yes	Canvas room URL
`isNew`	Yes	Whether a new canvas was created
`room_id`	No	Canvas room ID
`appState`	Yes	Canvas app state (viewBackgroundColor, etc.)
`elements`	Yes	All elements currently on the canvas
`collabUrl`	Yes	Collaboration server URL for Socket.IO

TDQS

A4.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark destructiveHint=true, and the description explicitly says 'delete'. It adds the dependency on room_id from a prior result, but doesn't detail irreversibility or side effects. With annotations present, this is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the verb and resource, and contains no unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete tool with full schema annotations and an output schema, the description covers the necessary usage context and prerequisites. No significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters are well-described in the schema. The description only restates the ids and room_id information, adding no new semantic value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool deletes elements from a canvas, using a specific verb and resource. This distinguishes it from sibling tools like add_elements and update_elements.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides the prerequisite of room_id from a previous Canvs tool result and instructs the user to pass an ids array. Though it doesn't explicitly mention alternatives, the context is clear for a delete operation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_guideGet whiteboard instructionsA

Read-only

Inspect

Returns guidance on diagram-creation workflow and tool selection: how to choose between Mermaid and manual element creation, and the recommended iteration workflow. Consult before building complex diagrams.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`guide`	Yes	Tool usage instructions text

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful context about the guide's content and purpose, but doesn't disclose additional behavioral traits such as output format or limitations. Given the strong annotation coverage, this is sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the primary purpose, and includes a clear usage directive. Every sentence adds value with no redundant or irrelevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (no params, output schema provided), the description is complete. It explains what the guidance covers and when to use it, while the output schema handles return value details. No additional context is needed for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the description need not explain parameter details. The schema contains no properties, and the description clarifies the tool's purpose without needing to compensate for missing parameter information. Baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool 'Returns guidance on diagram-creation workflow and tool selection,' specifying the exact resource and action. It also distinguishes from sibling tools like add_elements or query_elements by focusing on advisory content rather than element manipulation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly advises to 'Consult before building complex diagrams,' providing clear usage context. It also outlines the key topics covered (Mermaid vs. manual creation, iteration workflow), but does not explicitly state when not to use it or mention alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

query_elementsFind elements on the boardA

Read-only

Inspect

Query elements on a canvas. Requires room_id from a previous Canvs tool result. Returns elements matching optional filters. Use this before update_elements when making small edits to existing diagrams. If no browser has the canvas open, returns an error — ask the user to open the canvas URL in their browser and retry.

ParametersJSON Schema

Name	Required	Description
`type`	No	Filter by element type
`filter`	No	Additional key-value filters (e.g., {locked: true})
`room_id`	Yes	Room ID from a previous Canvs tool result. If you only have a URL, extract it from https://[host]/?room=[room_id] or https://[host]/gdrive?id=[room_id].

Output Schema

ParametersJSON Schema

Name	Required	Description
`count`	Yes	Number of matching elements
`elements`	Yes	Matching elements

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false, so the read-only nature is known. The description adds valuable behavioral context not in annotations: the requirement that a browser must have the canvas open, and the specific error/retry flow. It does not over-explain.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, followed by prerequisite, usage context, and error handling. Each sentence contributes meaning, though some information (room_id requirement) is also present in the schema, making it slightly redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists and annotations cover safety, the description adequately covers the tool's purpose, prerequisites, related tools, and a key failure mode. It is complete enough for an agent to invoke correctly without further clarification.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all parameters, including a detailed room_id extraction pattern. The description only restates that room_id is required and that there are optional filters, adding minimal semantic value beyond the schema. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: querying elements on a canvas with optional filters. It also distinguishes itself from siblings by explicitly positioning it as a precursor to update_elements for small edits to existing diagrams.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit usage guidance: requires a room_id from a previous Canvs tool result, should be used before update_elements, and describes the browser-open prerequisite and how to handle the error if the browser is not open. This is well beyond minimal guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

update_elementsUpdate elements on the boardA

Destructive

Inspect

Update elements on a canvas. Requires room_id from a previous Canvs tool result. Pass elements array with id and fields to update. IMPORTANT: in each update object ONLY id is required; all other fields are optional patch fields. Include ONLY elements that need changes; elements omitted from the request remain unchanged on the board. Prefer this tool for SMALL edits to existing diagrams (rename/move/restyle a few elements), typically after query_elements.

ParametersJSON Schema

Name	Required	Description	Default
`room_id`	Yes	Room ID from a previous Canvs tool result. If you only have a URL, extract it from https://[host]/?room=[room_id] or https://[host]/gdrive?id=[room_id].
`elements`	Yes	Array of element updates (each must have id)

Output Schema

ParametersJSON Schema

Name	Required	Description
`url`	Yes	Canvas room URL
`isNew`	Yes	Whether a new canvas was created
`room_id`	No	Canvas room ID
`appState`	Yes	Canvas app state (viewBackgroundColor, etc.)
`elements`	Yes	All elements currently on the canvas
`collabUrl`	Yes	Collaboration server URL for Socket.IO

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate this is a destructive/mutating operation (readOnlyHint=false, destructiveHint=true). The description adds critical patch semantics: 'only id is required; all other fields are optional patch fields' and 'elements omitted from the request remain unchanged.' These go beyond the annotations and clarify exactly how the mutation behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact — five sentences, with key information front-loaded. The critical 'IMPORTANT' caveat is highlighted, and every sentence adds value (purpose, prerequisite, input format, patch behavior, usage context). No fluff or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (2 outer params, nested elements objects), the description covers the essential workflow: requires room_id from a previous Canvs result, passes a patch array, and is preferred for small edits after query_elements. It omits failure behavior but is otherwise complete for practical use, especially since an output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage, so the baseline is 3. The description reinforces the patch nature of 'elements' and emphasizes that fields are optional, but the schema already describes each property and the items-level note 'only id is required.' No additional meaning beyond the schema is added.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Update elements on a canvas,' using a specific verb and resource. It clearly distinguishes from siblings by emphasizing 'existing diagrams' and 'small edits' (rename/move/restyle), contrasting with add_elements and delete_elements. This makes the tool's purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance: 'Prefer this tool for SMALL edits to existing diagrams... typically after query_elements.' It also requires room_id from a previous result, covering prerequisites. It stakes a clear position among siblings, though it doesn't explicitly name build/delete alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

2 tool updatesJul 24, 2026

Changedadd_elements1 field changed

changedInput schema / properties / room_id / description

Previous value: -"Room ID. If not provided, creates a new canvas. Extract from URLs as ?room=[room_id] or /gdrive?id=[room_id]."New value: +"Room ID of an existing canvas to add to. If the user is continuing a canvas already referenced in this conversation (by room_id, or a URL like ?room=[room_id] or /gdrive?id=[room_id]), pass it here. Omit to create a new canvas."

Changedadd_elements_from_mermaid1 field changed

changedInput schema / properties / room_id / description

Previous value: -"Room ID. If not provided, creates a new canvas. Extract from URLs as ?room=[room_id] or /gdrive?id=[room_id]."New value: +"Room ID of an existing canvas to add to. If the user is continuing a canvas already referenced in this conversation (by room_id, or a URL like ?room=[room_id] or /gdrive?id=[room_id]), pass it here. Omit to create a new canvas."

2 tool updatesJun 7, 2026

Changedadd_elements2 fields changed

changedInput schema / properties / elements / items / description

Previous value: -"Per-type required fields: rectangle/ellipse/diamond → x, y (width/height default to 100). text → x, y, text (width/height auto-sized; omit or set to 0). arrow/line → x, y, points (e.g. [[0,0],[100,0]]); optionally startBinding/endBinding instead of points. image → x, y, width, height, fileId. freedraw → x, y, points. type is inferred from fields if omitted (text field → text, points → line, fileId → image, else rectangle)."New value: +"Per-type required fields: rectangle/ellipse/diamond → x, y (width/height default to 100). text → x, y, text (width/height auto-sized; omit or set to 0). rectangle/ellipse/diamond may also include text, which creates a bound label. arrow/line → x, y, points (e.g. [[0,0],[100,0]]); optionally startBinding/endBinding instead of points. image → x, y, width, height, fileId. freedraw → x, y, points. type is inferred from fields if omitted (text field → text, points → line, fileId → image, else rectangle)."

changedInput schema / properties / elements / items / properties / text / description

Previous value: -"Text content. Required for type=text. Also used as arrow label when set on an arrow."New value: +"Text content. Required for type=text. For text elements and rectangle/ellipse/diamond shape labels, Supports the rich-text plugin HTML subset: <b>/<strong>, <i>/<em>, <u>, <br>, <div>/<p>, <ul>/<ol>/<li>, <a href>, <font color>, and <span style=\"color, background/background-color, font-size, font-family\">. Use textAlign for left/center/right alignment; avoid unsupported HTML/CSS. Also used as arrow label when set on an arrow."

Changedupdate_elements1 field changed

changedInput schema / properties / elements / items / properties / text / description

Previous value: -"New text content (for text elements or arrow labels)"New value: +"New text content. For text elements and rectangle/ellipse/diamond shape labels, Supports the rich-text plugin HTML subset: <b>/<strong>, <i>/<em>, <u>, <br>, <div>/<p>, <ul>/<ol>/<li>, <a href>, <font color>, and <span style=\"color, background/background-color, font-size, font-family\">. Use textAlign for left/center/right alignment; avoid unsupported HTML/CSS. Shape text updates the bound label."

5 tool updatesJun 2, 2026

Changedadd_elements3 fields changed

addedInput schema / properties / room_id

Added value: +{
+  "description": "Room ID. If not provided, creates a new canvas. Extract from URLs as ?room=[room_id] or /gdrive?id=[room_id].",
+  "type": "string"
+}

removedInput schema / properties / room_url

Removed value: -{
-  "description": "Room URL or ID. If not provided, creates a new canvas",
-  "type": "string"
-}

addedOutput schema / properties / room_id

Added value: +{
+  "description": "Canvas room ID",
+  "type": "string"
+}

Changedadd_elements_from_mermaid3 fields changed

addedInput schema / properties / room_id

Added value: +{
+  "description": "Room ID. If not provided, creates a new canvas. Extract from URLs as ?room=[room_id] or /gdrive?id=[room_id].",
+  "type": "string"
+}

removedInput schema / properties / room_url

Removed value: -{
-  "description": "Room URL or ID. If not provided, creates a new canvas",
-  "type": "string"
-}

addedOutput schema / properties / room_id

Added value: +{
+  "description": "Canvas room ID",
+  "type": "string"
+}

Changeddelete_elements4 fields changed

addedInput schema / properties / room_id

Added value: +{
+  "description": "Room ID from a previous Canvs tool result. If you only have a URL, extract it from https://[host]/?room=[room_id] or https://[host]/gdrive?id=[room_id].",
+  "type": "string"
+}

removedInput schema / properties / room_url

Removed value: -{
-  "description": "Canvas URL from create_canvas (e.g. https://canvs.io/?room=XXXX) or a Google Drive board URL (e.g. https://canvs.io/gdrive?id=FILE_ID)",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "room_url",
-  "ids"
-]New value: +[
+  "room_id",
+  "ids"
+]

addedOutput schema / properties / room_id

Added value: +{
+  "description": "Canvas room ID",
+  "type": "string"
+}

Changedquery_elements3 fields changed

addedInput schema / properties / room_id

Added value: +{
+  "description": "Room ID from a previous Canvs tool result. If you only have a URL, extract it from https://[host]/?room=[room_id] or https://[host]/gdrive?id=[room_id].",
+  "type": "string"
+}

removedInput schema / properties / room_url

Removed value: -{
-  "description": "Canvas URL from create_canvas (e.g. https://canvs.io/?room=XXXX) or a Google Drive board URL (e.g. https://canvs.io/gdrive?id=FILE_ID)",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "room_url"
-]New value: +[
+  "room_id"
+]

Changedupdate_elements4 fields changed

addedInput schema / properties / room_id

Added value: +{
+  "description": "Room ID from a previous Canvs tool result. If you only have a URL, extract it from https://[host]/?room=[room_id] or https://[host]/gdrive?id=[room_id].",
+  "type": "string"
+}

removedInput schema / properties / room_url

Removed value: -{
-  "description": "Canvas URL from create_canvas (e.g. https://canvs.io/?room=XXXX) or a Google Drive board URL (e.g. https://canvs.io/gdrive?id=FILE_ID)",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "room_url",
-  "elements"
-]New value: +[
+  "room_id",
+  "elements"
+]

addedOutput schema / properties / room_id

Added value: +{
+  "description": "Canvas room ID",
+  "type": "string"
+}

2 tool updatesMay 24, 2026

Changedadd_elements18 fields changed

addedInput schema / properties / elements / items / description

Added value: +"Per-type required fields: rectangle/ellipse/diamond → x, y (width/height default to 100). text → x, y, text (width/height auto-sized; omit or set to 0). arrow/line → x, y, points (e.g. [[0,0],[100,0]]); optionally startBinding/endBinding instead of points. image → x, y, width, height, fileId. freedraw → x, y, points. type is inferred from fields if omitted (text field → text, points → line, fileId → image, else rectangle)."

changedInput schema / properties / elements / items / properties / containerId / description

Previous value: -"Container element ID (for text bound to shapes). Set x,y to 0,0 for auto-centering"New value: +"For type=text: ID of the shape this text is bound to. Set x,y to 0,0 for auto-centering inside the shape."

changedInput schema / properties / elements / items / properties / endBinding / description

Previous value: -"For arrows: bind end point to a shape."New value: +"For type=arrow: binds the arrow end to a shape. Use instead of or alongside points."

addedInput schema / properties / elements / items / properties / endBinding / required
```
Added value: +[
+  "elementId",
+  "focus",
+  "gap"
+]
```

changedInput schema / properties / elements / items / properties / fontFamily / description

Previous value: -"Font family: 5=Excalifont, 6=Nunito, 7=Lilita One, 8=Comic Shanns (default: 5)"New value: +"Font family: 5=Excalifont, 6=Nunito, 7=Lilita One, 8=Comic Shanns (default: 5). Applies to text elements."

changedInput schema / properties / elements / items / properties / fontSize / description

Previous value: -"Font size (default: 20)"New value: +"Font size (default: 20). Applies to text elements."

changedInput schema / properties / elements / items / properties / height / description

Previous value: -"Height (default: 100)"New value: +"Height (default: 100; omit for text — auto-sized)"

changedInput schema / properties / elements / items / properties / label / description

Previous value: -"For arrows: text label displayed on the arrow"New value: +"For type=arrow: text label displayed on the arrow"

changedInput schema / properties / elements / items / properties / points / description

Previous value: -"Points array for arrows/lines. Relative to element x,y. Example: [[0,0],[0,100]] for vertical arrow"New value: +"Required for arrow/line/freedraw. Coordinates relative to element x,y. Example: [[0,0],[100,0]] for horizontal arrow."

changedInput schema / properties / elements / items / properties / startBinding / description

Previous value: -"For arrows: bind start point to a shape."New value: +"For type=arrow: binds the arrow start to a shape. Use instead of or alongside points."

addedInput schema / properties / elements / items / properties / startBinding / required
```
Added value: +[
+  "elementId",
+  "focus",
+  "gap"
+]
```

changedInput schema / properties / elements / items / properties / text / description

Previous value: -"Text content (for text elements)"New value: +"Text content. Required for type=text. Also used as arrow label when set on an arrow."

changedInput schema / properties / elements / items / properties / type / description

Previous value: -"Element type (e.g. rectangle, ellipse, diamond, arrow, line, freedraw, text, image)"New value: +"Element type. Inferred from fields if omitted: text field → text, points → line, fileId → image, else rectangle."

addedInput schema / properties / elements / items / properties / type / enum

Added value: +[
+  "rectangle",
+  "ellipse",
+  "diamond",
+  "arrow",
+  "line",
+  "freedraw",
+  "text",
+  "image"
+]

changedInput schema / properties / elements / items / properties / width / description

Previous value: -"Width (default: 100)"New value: +"Width (default: 100; omit for text — auto-sized)"

changedInput schema / properties / elements / items / properties / x / description

Previous value: -"X coordinate"New value: +"X coordinate (defaults to 0 if omitted)"

changedInput schema / properties / elements / items / properties / y / description

Previous value: -"Y coordinate"New value: +"Y coordinate (defaults to 0 if omitted)"

changedInput schema / properties / elements / items / required

Previous value: -[
-  "type",
-  "x",
-  "y"
-]New value: +[
+  "x",
+  "y"
+]

Changedupdate_elements13 fields changed

addedInput schema / properties / elements / items / description

Added value: +"Patch object: only id is required. Include only the fields you want to change."

changedInput schema / properties / elements / items / properties / backgroundColor / description
```
Previous value: -"New fill color"New value: +"New fill color (hex or 'transparent')"
```

changedInput schema / properties / elements / items / properties / fillStyle / description

Previous value: -"New fill style"New value: +"New fill style (solid, hachure, cross-hatch)"

changedInput schema / properties / elements / items / properties / fontSize / description
```
Previous value: -"New font size"New value: +"New font size (for text elements)"
```

changedInput schema / properties / elements / items / properties / id / description

Previous value: -"Element ID to update"New value: +"ID of the element to update (required)"

addedInput schema / properties / elements / items / properties / locked

Added value: +{
+  "description": "Lock/unlock the element",
+  "type": "boolean"
+}

changedInput schema / properties / elements / items / properties / opacity / description
```
Previous value: -"New opacity"New value: +"New opacity (0-100)"
```

changedInput schema / properties / elements / items / properties / points / description

Previous value: -"New points array"New value: +"New points array (for arrow/line/freedraw elements)"

changedInput schema / properties / elements / items / properties / roughness / description

Previous value: -"New roughness"New value: +"New roughness (0=architect, 1=artist, 2=cartoonist)"

changedInput schema / properties / elements / items / properties / strokeColor / description
```
Previous value: -"New stroke color"New value: +"New stroke color (hex)"
```

changedInput schema / properties / elements / items / properties / text / description

Previous value: -"New text content"New value: +"New text content (for text elements or arrow labels)"

changedInput schema / properties / elements / items / properties / type / description

Previous value: -"New element type (e.g. rectangle, ellipse, diamond, arrow, line, freedraw, text, image)"New value: +"New element type"

addedInput schema / properties / elements / items / properties / type / enum

Added value: +[
+  "rectangle",
+  "ellipse",
+  "diamond",
+  "arrow",
+  "line",
+  "freedraw",
+  "text",
+  "image"
+]

4 tool updatesMay 23, 2026

Changedadd_elements7 fields changed

addedOutput schema / properties / appState / additionalProperties
```
Added value: +true
```

changedOutput schema / properties / appState / description

Previous value: -"Current app state (viewBackgroundColor, etc.)"New value: +"Canvas app state (viewBackgroundColor, etc.)"

addedOutput schema / properties / appState / properties

Added value: +{
+  "viewBackgroundColor": {
+    "type": "string"
+  }
+}

changedOutput schema / properties / elements / description

Previous value: -"Current scene elements for inline SVG rendering"New value: +"All elements currently on the canvas"

addedOutput schema / properties / elements / items

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

removedOutput schema / properties / pendingMermaid

Removed value: -{
-  "description": "Mermaid definition to be rendered client-side",
-  "type": "object"
-}

addedOutput schema / required

Added value: +[
+  "url",
+  "isNew",
+  "collabUrl",
+  "elements",
+  "appState"
+]

Changedadd_elements_from_mermaid8 fields changed

addedOutput schema / properties / appState / additionalProperties
```
Added value: +true
```

changedOutput schema / properties / appState / description

Previous value: -"Current app state (viewBackgroundColor, etc.)"New value: +"Canvas app state (viewBackgroundColor, etc.)"

addedOutput schema / properties / appState / properties

Added value: +{
+  "viewBackgroundColor": {
+    "type": "string"
+  }
+}

changedOutput schema / properties / elements / description

Previous value: -"Current scene elements for inline SVG rendering"New value: +"All elements currently on the canvas"

addedOutput schema / properties / elements / items

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

changedOutput schema / properties / pendingMermaid / description

Previous value: -"Mermaid definition to be rendered client-side"New value: +"Mermaid definition pending client-side rendering"

addedOutput schema / properties / pendingMermaid / properties

Added value: +{
+  "config": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "definition": {
+    "description": "Mermaid diagram source",
+    "type": "string"
+  }
+}

addedOutput schema / required

Added value: +[
+  "url",
+  "isNew",
+  "collabUrl",
+  "elements",
+  "appState"
+]

Changeddelete_elements7 fields changed

addedOutput schema / properties / appState / additionalProperties
```
Added value: +true
```

changedOutput schema / properties / appState / description

Previous value: -"Current app state (viewBackgroundColor, etc.)"New value: +"Canvas app state (viewBackgroundColor, etc.)"

addedOutput schema / properties / appState / properties

Added value: +{
+  "viewBackgroundColor": {
+    "type": "string"
+  }
+}

changedOutput schema / properties / elements / description

Previous value: -"Current scene elements for inline SVG rendering"New value: +"All elements currently on the canvas"

addedOutput schema / properties / elements / items

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

removedOutput schema / properties / pendingMermaid

Removed value: -{
-  "description": "Mermaid definition to be rendered client-side",
-  "type": "object"
-}

addedOutput schema / required

Added value: +[
+  "url",
+  "isNew",
+  "collabUrl",
+  "elements",
+  "appState"
+]

Changedupdate_elements7 fields changed

addedOutput schema / properties / appState / additionalProperties
```
Added value: +true
```

changedOutput schema / properties / appState / description

Previous value: -"Current app state (viewBackgroundColor, etc.)"New value: +"Canvas app state (viewBackgroundColor, etc.)"

addedOutput schema / properties / appState / properties

Added value: +{
+  "viewBackgroundColor": {
+    "type": "string"
+  }
+}

changedOutput schema / properties / elements / description

Previous value: -"Current scene elements for inline SVG rendering"New value: +"All elements currently on the canvas"

addedOutput schema / properties / elements / items

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

removedOutput schema / properties / pendingMermaid

Removed value: -{
-  "description": "Mermaid definition to be rendered client-side",
-  "type": "object"
-}

addedOutput schema / required

Added value: +[
+  "url",
+  "isNew",
+  "collabUrl",
+  "elements",
+  "appState"
+]

4 tool updatesMay 23, 2026

Changedadd_elements14 fields changed
- changedInput schema / properties / elements / items / properties / endBinding / description
```
Previous value: -"For arrows: bind end point to a shape. REQUIRED for connected diagrams!"New value: +"For arrows: bind end point to a shape."
```
- removedInput schema / properties / elements / items / properties / endBinding / properties / elementId / description
```
Removed value: -"ID of shape to connect to (REQUIRED)"
```
- removedInput schema / properties / elements / items / properties / endBinding / properties / focus / description
```
Removed value: -"Position on edge: -1 to 1, 0=center (REQUIRED, use 0)"
```
- removedInput schema / properties / elements / items / properties / endBinding / properties / gap / description
```
Removed value: -"Gap from shape edge in pixels (REQUIRED, use 8)"
```
- removedInput schema / properties / elements / items / properties / endBinding / required
```
Removed value: -[
-  "elementId",
-  "focus",
-  "gap"
-]
```
- removedInput schema / properties / elements / items / properties / locked
```
Removed value: -{
-  "description": "Lock element (default: false)",
-  "type": "boolean"
-}
```
- changedInput schema / properties / elements / items / properties / startBinding / description
```
Previous value: -"For arrows: bind start point to a shape. REQUIRED for connected diagrams!"New value: +"For arrows: bind start point to a shape."
```
- removedInput schema / properties / elements / items / properties / startBinding / properties / elementId / description
```
Removed value: -"ID of shape to connect to (REQUIRED)"
```
- removedInput schema / properties / elements / items / properties / startBinding / properties / focus / description
```
Removed value: -"Position on edge: -1 to 1, 0=center (REQUIRED, use 0)"
```
- removedInput schema / properties / elements / items / properties / startBinding / properties / gap / description
```
Removed value: -"Gap from shape edge in pixels (REQUIRED, use 8)"
```
- removedInput schema / properties / elements / items / properties / startBinding / required
```
Removed value: -[
-  "elementId",
-  "focus",
-  "gap"
-]
```
- changedInput schema / properties / elements / items / properties / type / description
```
Previous value: -"Element type"New value: +"Element type (e.g. rectangle, ellipse, diamond, arrow, line, freedraw, text, image)"
```
- removedInput schema / properties / elements / items / properties / type / enum
```
Removed value: -[
-  "rectangle",
-  "ellipse",
-  "diamond",
-  "arrow",
-  "line",
-  "freedraw",
-  "text",
-  "image"
-]
```
- removedInput schema / properties / timeout
```
Removed value: -{
-  "default": 3600,
-  "description": "Room lifetime in seconds (default: 3600, max: 86400). Only used when creating new canvas",
-  "type": "number"
-}
```

Changedget_guide1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "guide": {
+      "description": "Tool usage instructions text",
+      "type": "string"
+    }
+  },
+  "required": [
+    "guide"
+  ],
+  "type": "object"
+}

Changedquery_elements1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of matching elements",
+      "type": "number"
+    },
+    "elements": {
+      "description": "Matching elements",
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "elements"
+  ],
+  "type": "object"
+}

Changedupdate_elements3 fields changed

removedInput schema / properties / elements / items / properties / locked

Removed value: -{
-  "description": "Lock/unlock element",
-  "type": "boolean"
-}

changedInput schema / properties / elements / items / properties / type / description

Previous value: -"New element type"New value: +"New element type (e.g. rectangle, ellipse, diamond, arrow, line, freedraw, text, image)"

removedInput schema / properties / elements / items / properties / type / enum

Removed value: -[
-  "rectangle",
-  "ellipse",
-  "diamond",
-  "arrow",
-  "line",
-  "freedraw",
-  "text",
-  "image"
-]

1 tool updateMay 14, 2026

Changedadd_elements_from_mermaid1 field changed

changedInput schema / properties / mermaid / description

Previous value: -"Mermaid diagram definition (flowchart, sequence, or class diagram)"New value: +"Mermaid diagram definition. Prefer converting compatible user requests into Mermaid instead of using add_elements."

1 tool updateMay 13, 2026

Changedadd_elements_from_mermaid5 fields changed

changedInput schema / properties / config / description

Previous value: -"Optional Mermaid configuration"New value: +"Optional Mermaid rendering config. flowchart.curve is handled automatically."

changedInput schema / properties / config / properties / flowchart / properties / curve / description

Previous value: -"Curve style for flowchart edges (default: linear)"New value: +"Edge curve style (handled server-side; no need to set explicitly)."

changedInput schema / properties / config / properties / flowchart / properties / curve / enum
```
Previous value: -[
-  "linear",
-  "basis"
-]New value: +[
+  "basis",
+  "linear"
+]
```

removedInput schema / properties / config / properties / maxEdges

Removed value: -{
-  "description": "Maximum number of edges to render (default: 1000)",
-  "type": "number"
-}

removedInput schema / properties / config / properties / maxTextSize

Removed value: -{
-  "description": "Maximum text size (default: 1000)",
-  "type": "number"
-}

6 tool updatesMay 9, 2026
- Removedalign_elements
- Removeddistribute_elements
- Removedgroup_elements
- Removedlock_elements
- Removedungroup_elements
- Removedunlock_elements
1 tool updateMay 6, 2026
- Changedadd_elements6 fields changed
  - changedInput schema / properties / elements / items / properties / endBinding / properties / focus / description
```
Previous value: -"Position on edge: -1 to 1, 0=center (default: 0)"New value: +"Position on edge: -1 to 1, 0=center (REQUIRED, use 0)"
```
  - changedInput schema / properties / elements / items / properties / endBinding / properties / gap / description
```
Previous value: -"Gap from shape edge in pixels (default: 8)"New value: +"Gap from shape edge in pixels (REQUIRED, use 8)"
```
  - addedInput schema / properties / elements / items / properties / endBinding / required
```
Added value: +[
+  "elementId",
+  "focus",
+  "gap"
+]
```
  - changedInput schema / properties / elements / items / properties / startBinding / properties / focus / description
```
Previous value: -"Position on edge: -1 to 1, 0=center (default: 0)"New value: +"Position on edge: -1 to 1, 0=center (REQUIRED, use 0)"
```
  - changedInput schema / properties / elements / items / properties / startBinding / properties / gap / description
```
Previous value: -"Gap from shape edge in pixels (default: 8)"New value: +"Gap from shape edge in pixels (REQUIRED, use 8)"
```
  - addedInput schema / properties / elements / items / properties / startBinding / required
```
Added value: +[
+  "elementId",
+  "focus",
+  "gap"
+]
```

2 tool updatesApr 26, 2026

Changedadd_elements1 field changed

changedInput schema / properties / elements / items / properties / fontFamily / description

Previous value: -"Font family: 1=Virgil, 2=Helvetica, 3=Cascadia (default: 1)"New value: +"Font family: 5=Excalifont, 6=Nunito, 7=Lilita One, 8=Comic Shanns (default: 5)"

Changedupdate_elements1 field changed
- changedInput schema / properties / elements / items / properties / fontFamily / description
```
Previous value: -"New font family"New value: +"New font family (5=Excalifont, 6=Nunito, 7=Lilita One, 8=Comic Shanns)"
```

1 tool updateApr 21, 2026
- Removedget_image

12 tool updatesApr 19, 2026

Changedadd_elements4 fields changed

addedOutput schema / properties / appState

Added value: +{
+  "description": "Current app state (viewBackgroundColor, etc.)",
+  "type": "object"
+}

addedOutput schema / properties / collabUrl

Added value: +{
+  "description": "Collaboration server URL for Socket.IO",
+  "type": "string"
+}

addedOutput schema / properties / elements

Added value: +{
+  "description": "Current scene elements for inline SVG rendering",
+  "type": "array"
+}

addedOutput schema / properties / pendingMermaid

Added value: +{
+  "description": "Mermaid definition to be rendered client-side",
+  "type": "object"
+}

Changedadd_elements_from_mermaid4 fields changed

addedOutput schema / properties / appState

Added value: +{
+  "description": "Current app state (viewBackgroundColor, etc.)",
+  "type": "object"
+}

addedOutput schema / properties / collabUrl

Added value: +{
+  "description": "Collaboration server URL for Socket.IO",
+  "type": "string"
+}

addedOutput schema / properties / elements

Added value: +{
+  "description": "Current scene elements for inline SVG rendering",
+  "type": "array"
+}

addedOutput schema / properties / pendingMermaid

Added value: +{
+  "description": "Mermaid definition to be rendered client-side",
+  "type": "object"
+}

Changedalign_elements5 fields changed

changedInput schema / properties / room_url / description

Previous value: -"Room URL (from create_canvas) or room ID to operate on"New value: +"Canvas URL from create_canvas (e.g. https://canvs.io/?room=XXXX) or a Google Drive board URL (e.g. https://canvs.io/gdrive?id=FILE_ID)"

addedOutput schema / properties / appState

Added value: +{
+  "description": "Current app state (viewBackgroundColor, etc.)",
+  "type": "object"
+}

addedOutput schema / properties / collabUrl

Added value: +{
+  "description": "Collaboration server URL for Socket.IO",
+  "type": "string"
+}

addedOutput schema / properties / elements

Added value: +{
+  "description": "Current scene elements for inline SVG rendering",
+  "type": "array"
+}

addedOutput schema / properties / pendingMermaid

Added value: +{
+  "description": "Mermaid definition to be rendered client-side",
+  "type": "object"
+}

Changeddelete_elements5 fields changed

changedInput schema / properties / room_url / description

Previous value: -"Room URL (from create_canvas) or room ID to operate on"New value: +"Canvas URL from create_canvas (e.g. https://canvs.io/?room=XXXX) or a Google Drive board URL (e.g. https://canvs.io/gdrive?id=FILE_ID)"

addedOutput schema / properties / appState

Added value: +{
+  "description": "Current app state (viewBackgroundColor, etc.)",
+  "type": "object"
+}

addedOutput schema / properties / collabUrl

Added value: +{
+  "description": "Collaboration server URL for Socket.IO",
+  "type": "string"
+}

addedOutput schema / properties / elements

Added value: +{
+  "description": "Current scene elements for inline SVG rendering",
+  "type": "array"
+}

addedOutput schema / properties / pendingMermaid

Added value: +{
+  "description": "Mermaid definition to be rendered client-side",
+  "type": "object"
+}

Changeddistribute_elements5 fields changed

changedInput schema / properties / room_url / description

Previous value: -"Room URL (from create_canvas) or room ID to operate on"New value: +"Canvas URL from create_canvas (e.g. https://canvs.io/?room=XXXX) or a Google Drive board URL (e.g. https://canvs.io/gdrive?id=FILE_ID)"

addedOutput schema / properties / appState

Added value: +{
+  "description": "Current app state (viewBackgroundColor, etc.)",
+  "type": "object"
+}

addedOutput schema / properties / collabUrl

Added value: +{
+  "description": "Collaboration server URL for Socket.IO",
+  "type": "string"
+}

addedOutput schema / properties / elements

Added value: +{
+  "description": "Current scene elements for inline SVG rendering",
+  "type": "array"
+}

addedOutput schema / properties / pendingMermaid

Added value: +{
+  "description": "Mermaid definition to be rendered client-side",
+  "type": "object"
+}

Changedget_image1 field changed

changedInput schema / properties / room_url / description

Previous value: -"Room URL (from create_canvas) or room ID to operate on"New value: +"Canvas URL from create_canvas (e.g. https://canvs.io/?room=XXXX) or a Google Drive board URL (e.g. https://canvs.io/gdrive?id=FILE_ID)"

Changedgroup_elements5 fields changed

changedInput schema / properties / room_url / description

Previous value: -"Room URL (from create_canvas) or room ID to operate on"New value: +"Canvas URL from create_canvas (e.g. https://canvs.io/?room=XXXX) or a Google Drive board URL (e.g. https://canvs.io/gdrive?id=FILE_ID)"

addedOutput schema / properties / appState

Added value: +{
+  "description": "Current app state (viewBackgroundColor, etc.)",
+  "type": "object"
+}

addedOutput schema / properties / collabUrl

Added value: +{
+  "description": "Collaboration server URL for Socket.IO",
+  "type": "string"
+}

addedOutput schema / properties / elements

Added value: +{
+  "description": "Current scene elements for inline SVG rendering",
+  "type": "array"
+}

addedOutput schema / properties / pendingMermaid

Added value: +{
+  "description": "Mermaid definition to be rendered client-side",
+  "type": "object"
+}

Changedlock_elements5 fields changed

changedInput schema / properties / room_url / description

Previous value: -"Room URL (from create_canvas) or room ID to operate on"New value: +"Canvas URL from create_canvas (e.g. https://canvs.io/?room=XXXX) or a Google Drive board URL (e.g. https://canvs.io/gdrive?id=FILE_ID)"

addedOutput schema / properties / appState

Added value: +{
+  "description": "Current app state (viewBackgroundColor, etc.)",
+  "type": "object"
+}

addedOutput schema / properties / collabUrl

Added value: +{
+  "description": "Collaboration server URL for Socket.IO",
+  "type": "string"
+}

addedOutput schema / properties / elements

Added value: +{
+  "description": "Current scene elements for inline SVG rendering",
+  "type": "array"
+}

addedOutput schema / properties / pendingMermaid

Added value: +{
+  "description": "Mermaid definition to be rendered client-side",
+  "type": "object"
+}

Changedquery_elements1 field changed

changedInput schema / properties / room_url / description

Previous value: -"Room URL (from create_canvas) or room ID to operate on"New value: +"Canvas URL from create_canvas (e.g. https://canvs.io/?room=XXXX) or a Google Drive board URL (e.g. https://canvs.io/gdrive?id=FILE_ID)"

Changedungroup_elements5 fields changed

changedInput schema / properties / room_url / description

Previous value: -"Room URL (from create_canvas) or room ID to operate on"New value: +"Canvas URL from create_canvas (e.g. https://canvs.io/?room=XXXX) or a Google Drive board URL (e.g. https://canvs.io/gdrive?id=FILE_ID)"

addedOutput schema / properties / appState

Added value: +{
+  "description": "Current app state (viewBackgroundColor, etc.)",
+  "type": "object"
+}

addedOutput schema / properties / collabUrl

Added value: +{
+  "description": "Collaboration server URL for Socket.IO",
+  "type": "string"
+}

addedOutput schema / properties / elements

Added value: +{
+  "description": "Current scene elements for inline SVG rendering",
+  "type": "array"
+}

addedOutput schema / properties / pendingMermaid

Added value: +{
+  "description": "Mermaid definition to be rendered client-side",
+  "type": "object"
+}

Changedunlock_elements5 fields changed

changedInput schema / properties / room_url / description

Previous value: -"Room URL (from create_canvas) or room ID to operate on"New value: +"Canvas URL from create_canvas (e.g. https://canvs.io/?room=XXXX) or a Google Drive board URL (e.g. https://canvs.io/gdrive?id=FILE_ID)"

addedOutput schema / properties / appState

Added value: +{
+  "description": "Current app state (viewBackgroundColor, etc.)",
+  "type": "object"
+}

addedOutput schema / properties / collabUrl

Added value: +{
+  "description": "Collaboration server URL for Socket.IO",
+  "type": "string"
+}

addedOutput schema / properties / elements

Added value: +{
+  "description": "Current scene elements for inline SVG rendering",
+  "type": "array"
+}

addedOutput schema / properties / pendingMermaid

Added value: +{
+  "description": "Mermaid definition to be rendered client-side",
+  "type": "object"
+}

Changedupdate_elements5 fields changed

changedInput schema / properties / room_url / description

Previous value: -"Room URL (from create_canvas) or room ID to operate on"New value: +"Canvas URL from create_canvas (e.g. https://canvs.io/?room=XXXX) or a Google Drive board URL (e.g. https://canvs.io/gdrive?id=FILE_ID)"

addedOutput schema / properties / appState

Added value: +{
+  "description": "Current app state (viewBackgroundColor, etc.)",
+  "type": "object"
+}

addedOutput schema / properties / collabUrl

Added value: +{
+  "description": "Collaboration server URL for Socket.IO",
+  "type": "string"
+}

addedOutput schema / properties / elements

Added value: +{
+  "description": "Current scene elements for inline SVG rendering",
+  "type": "array"
+}

addedOutput schema / properties / pendingMermaid

Added value: +{
+  "description": "Mermaid definition to be rendered client-side",
+  "type": "object"
+}

1 tool updateFeb 15, 2026

Changedungroup_elements3 fields changed

addedInput schema / properties / elementIds

Added value: +{
+  "description": "Array of element IDs to ungroup",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / groupId

Removed value: -{
-  "description": "Group ID to ungroup",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "room_url",
-  "groupId"
-]New value: +[
+  "room_url",
+  "elementIds"
+]

13 tool updatesFeb 12, 2026
- First observedadd_elements
- First observedadd_elements_from_mermaid
- First observedalign_elements
- First observeddelete_elements
- First observeddistribute_elements
- First observedget_guide
- First observedget_image
- First observedgroup_elements
- First observedlock_elements
- First observedquery_elements
- First observedungroup_elements
- First observedunlock_elements
- First observedupdate_elements

Frequently Asked Questions

Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.

Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
- GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
- HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
- DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.

The HTTP ownership file has this structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "claim": "glama_claim_..."
}

Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.

If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.

For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Connectors

jeda-ai A
ai.jeda
Visual AI for strategic thinking — SWOT, flowcharts, mindmaps, Gantt diagrams as polished SVG.
Data Visualization Design Tools
52
UnpagedOAuth
io.unpaged
Whiteboard where any shape opens into another canvas. Your AI agent draws on it live.
Design Tools Note Taking Workplace & Productivity
1
eraserOAuth
io.eraser
Generate, edit, and manage Eraser diagrams and docs with AI.
Design Tools Software Architecture
2
hustcc-mcp-mermaid
ai.smithery
Generate dynamic Mermaid diagrams and charts with AI assistance. Customize styles and export diagr…
Software Architecture Developer Tools App Automation
2627

Related MCP Servers

Overboard Studio
Design Tools Project Management
alona-iaig
A
license
Not graded
quality
D
maintenance
Create visual whiteboards, diagrams, flowcharts, and project plans from AI conversations. 17 MCP tools for board management, element creation, and real-time collaboration.
Updated 4 months ago (2026-04-23 20:23 UTC)
1
MIT
cnvs-whiteboard
Design Tools Workplace & Productivity
lksrz
A
license
Not graded
quality
D
maintenance
Enables AI agents to collaboratively read, write, draw, and diagram on a shared real-time whiteboard canvas with live human edits.
Updated 17 days ago (2026-08-20 09:57 UTC)
1
MIT
Chart MCP Server
Data Platforms Developer Tools Research & Data
qingfeng0512
F
license
Not graded
quality
D
maintenance
Provides 15 types of chart generation tools (line, bar, pie, radar, word cloud, mind map, etc.) with AI-powered intelligent color schemes and elegant design.
Updated 8 months ago (2025-12-26 03:18 UTC)
1
-
codepic
Software Architecture Developer Tools Data Visualization
abelce
A
license
Not graded
quality
C
maintenance
Lets AI coding agents generate editable hand-drawn diagrams directly in CodePic, with support for templates and iterative updates.
Updated 3 months ago (2026-06-16 14:50 UTC)
MIT

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clear, distinct purpose: add_elements for manual creation, add_elements_from_mermaid for Mermaid-based creation, delete/query/update for lifecycle operations, and get_guide for workflow guidance. The overlap between the two creation tools is explicitly resolved in descriptions, leaving no ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: add_elements, add_elements_from_mermaid, delete_elements, get_guide, query_elements, update_elements. The modifier 'from_mermaid' extends the base pattern without breaking consistency, and all verbs are clear (add, delete, get, query, update).

Tool Count5/5

With 6 tools, the set is well-scoped for a canvas/diagram server, covering creation, query, update, delete, and guidance. This is within the ideal 3-15 range, and each tool earns its place without redundancy or bloat.

Completeness4/5

The toolset provides solid CRUD coverage for canvas elements (add, query, update, delete) plus a Mermaid import option and usage guidance. A minor gap is that there is no explicit tool to list existing canvases/rooms; agents must rely on prior room_id, which could be a friction point in new sessions, but core workflows are fully supported.

Resources

Need Help?