Your system, mapped. Your agents, aligned.
SpecsGraph is one living model of what you are building, shared by your engineers and your AI agents. It is structured, it is versioned, and it moves every time your code does.
- Identity
- Billing
- Catalog
- Orders
- Fulfilment
- Notifications
- Analytics
Works with the agents your team already runs
- Claude Code
- Cursor
- GitHub Copilot
- Any MCP client
Docs stand still. Your system keeps moving.
Most specs are already behind the code on the day they get signed off. Agents can take in far more context than a team could ever keep tidy by hand, which means the spec can finally keep pace instead of lagging.
A specification should be a habit your team keeps, not a file it hands over.
Write-once specs
- Drafted up front, then left to drift
- Scattered across wikis, tickets and chat
- Agents guess at intent from stale prose
A living graph
- Updated alongside every change
- One typed model with shared vocabulary
- Agents read and propose against real structure
From an agent’s idea to a committed spec
- Step 01
An agent proposes the change
Your coding agent talks to SpecsGraph over MCP and suggests edits directly on the system graph, right where the change belongs.
- Step 02
Requirements gain structure
Every proposal turns into typed requirements, phrased in the vocabulary your team already uses for its domain.
- Step 03
The spec lands beside the code
Once approved, changes are versioned and written into your repository, next to the code they explain.
Everything a spec needs to stay honest
Living system graph
Zoom from contexts to services to single requirements and never lose sight of the whole.
Domain glossary
Each term gets one definition, linked everywhere it appears in the model.
Workstreams
Bundle changes into tracks and tasks, and watch how the work flows toward shipped value.
Review threads
Question, discuss or sign off on any node before it becomes part of the spec.
Decision log
Capture why each change happened so the next reader inherits the reasoning, not just the result.
Git-native versions
Every revision is a commit: diff it, review it and roll it back like any other code.
Plug in the agent you already trust
SpecsGraph speaks MCP, so any compatible agent can read the graph and suggest changes to it. No custom plugins, no lock-in to a single tool.
- Claude Code
- Cursor
- GitHub Copilot
- + any MCP client
Run it the way you want
- Open source
- Self-host anywhere
- Managed cloud coming soon
Self-host the complete product today, free. SpecsGraph Cloud, where we run it for you, is coming soon.
Self-host SpecsGraphThings people usually ask
Yes, all of it. You can run it on your own infrastructure today, and a hosted SpecsGraph Cloud is coming soon.
Nothing in the product. Cloud, which is coming soon, only changes who looks after servers, upgrades and backups.
Any agent with MCP support. You choose the agent; SpecsGraph supplies the graph it works on.
No. Agents draft the proposals and your team edits, challenges and approves them.
A wiki stores pages. SpecsGraph stores a typed, linked model of your system that tools can reason about.
Specs are versioned and committed into your repository, so they evolve in the same history as the code.
Keeping the model of your system current as the product changes, rather than writing it once and watching it age.
Engineering teams that build with AI agents and want a single source of truth that everyone, human or not, can rely on.