Skip to main content
Glama

CodePic

by io.github.abelce

Server Details

AI agent draws editable hand-drawn diagrams (flowchart, ER, architecture) via MCP, not static images

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
Transport
Streamable HTTP
URL
Repository
abelce/codepic-mcp
GitHub Stars
0
Server Listing
codepic

Available Tools

7 tools
create_diagramCreate DiagramAInspect

Create a custom CodePic hand-drawn style diagram by specifying nodes and edges. Requires API Key authentication. Returns a public view URL.

THIS IS THE DEFAULT TOOL FOR ANY USER-DESCRIBED DIAGRAM. Whenever the user describes a diagram they want ("draw an A/B test flowchart", "帮我画一个登录流程", "a system architecture with a load balancer and 3 servers", etc.), build it here from their description. Do NOT fall back to create_from_template / list_templates unless the user explicitly asked for a template.

When responding to the user, present the returned URL as a clickable markdown link (e.g. [Open in CodePic →](URL)) so the user can click it directly in their AI client (Cursor / Claude / etc.).

Container nesting (IMPORTANT — use whenever possible):

  • Set parentId on a node to nest it inside another node. ANY node type can be a container.

  • The parent automatically becomes draggable-as-a-group and users can keep dropping elements into it.

  • Call get_shape_catalog with tag container-capable to choose among native structural containers and adaptive semantic shapes such as rectangles, circles, ellipses, diamonds, cylinders, and hexagons.

  • Parent bounds are expanded automatically using the selected shape's title and outline safe area.

  • Use absolute canvas coordinates for all nodes — child coordinates are auto-converted to parent-relative.

  • Set node name, description, and tags when later MCP/Agent reads need stable business semantics beyond visible text.

  • Rule: whenever 2+ nodes logically belong to the same module / component / region, create a container node first and set parentId on each child.

Design tips for beautiful diagrams:

  • Use semantic types: button-primary for CTA buttons (auto blue), diamond for decisions

  • Pick a color palette and apply it consistently — light fill + darker stroke of the same hue: • Blue: fillColor #e3f2fd / #bbdefb, strokeColor #1565c0, fontColor #1565c0 (or #ffffff on dark fill) • Green: fillColor #e8f5e9 / #c8e6c9, strokeColor #2e7d32, fontColor #1b5e20 • Purple: fillColor #f3e5f5 / #e1bee7, strokeColor #6a1b9a, fontColor #4a148c • Neutral: fillColor #f8fafc / #f1f5f9, strokeColor #475569, fontColor #1e293b

  • Each semantic group (decisions, processes, I/O) should share a fill color to create visual hierarchy

  • Dark fill (e.g. #1565c0, #ef4444) → fontColor #ffffff; light fill → fontColor #111827

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesDocument name
edgesNoArray of connector edges between nodes
nodesYesArray of shape nodes to place on the canvas
backgroundColorNoCanvas background color (default: '#f8f9fa')

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and meets it: it discloses the API-key authentication requirement, the public view URL return, and the container-nesting behaviors (auto parent-relative coordinate conversion, automatic expansion of parent bounds, draggable-as-a-group). It also documents the rule that multiple related nodes should be wrapped in a container, which shapes agent expectations about how the tool will structure the diagram.

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 long, but it is well-structured with bold section headers, bullet lists, and examples, and the purpose is front-loaded. It earns most of its length by covering container nesting and design guidance; however, some content (such as the extensive color hex list and design tips) is more reference material than invocation-critical and could be trimmed or moved to docs.

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 complex tool with no output schema, the description is remarkably complete: it specifies authentication, the returned artifact (public view URL), the sibling-routing rule, the container nesting model, coordinate conventions, and even formatting of the agent's reply. The only minor gap is error cases, but nothing essential for selecting and invoking the tool correctly is missing.

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

Parameters5/5

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

Schema coverage is 100%, so 3 would be the baseline, but the description adds substantial meaning beyond the schema: it recommends semantic types (button-primary for CTA, diamond for decisions), provides a concrete color palette with hex codes, and explains the parentId usage rule and coordinate conventions. This goes well beyond the schema's field descriptions.

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 a specific verb and resource: 'Create a custom CodePic hand-drawn style diagram by specifying nodes and edges.' It then explicitly distinguishes itself from siblings by declaring itself the default for user-described diagrams and telling the agent not to fall back to create_from_template/list_templates unless the user explicitly asked for a template. This leaves no ambiguity about what the tool does or how it differs from its siblings.

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?

It contains an explicit, bolded directive: 'THIS IS THE DEFAULT TOOL FOR ANY USER-DESCRIBED DIAGRAM,' followed by the exact conditions under which to prefer alternatives (only when the user explicitly asked for a template). It also instructs how to present the returned URL as a clickable markdown link, covering the user-facing part of usage.

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

create_from_templateCreate from TemplateAInspect

Create a new CodePic diagram from a predefined template. Requires API Key authentication. Returns a public view URL and edit URL.

STRICT USAGE RULE — READ BEFORE CALLING: Only call this tool when the user has explicitly asked to use a template. Explicit signals include phrases like: "use a template", "from template", "用模板", "从模板创建", "list templates and pick one", or the user directly naming/selecting a template slug.

If the user merely describes a diagram they want (e.g. "draw an A/B test flowchart", "帮我画一个登录流程", "给我做一个系统架构图"), DO NOT call this tool. Call create_diagram instead and build the diagram from the user's description. Never silently substitute a template for a described diagram — the user will get a generic result that does not match what they asked for.

When responding to the user, present the returned URL as a clickable markdown link (e.g. [Open in CodePic →](URL)) so the user can click it directly in their AI client (Cursor / Claude / etc.).

ParametersJSON Schema
NameRequiredDescriptionDefault
nameNoDocument name (defaults to template name)
slugYesTemplate slug (e.g. 'flowchart', 'erd', 'kanban'). Call list_templates to see all.
localeNoLanguage for template content (default: en)

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses authentication requirements, return URLs, and presentation expectations. It doesn't cover edge cases like invalid slugs or quota consumption, but covers the key behavioral aspects needed for correct invocation.

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-structured with a bold usage rule and clear sections, but is slightly verbose. The strict usage rule could be tightened without losing value, though the structure helps readability.

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 creation tool with no output schema, the description is complete: it explains the tool's purpose, usage conditions, authentication, return values, and how to present results. No critical information is missing 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.

Parameters3/5

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

Schema description coverage is 100%, so all three parameters are already well-documented in the schema (including slug examples and reference to list_templates). The description adds no additional parameter-specific meaning beyond what the schema provides, earning the baseline score.

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 a new CodePic diagram from a predefined template, using a specific verb and resource. It distinguishes itself from siblings by mentioning the template source and the explicit usage rule that differentiates it from create_diagram.

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?

The description provides explicit when-to-use and when-not-to-use criteria, naming create_diagram as the alternative and giving concrete example phrases that signal template usage versus diagram description. This is exemplary guidance that leaves no ambiguity.

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

get_diagramGet DiagramAInspect

Fetch the current state of an existing CodePic diagram. Returns a compact summary of all elements with their IDs, types, positions, and parent-child relationships. Use this before update_diagram when you need to: add nested children to existing containers, make targeted edits to specific elements, or understand the current structure. Requires API Key authentication.

ParametersJSON Schema
NameRequiredDescriptionDefault
documentIdYesDocument ID to fetch

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so the description carries the full burden. It discloses return content (compact summary with IDs, types, positions, relationships) and the authentication requirement, which are valuable behavioral details. Not quite a 5 because it lacks mentions of error handling or exact response structure, but for a simple getter it is strong.

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?

Three sentences, each contributing purpose, usage scenario, and auth requirement respectively. No fluff, well-structured and front-loaded.

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?

For a single-parameter getter with no output schema, the description explains what is returned and when to use it. It is nearly complete, though it could mention whether the operation is safe/read-only explicitly, but given no annotations, this is already decent.

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?

The schema already fully describes the only parameter (documentId) with 100% coverage. The description does not add additional meaning about the parameter, so it remains at the baseline of 3.

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 fetches the current state of an existing CodePic diagram, using a specific verb ('Fetch') and resource. It distinguishes itself from siblings like create_diagram and update_diagram by focusing on reading an existing diagram.

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?

Explicitly says 'Use this before update_diagram when you need to: add nested children...' providing concrete scenarios and naming the alternative tool. This gives clear when-to-use guidance.

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

get_shape_catalogGet Shape CatalogAInspect

Return compact machine-readable shape metadata for planning a diagram: semantic tags, geometry family, container support, recommended padding, default size, and MCP availability. Use this before create_diagram when choosing shapes or containers. Unlike get_shape_docs, this tool is concise and filterable.

ParametersJSON Schema
NameRequiredDescriptionDefault
tagNoFilter by one exact AI tag, e.g. container-capable, decision, database, or architecture.
categoryNoFilter by the shape category.
containerModeNoFilter by container support. adaptive shapes become containers when they receive children.

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are present, so the description carries the behavioral disclosure burden. It clearly signals a read-only catalog lookup with 'Return...' and lists the output fields: semantic tags, geometry family, container support, recommended padding, default size, and MCP availability. It stops short of describing exact response formatting or edge cases, so it isn't a 5.

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?

Two focused sentences carry all essential information: what the tool returns, when to use it, and how it differs from a sibling. No filler 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 there is no output schema and no annotations, the description compensates well by naming the output fields and giving usage context. It could be slightly more explicit about the response envelope or how 'MCP availability' is represented, but overall it is complete enough for safe invocation.

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%, and each parameter already has a clear description, including enum meanings. The tool description only adds that the result is 'filterable,' which is consistent but not a major semantic addition. Baseline 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 uses a specific verb and resource: 'Return compact machine-readable shape metadata for planning a diagram.' It enumerates the exact content returned and explicitly contrasts itself with get_shape_docs, making it easy to distinguish from siblings.

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?

It gives explicit timing and context: 'Use this before create_diagram when choosing shapes or containers.' It also names the alternative tool, get_shape_docs, and explains the difference, so an agent knows when to pick this tool.

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

get_shape_docsGet Shape DocsAInspect

Return the full CodePic shape reference — all element types, their fields, data payloads, and JSON examples. Call get_shape_catalog first for concise shape selection and container capabilities; use this tool when you need complete fields or type-specific data (e.g. select options, triangle direction, callout tail). No authentication required.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden. It adds a useful behavioral detail ('No authentication required') and describes what will be returned. It does not mention response size or formatting, but this is a low-risk read-only documentation lookup.

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?

Three concise sentences with no filler: purpose is front-loaded, sibling routing is second, and authentication is last. Every sentence contributes actionable 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?

With no parameters, no output schema, and no annotations, the description still tells the agent what the tool returns, when to use it versus get_shape_catalog, and that no auth is needed. Nothing essential is missing for invoking this documentation tool 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 there are no parameter semantics for the description to clarify beyond the schema. The baseline of 4 applies because parameter description is unnecessary here, and the description adds value by explaining the kind of content returned.

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 states a specific verb ('Return') and a clear resource (the full CodePic shape reference), listing what it contains: element types, fields, payloads, and JSON examples. It also differentiates itself from the sister tool get_shape_catalog by highlighting full versus concise reference material.

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?

Explicitly tells the agent to call get_shape_catalog first for concise selection and container capabilities, and to use this tool when complete fields or type-specific data are needed. This is clear routing between siblings with concrete examples.

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

list_templatesList TemplatesAInspect

List all available CodePic diagram templates. Use this ONLY when the user has explicitly asked to browse, list, or pick from templates (e.g. "show me templates", "列出模板"). Do NOT call this as a preparatory step when the user just described a diagram they want — in that case go straight to create_diagram. Discovering slugs here is only meaningful before a user-confirmed create_from_template call.

ParametersJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by category

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations provided, the description carries the full responsibility for behavioral disclosure. It gives useful context about discovering slugs and the intended workflow, but it doesn't explicitly state that the operation is read-only, what the response might contain beyond slugs, or any pagination/authorization implications. The guidance is more about when to call than what the tool actually does under the hood.

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-structured, leading with the core purpose and then providing critical usage rules. While it is longer than strictly necessary, every sentence serves a purpose—clarifying when to use the tool and when to defer to siblings. The examples ('show me templates', '列出模板') are helpful without being verbose.

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?

For a simple read-only list operation, the description covers the essential context: what it does, when to use it, and how it relates to `create_diagram` and `create_from_template`. It does not describe the return format, but since no output schema is present and the tool is straightforward, the missing information is not critical. The description adequately prepares an agent to decide when to call this tool.

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?

The schema already provides 100% coverage with a clear description and enum values for the single optional `category` parameter. The description adds no additional meaning about the parameter, but it doesn't need to—the schema is self-explanatory. This is the baseline case where the description is not expected to compensate for any gaps.

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 names a specific verb ('List'), a clear resource ('all available CodePic diagram templates'), and immediately differentiates this tool from the relevant sibling tools ('go straight to create_diagram' and 'before a user-confirmed create_from_template call'). It makes the tool's purpose unmistakable even before looking at the schema.

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?

The description explicitly states when to use the tool ('ONLY when the user has explicitly asked to browse, list, or pick from templates') and when not to ('Do NOT call this as a preparatory step'), and it names the alternative (`create_diagram`). It also clarifies the relationship with `create_from_template`, leaving no ambiguity about routing decisions.

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

update_diagramUpdate DiagramAInspect

Update an existing CodePic diagram. You can rename it, replace all nodes/edges, or add/remove individual nodes and edges. Requires API Key authentication.

When responding to the user, present the returned URL as a clickable markdown link (e.g. [Open in CodePic →](URL)) so the user can click it directly in their AI client (Cursor / Claude / etc.).

ParametersJSON Schema
NameRequiredDescriptionDefault
nameNoNew document name
edgesNoFull replacement of all edges
nodesNoFull replacement of all nodes. If provided, replaces the entire canvas content.
addEdgesNoEdges to add
addNodesNoNodes to add (without replacing existing ones)
documentIdYesDocument ID to update (from a previous create call)
removeEdgeIdsNoIDs of edges to remove
removeNodeIdsNoIDs of nodes to remove
backgroundColorNoNew canvas background color

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the mutating behaviors (rename, full replacement, add/remove) and the prerequisite (API Key auth), and includes the non-obvious instruction to present returned URLs as clickable markdown links. It does not fully detail destructive side effects such as passing `nodes` deleting existing nodes, but 'replace all' plus the schema's 'full replacement' note mitigate the gap.

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 compact and front-loaded with core update semantics, then adds auth and response-formatting instructions. The markdown-link sentence is a bit verbose with client examples, but every part is purposeful; minor redundancy keeps it from a perfect score.

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?

For a complex mutation tool with no output schema, the description covers the key invocation facts: what operations are possible, that API Key auth is required, and what to do with the returned URL. The long parameter-level details are delegated to the schema, so nothing critical is missing for an agent to call it correctly.

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 very high, with detailed explanations for nodes, edges, data, type, and other fields. The description only summarizes high-level modes (rename/replace/add/remove) without adding parameter formats or constraints, so it sits at the baseline of 3 for a schema-heavy definition.

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 uses a specific verb ('Update'), names the resource ('existing CodePic diagram'), and clearly enumerates the operation modes (rename, replace all nodes/edges, add/remove individual nodes/edges). This distinguishes it from siblings like create_diagram and get_diagram by scoping it to mutations of an existing artifact.

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

Usage Guidelines3/5

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

The phrase 'existing' implies this is the tool to call after a diagram has been created, but it never explicitly contrasts it with create_diagram/get_diagram or states 'use create_diagram to make a new one'. The response-formatting instruction is useful guidance but not about tool selection, so usage guidance remains implied rather than explicit.

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.

  1. 2 tool updates
    • Changedcreate_diagram3 fields changed
      • addedInput schema / properties / nodes / items / properties / text / anyOf
        Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "blocks": {
+        "items": {
+          "anyOf": [
+            {
+              "additionalProperties": false,
+              "properties": {
+                "runs": {
+                  "items": {
+                    "additionalProperties": false,
+                    "properties": {
+                      "href": {
+                        "format": "uri",
+                        "type": "string"
+                      },
+                      "style": {
+                        "additionalProperties": false,
+                        "properties": {
+                          "fontColor": {
+                            "minLength": 1,
+                            "type": "string"
+                          },
+                          "fontFamily": {
+                            "minLength": 1,
+                            "type": "string"
+                          },
+                          "fontSize": {
+                            "exclusiveMinimum": 0,
+                            "type": "number"
+                          },
+                          "fontStyle": {
+                            "minLength": 1,
+                            "type": "string"
+                          },
+                          "fontWeight": {
+                            "minLength": 1,
+                            "type": "string"
+                          },
+                          "textDecoration": {
+                            "enum": [
+                              "none",
+                              "underline",
+                              "line-through"
+                            ],
+                            "type": "string"
+                          }
+                        },
+                        "type": "object"
+                      },
+                      "text": {
+                        "type": "string"
+                      }
+                    },
+                    "required": [
+                      "text"
+                    ],
+                    "type": "object"
+                  },
+                  "minItems": 1,
+                  "type": "array"
+                },
+                "textAlign": {
+                  "enum": [
+                    "left",
+                    "center",
+                    "right"
+                  ],
+                  "type": "string"
+                },
+                "type": {
+                  "const": "paragraph",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "type",
+                "runs"
+              ],
+              "type": "object"
+            },
+            {
+              "additionalProperties": false,
+              "properties": {
+                "level": {
+                  "maximum": 5,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "listType": {
+                  "enum": [
+                    "ordered",
+                    "unordered"
+                  ],
+                  "type": "string"
+                },
+                "runs": {
+                  "items": {
+                    "$ref": "#/properties/nodes/items/properties/text/anyOf/0/properties/blocks/items/anyOf/0/properties/runs/items"
+                  },
+                  "minItems": 1,
+                  "type": "array"
+                },
+                "textAlign": {
+                  "enum": [
+                    "left",
+                    "center",
+                    "right"
+                  ],
+                  "type": "string"
+                },
+                "type": {
+                  "const": "list-item",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "type",
+                "listType",
+                "runs"
+              ],
+              "type": "object"
+            }
+          ]
+        },
+        "minItems": 1,
+        "type": "array"
+      },
+      "kind": {
+        "const": "rich-text",
+        "type": "string"
+      },
+      "version": {
+        "const": 1,
+        "type": "number"
+      }
+    },
+    "required": [
+      "kind",
+      "version",
+      "blocks"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "string"
+  }
+]
      • changedInput schema / properties / nodes / items / properties / text / description
        Previous value: -"Text displayed in the node"New value: +"Text content. Use RichTextContent for normal shapes; code/input use a raw string; frame uses a string title."
      • removedInput schema / properties / nodes / items / properties / text / type
        Removed value: -"string"
    • Changedupdate_diagram3 fields changed
      • addedInput schema / properties / nodes / items / properties / text / anyOf
        Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "blocks": {
+        "items": {
+          "anyOf": [
+            {
+              "additionalProperties": false,
+              "properties": {
+                "runs": {
+                  "items": {
+                    "additionalProperties": false,
+                    "properties": {
+                      "href": {
+                        "format": "uri",
+                        "type": "string"
+                      },
+                      "style": {
+                        "additionalProperties": false,
+                        "properties": {
+                          "fontColor": {
+                            "minLength": 1,
+                            "type": "string"
+                          },
+                          "fontFamily": {
+                            "minLength": 1,
+                            "type": "string"
+                          },
+                          "fontSize": {
+                            "exclusiveMinimum": 0,
+                            "type": "number"
+                          },
+                          "fontStyle": {
+                            "minLength": 1,
+                            "type": "string"
+                          },
+                          "fontWeight": {
+                            "minLength": 1,
+                            "type": "string"
+                          },
+                          "textDecoration": {
+                            "enum": [
+                              "none",
+                              "underline",
+                              "line-through"
+                            ],
+                            "type": "string"
+                          }
+                        },
+                        "type": "object"
+                      },
+                      "text": {
+                        "type": "string"
+                      }
+                    },
+                    "required": [
+                      "text"
+                    ],
+                    "type": "object"
+                  },
+                  "minItems": 1,
+                  "type": "array"
+                },
+                "textAlign": {
+                  "enum": [
+                    "left",
+                    "center",
+                    "right"
+                  ],
+                  "type": "string"
+                },
+                "type": {
+                  "const": "paragraph",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "type",
+                "runs"
+              ],
+              "type": "object"
+            },
+            {
+              "additionalProperties": false,
+              "properties": {
+                "level": {
+                  "maximum": 5,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "listType": {
+                  "enum": [
+                    "ordered",
+                    "unordered"
+                  ],
+                  "type": "string"
+                },
+                "runs": {
+                  "items": {
+                    "$ref": "#/properties/nodes/items/properties/text/anyOf/0/properties/blocks/items/anyOf/0/properties/runs/items"
+                  },
+                  "minItems": 1,
+                  "type": "array"
+                },
+                "textAlign": {
+                  "enum": [
+                    "left",
+                    "center",
+                    "right"
+                  ],
+                  "type": "string"
+                },
+                "type": {
+                  "const": "list-item",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "type",
+                "listType",
+                "runs"
+              ],
+              "type": "object"
+            }
+          ]
+        },
+        "minItems": 1,
+        "type": "array"
+      },
+      "kind": {
+        "const": "rich-text",
+        "type": "string"
+      },
+      "version": {
+        "const": 1,
+        "type": "number"
+      }
+    },
+    "required": [
+      "kind",
+      "version",
+      "blocks"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "string"
+  }
+]
      • changedInput schema / properties / nodes / items / properties / text / description
        Previous value: -"Text displayed in the node"New value: +"Text content. Use RichTextContent for normal shapes; code/input use a raw string; frame uses a string title."
      • removedInput schema / properties / nodes / items / properties / text / type
        Removed value: -"string"
  2. 3 tool updates
    • Changedcreate_diagram4 fields changed
      • addedInput schema / properties / nodes / items / properties / description
        Added value: +{
+  "description": "Concise semantic purpose of this node, independent of its visible text.",
+  "maxLength": 500,
+  "type": "string"
+}
      • addedInput schema / properties / nodes / items / properties / name
        Added value: +{
+  "description": "Stable semantic name for MCP/Agent understanding, e.g. 'payment-service'.",
+  "maxLength": 80,
+  "type": "string"
+}
      • changedInput schema / properties / nodes / items / properties / parentId / description
        Previous value: -"Parent container node ID. Nest this node inside another node (any type can be a container). The parent automatically becomes containable=true so users can keep dragging elements into it. Provide x/y as absolute canvas coordinates — they are auto-converted to parent-relative coordinates. WHEN TO USE: whenever multiple nodes logically belong to the same module, region, or component, wrap them in a shared container (frame/rect/package/swimlane) and set parentId on each child. This lets users reposition the whole group and drag additional elements into it."New value: +"Parent container node ID. Nest this node inside another node (any type can be a container). The parent automatically becomes containable=true so users can keep dragging elements into it. Call get_shape_catalog with tag='container-capable' to choose a suitable parent shape. Provide x/y as absolute canvas coordinates — they are auto-converted to parent-relative coordinates. WHEN TO USE: whenever multiple nodes logically belong to the same module, region, or component, wrap them in a shared container and set parentId on each child. This lets users reposition the whole group and drag additional elements into it."
      • addedInput schema / properties / nodes / items / properties / tags
        Added value: +{
+  "description": "Instance-level semantic tags for future MCP/Agent reads, e.g. ['backend','critical','pii']. Use get_shape_catalog tags for shape selection; use this field for the node's role in this diagram.",
+  "items": {
+    "maxLength": 48,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 12,
+  "type": "array"
+}
    • Addedget_shape_catalog
    • Changedupdate_diagram4 fields changed
      • addedInput schema / properties / nodes / items / properties / description
        Added value: +{
+  "description": "Concise semantic purpose of this node, independent of its visible text.",
+  "maxLength": 500,
+  "type": "string"
+}
      • addedInput schema / properties / nodes / items / properties / name
        Added value: +{
+  "description": "Stable semantic name for MCP/Agent understanding, e.g. 'payment-service'.",
+  "maxLength": 80,
+  "type": "string"
+}
      • changedInput schema / properties / nodes / items / properties / parentId / description
        Previous value: -"Parent container node ID. Nest this node inside another node (any type can be a container). The parent automatically becomes containable=true so users can keep dragging elements into it. Provide x/y as absolute canvas coordinates — they are auto-converted to parent-relative coordinates. WHEN TO USE: whenever multiple nodes logically belong to the same module, region, or component, wrap them in a shared container (frame/rect/package/swimlane) and set parentId on each child. This lets users reposition the whole group and drag additional elements into it."New value: +"Parent container node ID. Nest this node inside another node (any type can be a container). The parent automatically becomes containable=true so users can keep dragging elements into it. Call get_shape_catalog with tag='container-capable' to choose a suitable parent shape. Provide x/y as absolute canvas coordinates — they are auto-converted to parent-relative coordinates. WHEN TO USE: whenever multiple nodes logically belong to the same module, region, or component, wrap them in a shared container and set parentId on each child. This lets users reposition the whole group and drag additional elements into it."
      • addedInput schema / properties / nodes / items / properties / tags
        Added value: +{
+  "description": "Instance-level semantic tags for future MCP/Agent reads, e.g. ['backend','critical','pii']. Use get_shape_catalog tags for shape selection; use this field for the node's role in this diagram.",
+  "items": {
+    "maxLength": 48,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 12,
+  "type": "array"
+}
  3. 1 tool update
    • Changedlist_templates1 field changed
      • changedInput schema / properties / category / enum
        Previous value: -[
-  "collaboration",
-  "flowchart",
-  "planning",
-  "design",
-  "engineering"
-]New value: +[
+  "planning",
+  "flowchart",
+  "collaboration",
+  "design",
+  "engineering"
+]
  4. 1 tool update
    • Changedlist_templates1 field changed
      • changedInput schema / properties / category / enum
        Previous value: -[
-  "flowchart",
-  "collaboration",
-  "planning",
-  "design",
-  "engineering"
-]New value: +[
+  "collaboration",
+  "flowchart",
+  "planning",
+  "design",
+  "engineering"
+]
  5. 1 tool update
    • Changedlist_templates1 field changed
      • changedInput schema / properties / category / enum
        Previous value: -[
-  "flowchart",
-  "planning",
-  "design",
-  "engineering",
-  "collaboration"
-]New value: +[
+  "flowchart",
+  "collaboration",
+  "planning",
+  "design",
+  "engineering"
+]
  6. 1 tool update
    • Changedlist_templates1 field changed
      • changedInput schema / properties / category / enum
        Previous value: -[
-  "planning",
-  "flowchart",
-  "design",
-  "engineering",
-  "collaboration"
-]New value: +[
+  "flowchart",
+  "planning",
+  "design",
+  "engineering",
+  "collaboration"
+]
  7. 1 tool update
    • Changedlist_templates1 field changed
      • changedInput schema / properties / category / enum
        Previous value: -[
-  "planning",
-  "design",
-  "engineering",
-  "collaboration",
-  "flowchart"
-]New value: +[
+  "planning",
+  "flowchart",
+  "design",
+  "engineering",
+  "collaboration"
+]
  8. 1 tool update
    • Changedlist_templates1 field changed
      • changedInput schema / properties / category / enum
        Previous value: -[
-  "design",
-  "planning",
-  "engineering",
-  "collaboration",
-  "flowchart"
-]New value: +[
+  "planning",
+  "design",
+  "engineering",
+  "collaboration",
+  "flowchart"
+]
  9. 2 tool updates
    • Changedcreate_diagram1 field changed
      • changedInput schema / properties / nodes / items / properties / type / enum
        Previous value: -[
-  "rect",
-  "ellipse",
-  "circle",
-  "diamond",
-  "parallelogram",
-  "document",
-  "cylinder",
-  "hexagon",
-  "triangle",
-  "callout",
-  "cloud",
-  "terminator",
-  "cross",
-  "off-page-connector",
-  "actor",
-  "note",
-  "component",
-  "end-node",
-  "start-node",
-  "fork-bar",
-  "predefined-process",
-  "delay",
-  "manual-input",
-  "stored-data",
-  "text",
-  "textarea",
-  "link",
-  "icon",
-  "image",
-  "frame",
-  "package",
-  "swimlane",
-  "rounded-rect",
-  "table",
-  "button",
-  "button-primary",
-  "button-secondary",
-  "button-destructive",
-  "button-ghost",
-  "input",
-  "select",
-  "checkbox",
-  "radio",
-  "switch",
-  "slider",
-  "server",
-  "load-balancer",
-  "firewall",
-  "container",
-  "msg-queue",
-  "queue",
-  "router",
-  "lambda",
-  "cache",
-  "pod",
-  "browser-frame",
-  "mobile-frame",
-  "code"
-]New value: +[
+  "rect",
+  "ellipse",
+  "circle",
+  "diamond",
+  "parallelogram",
+  "document",
+  "cylinder",
+  "hexagon",
+  "triangle",
+  "callout",
+  "cloud",
+  "terminator",
+  "cross",
+  "off-page-connector",
+  "actor",
+  "note",
+  "component",
+  "end-node",
+  "start-node",
+  "fork-bar",
+  "predefined-process",
+  "delay",
+  "manual-input",
+  "stored-data",
+  "text",
+  "textarea",
+  "link",
+  "icon",
+  "image",
+  "frame",
+  "package",
+  "swimlane",
+  "rounded-rect",
+  "table",
+  "button",
+  "button-primary",
+  "button-secondary",
+  "button-destructive",
+  "button-ghost",
+  "input",
+  "select",
+  "checkbox",
+  "radio",
+  "switch",
+  "slider",
+  "progress",
+  "server",
+  "load-balancer",
+  "firewall",
+  "container",
+  "msg-queue",
+  "queue",
+  "router",
+  "lambda",
+  "cache",
+  "pod",
+  "browser-frame",
+  "mobile-frame",
+  "code"
+]
    • Changedupdate_diagram1 field changed
      • changedInput schema / properties / nodes / items / properties / type / enum
        Previous value: -[
-  "rect",
-  "ellipse",
-  "circle",
-  "diamond",
-  "parallelogram",
-  "document",
-  "cylinder",
-  "hexagon",
-  "triangle",
-  "callout",
-  "cloud",
-  "terminator",
-  "cross",
-  "off-page-connector",
-  "actor",
-  "note",
-  "component",
-  "end-node",
-  "start-node",
-  "fork-bar",
-  "predefined-process",
-  "delay",
-  "manual-input",
-  "stored-data",
-  "text",
-  "textarea",
-  "link",
-  "icon",
-  "image",
-  "frame",
-  "package",
-  "swimlane",
-  "rounded-rect",
-  "table",
-  "button",
-  "button-primary",
-  "button-secondary",
-  "button-destructive",
-  "button-ghost",
-  "input",
-  "select",
-  "checkbox",
-  "radio",
-  "switch",
-  "slider",
-  "server",
-  "load-balancer",
-  "firewall",
-  "container",
-  "msg-queue",
-  "queue",
-  "router",
-  "lambda",
-  "cache",
-  "pod",
-  "browser-frame",
-  "mobile-frame",
-  "code"
-]New value: +[
+  "rect",
+  "ellipse",
+  "circle",
+  "diamond",
+  "parallelogram",
+  "document",
+  "cylinder",
+  "hexagon",
+  "triangle",
+  "callout",
+  "cloud",
+  "terminator",
+  "cross",
+  "off-page-connector",
+  "actor",
+  "note",
+  "component",
+  "end-node",
+  "start-node",
+  "fork-bar",
+  "predefined-process",
+  "delay",
+  "manual-input",
+  "stored-data",
+  "text",
+  "textarea",
+  "link",
+  "icon",
+  "image",
+  "frame",
+  "package",
+  "swimlane",
+  "rounded-rect",
+  "table",
+  "button",
+  "button-primary",
+  "button-secondary",
+  "button-destructive",
+  "button-ghost",
+  "input",
+  "select",
+  "checkbox",
+  "radio",
+  "switch",
+  "slider",
+  "progress",
+  "server",
+  "load-balancer",
+  "firewall",
+  "container",
+  "msg-queue",
+  "queue",
+  "router",
+  "lambda",
+  "cache",
+  "pod",
+  "browser-frame",
+  "mobile-frame",
+  "code"
+]
  10. 1 tool update
    • Changedlist_templates1 field changed
      • changedInput schema / properties / category / enum
        Previous value: -[
-  "planning",
-  "engineering",
-  "design",
-  "collaboration",
-  "flowchart"
-]New value: +[
+  "design",
+  "planning",
+  "engineering",
+  "collaboration",
+  "flowchart"
+]
  11. 1 tool update
    • Changedlist_templates1 field changed
      • changedInput schema / properties / category / enum
        Previous value: -[
-  "engineering",
-  "planning",
-  "design",
-  "collaboration",
-  "flowchart"
-]New value: +[
+  "planning",
+  "engineering",
+  "design",
+  "collaboration",
+  "flowchart"
+]
  12. 2 tool updates
    • Changedcreate_diagram1 field changed
      • changedInput schema / properties / nodes / items / properties / fontFamily / description
        Previous value: -"Font family (default: 'pigtruman, sans-serif')"New value: +"Font family (default: 'Inter, sans-serif')"
    • Changedupdate_diagram1 field changed
      • changedInput schema / properties / nodes / items / properties / fontFamily / description
        Previous value: -"Font family (default: 'pigtruman, sans-serif')"New value: +"Font family (default: 'Inter, sans-serif')"
  13. 1 tool update
    • Changedlist_templates1 field changed
      • changedInput schema / properties / category / enum
        Previous value: -[
-  "planning",
-  "design",
-  "collaboration",
-  "engineering",
-  "flowchart"
-]New value: +[
+  "engineering",
+  "planning",
+  "design",
+  "collaboration",
+  "flowchart"
+]
  14. 1 tool update
    • Changedlist_templates1 field changed
      • changedInput schema / properties / category / enum
        Previous value: -[
-  "design",
-  "planning",
-  "collaboration",
-  "engineering",
-  "flowchart"
-]New value: +[
+  "planning",
+  "design",
+  "collaboration",
+  "engineering",
+  "flowchart"
+]
  15. 1 tool update
    • Changedlist_templates1 field changed
      • changedInput schema / properties / category / enum
        Previous value: -[
-  "planning",
-  "collaboration",
-  "engineering",
-  "flowchart",
-  "design"
-]New value: +[
+  "design",
+  "planning",
+  "collaboration",
+  "engineering",
+  "flowchart"
+]
  16. 1 tool update
    • Changedlist_templates1 field changed
      • changedInput schema / properties / category / enum
        Previous value: -[
-  "collaboration",
-  "planning",
-  "engineering",
-  "flowchart",
-  "design"
-]New value: +[
+  "planning",
+  "collaboration",
+  "engineering",
+  "flowchart",
+  "design"
+]
  17. 1 tool update
    • Changedlist_templates1 field changed
      • changedInput schema / properties / category / enum
        Previous value: -[
-  "planning",
-  "engineering",
-  "flowchart",
-  "collaboration",
-  "design"
-]New value: +[
+  "collaboration",
+  "planning",
+  "engineering",
+  "flowchart",
+  "design"
+]
  18. 1 tool update
    • Changedlist_templates1 field changed
      • changedInput schema / properties / category / enum
        Previous value: -[
-  "engineering",
-  "planning",
-  "flowchart",
-  "collaboration",
-  "design"
-]New value: +[
+  "planning",
+  "engineering",
+  "flowchart",
+  "collaboration",
+  "design"
+]
  19. 1 tool update
    • Changedlist_templates1 field changed
      • changedInput schema / properties / category / enum
        Previous value: -[
-  "planning",
-  "engineering",
-  "flowchart",
-  "collaboration",
-  "design"
-]New value: +[
+  "engineering",
+  "planning",
+  "flowchart",
+  "collaboration",
+  "design"
+]

Frequently Asked Questions

Discussions

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

Login with GitHub to comment

Related MCP Connectors

Related MCP Servers

  • Lousa

    henriquepe
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to draw animated, hand-drawn diagrams on a live whiteboard through MCP tools, allowing users to visually explain concepts and edit scenes interactively.
    45
    AGPL 3.0

  • inkwire

    TheTechChild
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables visual collaboration with an AI agent on a codebase through a shared drawing canvas, where hand-drawn diagrams are inferred as editable structure over MCP.
    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 distinct purpose: create, get, update, list templates, and get shape documentation. No overlapping or ambiguous functions.

Naming Consistency5/5

All tool names follow a clear verb_noun pattern (create_diagram, get_diagram, get_shape_docs, list_templates, update_diagram), with consistent use of underscores and action-first naming.

Tool Count5/5

The tool count (5 listed, though count says 6) is well within the typical 3–15 range for this domain, providing a focused set without unnecessary bloat.

Completeness3/5

The set covers create, read, and update operations, but lacks a delete tool and a way to list all diagrams (only templates are listed). This leaves gaps in the lifecycle coverage, though the core diagram creation workflow is supported.

Resources