Diagrams that stay aligned with your code
I built Planform because I was tired of diagrams that drift from my code. It's a UML editor that connects to your codebase through MCP. Your AI assistant (Cursor, Copilot, Claude Code) generates diagrams from your code. You edit them here. Then have the AI implement changes back.
What is Planform?
It's a UML diagram editor that uses MCP (Model Context Protocol) to connect to your codebase. I got tired of manually creating diagrams that become outdated the moment I change my code. So I built this to let AI assistants do the heavy lifting—generate diagrams from code, let you edit them, then implement changes back.
The problem with diagrams today
- You spend time creating diagrams manually, then they're outdated as soon as you refactor
- There's no bridge between your code and diagrams—can't generate from code or push changes back
- Context switching between diagram tools and your editor kills productivity
How it works
Planform uses MCP (Model Context Protocol) to connect diagrams to your codebase. If you're already using Cursor, Copilot, or Claude Code, they can read your code and generate diagrams. You refine them in Planform, then tell your AI to implement those changes back into your code.
The diagrams come from your actual code structure, not some abstract design. It's bidirectional: code → diagram → code. You're not manually keeping things in sync.
What you can do
- Ask your AI assistant to generate UML diagrams from your codebase
- Edit and refine diagrams in Planform's editor
- Have your AI implement diagram changes back into your code
- Keep diagrams that actually reflect your code structure