What agents get
Query services, relationships, groups, and documentation hooks from the compiled architecture map. Agents see the same topology humans explore in the interactive Cytoscape graph.
MCP architecture server
MCP for AI agents - architecture context with Git provenance
As of 2026, AI agents need trustworthy system context. Navo’s MCP server serves the same living map your team browses - compiled from Git YAML - so agent answers stay grounded in the architecture source of truth.
Why provenance matters
Unlike screenshots or chat-pasted diagrams, Navo’s MCP context is derived from versioned YAML in Git. Changes land through pull requests and CI validation before agents (or people) see them.
How it fits the stack
MCP ships with Community. Pair it with the interactive browser, in-app wiki, and CLI imports so humans and agents share one map - deployable as a static SPA with no heavy portal platform.
FAQ
What is an MCP architecture server?
An MCP (Model Context Protocol) architecture server exposes structured software-architecture data - services, edges, and metadata - to AI tools and agents in a standard way. Navo’s MCP server is backed by Git YAML as the source of truth.
Is MCP included in Navo Community?
Yes. The Community edition includes the MCP server along with the interactive graph, wiki reader, and AI YAML generator.
Keep architecture living next to code
Reduce architecture drift and meetings. Unlimited viewers free. Community includes MCP, AI YAML, and Git as source of truth.