plantuml-mcp-server

Provides an MCP server that lets an agent generate PlantUML diagrams (e.g., sequence/class/C4) and return embeddable URLs or images, plus encode/decode PlantUML for URL sharing.

Evaluated Mar 30, 2026 (21d ago)
Repo ↗ DevTools mcp plantuml diagram-generation claude developer-tools nodejs
⚙ Agent Friendliness
62
/ 100
Can an agent use this?
🔒 Security
48
/ 100
Is it safe for agents?
⚡ Reliability
35
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
78
Documentation
70
Error Messages
0
Auth Simplicity
95
Rate Limits
0

🔒 Security

TLS Enforcement
80
Auth Strength
40
Scope Granularity
0
Dep. Hygiene
55
Secret Handling
70

Security guidance is limited to local file output restrictions (CWD-only by default; extension and allowlist controls). No explicit guidance is provided for sanitizing PlantUML inputs, controlling !include/external resource access, enforcing TLS beyond using a likely HTTPS URL, or handling upstream server auth. The dependency list is small but no vulnerability status is provided.

⚡ Reliability

Uptime/SLA
0
Version Stability
55
Breaking Changes
35
Error Recovery
50
AF Security Reliability

Best When

You want an agent-friendly way to generate PlantUML diagrams inside an MCP-capable LLM client, using either the default public PlantUML service or your own PlantUML server.

Avoid When

You cannot ensure safe handling of PlantUML features like !include or external libraries, or you need strong guarantees about SSRF/file access beyond the tool’s documented output path restrictions.

Use Cases

  • Integrate PlantUML diagram generation into Claude Desktop/Claude Code via MCP
  • Automatically generate sequence, class, and architecture diagrams from structured prompts
  • Share diagrams by encoding PlantUML into URL-safe strings
  • Render diagrams through a configurable upstream PlantUML server URL
  • Optionally save rendered diagrams locally with directory allowlisting

Not For

  • Running untrusted PlantUML that could rely on external includes/libraries without sandboxing
  • High-security environments that cannot control file-system write locations beyond the documented allowlist
  • Teams needing a first-class REST/SDK platform for PlantUML generation outside the MCP workflow

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: No auth documented for the MCP server itself (uses environment variable for upstream PlantUML URL)
OAuth: No Scopes: No

Authentication/authorization to the upstream PlantUML server is not described; configuration is via PLANTUML_SERVER_URL only.

Pricing

Free tier: No
Requires CC: No

No pricing information for the MCP server is provided in the supplied README data.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Documented

Known Gotchas

  • Tool relies on an external PlantUML server URL; availability/behavior depends on that upstream service
  • Using output_path requires directory allowlisting via PLANTUML_ALLOWED_DIRS; misconfiguration can cause failures
  • PlantUML features like !include may need additional upstream support and can complicate security/sandboxing

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for plantuml-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-30.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered