ArchGraph
Give your coding agent structured architecture maps, security signals, and change-impact context across a repo before refactors or reviews.
Overview
ArchGraph is a MCP server for the Ship phase that exposes 20 tools for architecture, security, and change-impact analysis on your codebase via a hosted remote endpoint.
What is this MCP server?
- 20 MCP tools for architecture, security, and impact analysis in one remote server
- Streamable HTTP remote at mcp.archgraph.dev with Bearer API key auth
- Purpose-built code intelligence layer for AI agents working in real repositories
- Supports security-focused queries alongside structural and dependency insight
- Hosted gateway (archgraph-gateway) with dashboard key management at archgraph.dev
- 20 MCP tools documented for architecture, security, and impact analysis
- Server version 1.0.0 per MCP registry metadata
- Remote endpoint: https://mcp.archgraph.dev/mcp (streamable-http)
What problem does it solve?
Agents refactor and review code without reliable maps of dependencies, security hotspots, or what else will break when a file changes.
Who is it for?
Indie builders with an existing codebase who want agent-driven refactors, security checks, and impact analysis without wiring many one-off tools.
Skip if: Greenfield projects with no code yet, or teams that only need lightweight doc lookup without structural analysis.
What do I get? / Deliverables
Your agent can query structured architecture and impact intelligence so edits and reviews are grounded in the real graph of the repo.
- Agent-callable architecture, security, and impact insights across the codebase
- Repeatable review context without custom scripts per analysis type
- Remote MCP registration pointing at mcp.archgraph.dev
Recommended MCP Servers
Journey fit
ArchGraph shines when the product already exists and you need safer edits—impact and security analysis sit naturally in ship’s review and hardening loop. Code review and pre-merge reasoning are where 20 architecture and security tools prevent agents from guessing module boundaries.
How it compares
Code-intelligence MCP with 20 analysis tools, not a generic filesystem or single-linter integration.
Common Questions / FAQ
Who is dev.archgraph/mcp for?
Solo and small-team builders using AI coding agents who need architecture, security, and impact analysis on an existing repository.
When should I use dev.archgraph/mcp?
Use it during code review, refactors, and pre-ship hardening when you want agents to reason about structure and blast radius instead of guessing.
How do I add dev.archgraph/mcp to my agent?
Create an API key at archgraph.dev/dashboard/keys, add the streamable-http remote https://mcp.archgraph.dev/mcp with Authorization Bearer ag_YOUR_KEY, then enable the server in Claude Code, Cursor, or another MCP client.