Give your coding agent your architecture.
UIGraph MCP is the local stdio handoff between your coding agent and the graph your repository keeps current.
npm i -g @uigraph/mcpOne process. Your client’s native format.
Choose your agent, then use its initializer or paste the matching configuration. Replace the cloud URL with your own MCP server URL when self-hosting.
Cursor
Add the server to your project, then restart Cursor.
Quick setup
uigraph-mcp init cursor.cursor/mcp.json
{
"mcpServers": {
"uigraph": {
"command": "uigraph-mcp",
"env": {
"UIGRAPH_MCP_SERVER_URL": "https://mcp.uigraph.app"
}
}
}
}
See what crosses the local boundary.
Services, owners, endpoints, dependencies, screens, and focal points come from the graph — not inferred from file names.
> which screens and focal points are in the checkout map?
tools/call → get_map({ slug: "checkout" })
6 frames · 2 focal points
Payment → payments-service
Confirmation → orders-service
✓ answered from the graph
Authenticate as the person or system doing the work.
A user login stays in your OS keychain. Automation uses a service-account token in the environment. Choose the identity that matches where the agent runs.
Personal machine
Use your login.
Open browser sign-in once. The proxy stores the credentials in your OS keychain.
uigraph-mcp auth loginShared machine or CI
Use a service account.
Access belongs to the team instead of depending on one person’s account.
UIGRAPH_ACCESS_TOKEN=uig_…Keep the graph current. Put it to work.
The CLI builds the graph from your repository. MCP makes that context available inside the coding agent.
Frequently asked questions
Installation, compatibility, access, and the graph MCP reads.
Read the docsGive your agent the map.
One local process turns current architecture into context your coding agent can query.