Skip to main content
Glama
README.md
# UML Forge MCP Connector

<!-- mcp-name: io.github.dave1362/umlforge -->

**Architecture intelligence, security analysis, and living documentation ? inside your coding agent.**

[UML Forge](https://umlforge.dev) gives Claude Code, Cursor, Windsurf, and any
MCP-compatible coding agent a suite of 14 specialised tools for producing
professional UML diagrams from your codebase, schema, or architecture
descriptions.

## Quick start

**Claude Code:**
```json
{
  "mcpServers": {
    "umlforge": {
      "command": "uvx",
      "args": ["umlforge"],
      "env": { "UMLFORGE_API_KEY": "your-api-key" }
    }
  }
}
```

**Cursor / Windsurf** ? add the same block to your MCP settings.

Get your API key at [umlforge.dev](https://umlforge.dev).

## Tools included

| Tool | Description |
|------|-------------|
| `umlforge_suggest` | **Start here.** Describe your goal in plain English ? returns the right tool and a ready-to-run call |
| `umlforge_reverse_engineer` | Class, sequence, and state diagrams from a codebase or GitHub URL |
| `umlforge_api_sequence` | Sequence diagrams for request flows across services |
| `umlforge_erd_schema` | Entity-relationship diagrams from domain descriptions or SQL schemas |
| `umlforge_state_machine` | State diagrams from entity lifecycles and business rules |
| `umlforge_frontend_components` | Component hierarchy and interaction diagrams for UI features |
| `umlforge_deployment` | Infrastructure and CI/CD pipeline diagrams |
| `umlforge_threat_model` | STRIDE threat model + attack surface diagram |
| `umlforge_event_driven` | Event flow and pub/sub architecture diagrams |
| `umlforge_ai_agent` | Agent topology and tool-call flow diagrams for LLM pipelines |
| `umlforge_stakeholder_arch` | C4 context diagrams for investors, CTOs, and non-technical stakeholders |
| `umlforge_living_docs` | Update existing diagrams to reflect sprint or PR changes |
| `umlforge_onboarding` | Day-one knowledge-transfer package for new team members |
| `umlforge_legacy_migration` | Legacy structure + modern architecture diagrams and 6-phase migration roadmap from COBOL, Fortran, ABAP, RPG, and other legacy languages |

All tools accept `report_mode=True` to generate a written analysis report
alongside the diagram.

## Requirements

- Python 3.11+
- An API key from [umlforge.dev](https://umlforge.dev) (free tier available)

## License

MIT ? see [LICENSE](LICENSE).

TDQS

A4.7/5.0

Scored across 14 tools

Disambiguation5/5

Each tool targets a clearly distinct modeling domain (reverse engineering, legacy migration, C4, threat modeling, API sequence, state machine, living docs, ERD, frontend, event-driven, onboarding, AI agents, deployment, suggest). The descriptions include explicit NOT FOR sections that disambiguate borderline cases. The suggest tool further reduces risk of misselection.

Naming Consistency5/5

All 14 tool names follow a consistent snake_case pattern with no mixed conventions. The umlforge_ prefix is applied uniformly. Names are descriptive and adhere to a verb/noun or domain noun style.

Tool Count5/5

14 tools is an ideal count for a comprehensive UML/diagramming server covering many distinct modeling aspects. Each tool has a unique, justified purpose, and the set is well-scoped without excessive overlap or gaps that would suggest missing tools.

Completeness5/5

The toolset covers a wide range of diagram types and analysis workflows: reverse engineering, design from scratch (stakeholder_arch), state machines, sequence diagrams, ERDs, deployment, threat modeling, event-driven, AI agents, legacy migration, onboarding, living docs updates, and a suggestion helper. This represents near-complete lifecycle coverage for UML and architecture documentation.

Maintenance

ActivityMaintained
ResponsivenessNo issues