Koskamo

Zovo Use Case Diagram MCP

This MCP server converts plain text descriptions of actors, use cases, and system boundaries into UML use case diagrams. It validates the input against a strict grammar, checks for logical errors like orphaned actors or cycles, and generates PDF, SVG, and CSV outputs. It supports features such as include/extend relationships, actor generalization, and system boundaries.

Visit Zovo

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Zovo Use Case Diagram MCP logo, by ZovoCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-08Published by Zovo
MCP endpoint (Streamable HTTP)
https://use-case-diagram.zovo.one/mcp
Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (2)

2 of 2 have a description · 2 of 2 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Generate UML use case diagrams from plain text
  • Validate use case diagram text for errors
  • Export diagrams to PDF, SVG, and CSV

Source and maintenance

Community listingRegistry 1.0.0
mcp-registry: io.github.theluckystrike/use-case-diagram@1.0.0Project website

Protocol and capabilities

Server
use-case-diagram 1.0.0
MCP protocol negotiated in check
2025-11-25
Tools
2 advertised
Resources
1 advertised
Resource templates
1 advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  },
  "resources": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Zovo Use Case Diagram draws a UML use case diagram from a short line grammar, with PDF, SVG and CSV downloads, and checks it: actors with no use case, use cases no actor reaches, and include/extend cycles. Use make_use_case_diagram to draw it and check_use_case_diagram to check the text without drawing. Grammar, one statement per line: actor Name; actor "Long name" as A; usecase Name; usecase "Text" as UC1; system "Name" { ... } holding use case lines (not nested); A -- UC1; UC1 ..> UC2 : include; UC3 ..> UC1 : extend; Admin --|> User; note UC1: text; # comments. A line outside the grammar is refused with its line number and the token, and nothing is drawn. When the user describes the diagram in words, write it in this grammar first and show it with the result. Files of large diagrams are kept for 1 hour so the download links work, then deleted.

Tools

2 advertised

make_use_case_diagram — Make use case diagram
Advertised by the server during the last successful anonymous check.
Advertised read-only

Use this when the user wants a UML use case diagram drawn, for example "draw the use cases of an online shop" or "make a PDF use case diagram of this system". Takes the diagram text in a line grammar: actor Name / actor "Long name" as A; usecase Name / usecase "Text" as UC1; system "Name" { ... } (use cases inside belong to it; not nested); A -- UC1 (association); UC1 ..> UC2 : include; UC3 ..> UC1 : extend; Admin --|> User (actor generalization); note UC1: text; # comments. When the user describes the diagram in words, write it in this grammar first. Returns counts, elements, relations in input order, the diagram check (actors with no use case, use cases no actor reaches, include/extend cycles), a check on the drawing, the PDF page count, an interactive diagram, and PDF, SVG and CSV downloads. Refuses a line outside the grammar, unknown names, relations between the wrong kinds of element and generalization cycles, with the line number and token. Up to 30 actors, 80 use cases, 6 systems and 300 relations. Does not read use case generalization, packages or nested systems. Download links of large diagrams expire after about 1 hour.

make_use_case_diagram input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "diagram"
  ],
  "properties": {
    "title": {
      "type": "string",
      "maxLength": 400,
      "description": "Title printed on the diagram and used in file names, up to 80 characters, e.g. \"Online shop\"."
    },
    "diagram": {
      "type": "string",
      "maxLength": 100000,
      "description": "The use case diagram in this line grammar, one statement per line, up to 40,000 characters: actor Name | actor \"Long name\" as A | usecase Name | usecase \"Text\" as UC1 | system \"Name\" { ... } (use case lines inside belong to that system; not nested) | A -- UC1 (association) | UC1 ..> UC2 : include | UC3 ..> UC1 : extend | Admin --|> User (actor generalization) | note UC1: text | # comment. Declare each actor and use case before or after use. Example: \"actor Customer\\nsystem \\\"Shop\\\" {\\nusecase \\\"Place order\\\" as Order\\nusecase Pay\\n}\\nCustomer -- Order\\nOrder ..> Pay : include\"."
    },
    "page_size": {
      "enum": [
        "letter",
        "a4"
      ],
      "type": "string",
      "description": "PDF paper: letter (default) or a4. The PDF is portrait, or landscape when the diagram is too wide for portrait. Example: a4."
    }
  }
}
make_use_case_diagram output schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "title",
    "counts",
    "elements",
    "relations",
    "analysis",
    "pdf",
    "layout_check",
    "warnings",
    "downloads"
  ],
  "properties": {
    "pdf": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "shown": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "title": {
      "type": "string"
    },
    "counts": {
      "type": "object",
      "required": [
        "actors",
        "use_cases",
        "systems",
        "relations",
        "associations",
        "includes",
        "extends",
        "generalizations",
        "notes"
      ],
      "properties": {
        "notes": {
          "type": "number"
        },
        "actors": {
          "type": "number"
        },
        "extends": {
          "type": "number"
        },
        "systems": {
          "type": "number"
        },
        "includes": {
          "type": "number"
        },
        "relations": {
          "type": "number"
        },
        "use_cases": {
          "type": "number"
        },
        "associations": {
          "type": "number"
        },
        "generalizations": {
          "type": "number"
        }
      },
      "additionalProperties": false
    },
    "analysis": {
      "type": "object",
      "required": [
        "actors_without_use_case",
        "use_cases_without_actor",
        "include_extend_cycles",
        "empty_systems"
      ],
      "properties": {
        "empty_systems": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "include_extend_cycles": {
          "type": "array",
          "items": {
            "type": "array",
            "items": {
              "type": "string"
            }
          }
        },
        "actors_without_use_case": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "use_cases_without_actor": {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      },
      "additionalProperties": false
    },
    "elements": {
      "type": "array",
      "items": {
        "type": "object",
        "propertyNames": {
          "type": "string"
        },
        "additionalProperties": {}
      }
    },
    "warnings": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "downloads": {
      "type": "object",
      "properties": {
        "csv": {
          "type": "string"
        },
        "pdf": {
          "type": "string"
        },
        "svg": {
          "type": "string"
        }
      },
      "additionalProperties": false
    },
    "relations": {
      "type": "array",
      "items": {
        "type": "object",
        "propertyNames": {
          "type": "string"
        },
        "additionalProperties": {}
      }
    },
    "layout_check": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    }
  },
  "additionalProperties": false
}
make_use_case_diagram annotations
{
  "title": "Make use case diagram",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
check_use_case_diagram — Check use case diagram text
Advertised by the server during the last successful anonymous check.
Advertised read-only

Use this when the user wants use case diagram text checked without a drawing, for example "which use cases have no actor?" or "check my use case diagram". Takes the same diagram text as make_use_case_diagram. Returns ready true or false; when a line breaks the grammar (also unknown names, relations between the wrong kinds of element, or a generalization cycle), the line number, the token and the reason; otherwise the elements with their relation counts, actors with no use case (an actor counts when it or an actor it specializes has an association), use cases no actor reaches (directly, through include, or as an extension of a reached use case), and include/extend cycles. Does not draw the diagram or make files.

check_use_case_diagram input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "diagram"
  ],
  "properties": {
    "diagram": {
      "type": "string",
      "maxLength": 100000,
      "description": "The use case diagram in this line grammar, one statement per line, up to 40,000 characters: actor Name | actor \"Long name\" as A | usecase Name | usecase \"Text\" as UC1 | system \"Name\" { ... } (use case lines inside belong to that system; not nested) | A -- UC1 (association) | UC1 ..> UC2 : include | UC3 ..> UC1 : extend | Admin --|> User (actor generalization) | note UC1: text | # comment. Declare each actor and use case before or after use. Example: \"actor Customer\\nsystem \\\"Shop\\\" {\\nusecase \\\"Place order\\\" as Order\\nusecase Pay\\n}\\nCustomer -- Order\\nOrder ..> Pay : include\"."
    }
  }
}
check_use_case_diagram output schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "ready",
    "elements",
    "error",
    "notes",
    "grammar",
    "limits"
  ],
  "properties": {
    "error": {
      "anyOf": [
        {
          "type": "object",
          "propertyNames": {
            "type": "string"
          },
          "additionalProperties": {}
        },
        {
          "type": "null"
        }
      ]
    },
    "notes": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "ready": {
      "type": "boolean"
    },
    "shown": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "counts": {
      "type": "object",
      "required": [
        "actors",
        "use_cases",
        "systems",
        "relations",
        "associations",
        "includes",
        "extends",
        "generalizations",
        "notes"
      ],
      "properties": {
        "notes": {
          "type": "number"
        },
        "actors": {
          "type": "number"
        },
        "extends": {
          "type": "number"
        },
        "systems": {
          "type": "number"
        },
        "includes": {
          "type": "number"
        },
        "relations": {
          "type": "number"
        },
        "use_cases": {
          "type": "number"
        },
        "associations": {
          "type": "number"
        },
        "generalizations": {
          "type": "number"
        }
      },
      "additionalProperties": false
    },
    "limits": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "grammar": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "analysis": {
      "type": "object",
      "required": [
        "actors_without_use_case",
        "use_cases_without_actor",
        "include_extend_cycles",
        "empty_systems"
      ],
      "properties": {
        "empty_systems": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "include_extend_cycles": {
          "type": "array",
          "items": {
            "type": "array",
            "items": {
              "type": "string"
            }
          }
        },
        "actors_without_use_case": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "use_cases_without_actor": {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      },
      "additionalProperties": false
    },
    "elements": {
      "type": "array",
      "items": {
        "type": "object",
        "propertyNames": {
          "type": "string"
        },
        "additionalProperties": {}
      }
    }
  },
  "additionalProperties": false
}
check_use_case_diagram annotations
{
  "title": "Check use case diagram text",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

1 advertised

use-case-diagram-widget — Zovo Use Case Diagram view

Advertised by the server during the last successful anonymous check.

Interactive view for Zovo Use Case Diagram.

use-case-diagram-widget URI
ui://widget/use-case-diagram-v1-1.0.0-9279add9b9daf92f6a2d82026a46d4b72b3f4b3295b413718325d02b12a28cd4.html

MIME type: text/html;profile=mcp-app

use-case-diagram-widget-legacy — Zovo Use Case Diagram view (previous versions)

Advertised by the server during the last successful anonymous check.

use-case-diagram-widget-legacy URI template
ui://widget/use-case-diagram-{version}.html

MIME type: text/html;profile=mcp-app

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
347 ms
95th percentile latency
347 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 347 ms · metadata changed · 2 tool(s), 1 resource(s), 1 resource template(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http zovo-use-case-diagram-mcp https://use-case-diagram.zovo.one/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add zovo-use-case-diagram-mcp --url https://use-case-diagram.zovo.one/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable zovo-use-case-diagram-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "zovo-use-case-diagram-mcp": {
      "url": "https://use-case-diagram.zovo.one/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "zovo-use-case-diagram-mcp": {
      "type": "streamableHttp",
      "url": "https://use-case-diagram.zovo.one/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start zovo-use-case-diagram-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "zovo-use-case-diagram-mcp": {
      "type": "http",
      "url": "https://use-case-diagram.zovo.one/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http zovo-use-case-diagram-mcp https://use-case-diagram.zovo.one/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://use-case-diagram.zovo.one/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "zovo-use-case-diagram-mcp": {
      "serverUrl": "https://use-case-diagram.zovo.one/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Zovo Use Case Diagram MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 8,931