rendering
PlantUML MCP Integration for LangChain
Connect PlantUML to LangChain through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.
Connect PlantUML to LangChain
Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls.
Use the MCP gateway when the agent should discover tools, or wrap kosmo integrations:call for fixed chains. The gateway is local, scoped to this integration, and starts with
--write=deny so LangChain can inspect read-capable tools without receiving write access by default.
PlantUML MCP Config for LangChain
Keep the gateway scoped to the integration and operation class needed by the chain.
{
"mcpServers": {
"kosmokrator-plantuml": {
"type": "stdio",
"command": "kosmo",
"args": [
"mcp:serve",
"--integration=plantuml",
"--write=deny"
]
}
}
} Run the Gateway Manually
kosmokrator mcp:serve --integration=plantuml --write=deny Why Use KosmoKrator Here
Expose only PlantUML instead of a broad multi-service tool list.
Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.
Start read-only, then opt into ask or allow for trusted workspaces.
PlantUML Tools Visible to LangChain
LangChain sees stable MCP tool names generated from the PlantUML integration catalog.
| MCP tool | Source function | Type | Description |
|---|---|---|---|
integration__plantuml__render_plantuml | plantuml.render_plantuml | Write | Render a PlantUML diagram to a PNG image. Pass valid PlantUML syntax and get back a markdown image embed. Supported diagram types: class, sequence, activity, component, state, use case, object, deployment, timing, network (nwdiag), wireframe (salt), Gantt, mindmap, WBS, JSON, YAML, ERD. Example syntax: ``` @startuml Alice -> Bob: Authentication Request Bob --> Alice: Authentication Response Alice -> Bob: Another request Bob --> Alice: Another response @enduml ``` Tips: - Always wrap syntax in @startuml / @enduml - Use `->` for solid arrows, `-->` for dashed arrows - Use `class ClassName { }` blocks for class diagrams - Use `(*) -->` for activity diagram start - Use `[Component]` for component diagrams - Use `state "Name" as s1` for state diagrams |