Zovo Use Case Diagram

io.github.theluckystrikePublished by GitHub account theluckystrikev1.0.0Updated Nov 8, 2026

Turn a few lines of text into a UML use case diagram document, and check it.

The publisher's own server: Diagram

VerifiedStreamable HTTPWeb executableDeveloper ToolsMedia & Design

Overview

AI-generated overview

Draws UML use case diagrams from a short line-based grammar, with PDF, SVG and CSV downloads, and checks the diagram text for problems.

What you can do
  • Draw a UML use case diagram from line-grammar text and get PDF, SVG and CSV downloads
  • Check diagram text without drawing it, reporting actors with no use case, unreachable use cases, and include/extend cycles
  • Validate grammar, returning the offending line number and token when a line is refused
  • Parse actors, use cases, systems, associations, generalizations, include/extend relations, notes and comments
When to use it
Useful when you want an assistant to turn a described system into a use case diagram document, or to sanity-check use case text before drawing it. Suited to quick UML documentation rather than editing existing diagram files.
Requirements
A remote MCP endpoint; no package, account, API key or environment variable is declared. Network access to the hosted endpoint is needed to draw and download files.
Before you install
Generated files for large diagrams are kept for only 1 hour before deletion, so download links stop working after that. Invalid lines cause the whole request to be refused and nothing is drawn.

Installation

In SourceWeft

  1. Open Zovo Use Case Diagram in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.theluckystrike%2Fuse-case-diagram/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "zovo-use-case-diagram": {
      "type": "http",
      "url": "https://use-case-diagram.zovo.one/mcp"
    }
  }
}

Tools

2

make_use_case_diagram

Make use case diagram

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.

Parameterstitlediagramrequiredpage_size

check_use_case_diagram

Check use case diagram text

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.

Parametersdiagramrequired

Version history

1
  1. v1.0.0LatestNov 8, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Diagram integrations