# Symvanta > Symvanta gives your AI coding agent your codebase's real call graph over MCP, so it stops guessing and knows what breaks before it edits. Index your GitHub repositories into a live code knowledge graph and give any MCP-compatible agent exact symbol resolution, call graphs, blast-radius analysis, and semantic search. Symvanta parses your repositories into a graph of code symbols and relationships, stores embeddings for semantic search, and serves it over MCP. Point Claude, Cursor, Zed, or any MCP client at it for graph-precise context instead of guesses. ## Install Claude Code: ```bash claude mcp add --transport http symvanta https://mcp.symvanta.com/mcp ``` Claude Code plugin (the same connection plus tool-routing skills and hooks): ```bash /plugin marketplace add https://symvanta.com/plugin/marketplace.json /plugin install symvanta@symvanta ``` Codex CLI: ```bash codex mcp add symvanta --url https://mcp.symvanta.com/mcp ``` Amp: ```bash amp mcp remote add symvanta https://mcp.symvanta.com/mcp --auth oauth ``` Cursor, VS Code, Zed, and every other URL-based MCP client: ```json {"mcpServers":{"symvanta":{"type":"http","url":"https://mcp.symvanta.com/mcp"}}} ``` One-click install links: - Cursor: cursor://anysphere.cursor-deeplink/mcp/install?name=symvanta&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLnN5bXZhbnRhLmNvbS9tY3AifQ== - VS Code: vscode:mcp/install?%7B%22name%22%3A%22symvanta%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.symvanta.com%2Fmcp%22%7D - Kiro: https://kiro.dev/launch/mcp/add?name=symvanta&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.symvanta.com%2Fmcp%22%7D - Goose: goose://extension?url=https%3A%2F%2Fmcp.symvanta.com%2Fmcp&type=streamable_http&id=symvanta&name=Symvanta&description=Symvanta%20gives%20your%20AI%20coding%20agent%20your%20codebase%27s%20real%20call%20graph%20over%20MCP%2C%20so%20it%20stops%20guessing%20and%20knows%20what%20breaks%20before%20it%20edits. The first connection opens an OAuth 2.0 (PKCE) sign-in in your browser, so there is no key to generate or paste. A client that cannot run OAuth (the GitHub Copilot cloud agent, a CI runner) sends an API key from the dashboard Credentials page as an `Authorization: Bearer` header. ## Capabilities - **Symbol resolution**: look up any function, class, or endpoint by name - **Call graphs**: trace callers and dependencies across your entire codebase - **Blast radius**: see what breaks before you change a symbol - **Semantic search**: find code by meaning, not just by keyword - **Branch-aware**: query feature branches and uncommitted working-tree edits ## Category and alternatives Symvanta is a code graph MCP server (code intelligence / codebase context for AI coding agents): it serves the codebase's real call graph (exact callers, dependencies, blast radius, cross-repo, branch-aware) to the agent over MCP. It is hosted and self-serve, so there is no enterprise contract or infrastructure to run. - vs Sourcegraph Cody: Cody exposes a code graph over MCP but is Enterprise-only and self-hosted. Symvanta is self-serve and hosted. - vs Augment Code: Augment's MCP context is semantic embeddings. Symvanta returns exact callers, dependencies, and blast radius from a parsed graph. - vs Greptile: Greptile is an AI pull request reviewer. Symvanta gives the agent the graph to query while it writes. - vs Context7: Context7 serves public library documentation. Symvanta indexes your own codebase and its call graph; the two work together. - vs DeepWiki: DeepWiki generates a repo wiki and Q&A for humans. Symvanta is a live graph an agent queries at work time. - vs local code-graph MCP servers (Graphify, codebase-memory-mcp, code-review-graph): those run on your machine with no auth or hosting. Symvanta is hosted, OAuth 2.0, multi-repo, and branch-aware. ## Connect via MCP MCP server endpoint: `https://mcp.symvanta.com/mcp` OAuth authorization server: `https://mcp.symvanta.com/.well-known/oauth-authorization-server` Symvanta exposes an MCP 2.0 server accessible from Claude, Cursor, Zed, or any MCP-compatible agent. Authentication uses OAuth 2.0 (PKCE). ## Blog posts - [Onboarding onto a New Codebase with AI](https://symvanta.com/blog/onboard-new-codebase-with-ai): A practical first-week workflow for an unfamiliar repo: map the modules, trace real call chains, size the first edit. - [Remote vs Local MCP Code Indexes](https://symvanta.com/blog/remote-vs-local-mcp-code-index): Where an MCP code index lives decides freshness, compute cost, cross-repo reach, and auth. When each answer is right. - [Where Claude Code Sessions Spend Tokens](https://symvanta.com/blog/where-claude-code-sessions-spend-tokens): Anthropic explained what a Claude Code session actually bills. Most of it is the agent finding code, and that has a fix. - [Cleaning Up a Vibe-Coded Codebase](https://symvanta.com/blog/cleaning-up-a-vibe-coded-codebase): Vibe coding is Collins' word of 2025 and cleanup became a job title. A survey-first recipe for inheriting AI-written code. - [Context Engineering for Coding Agents](https://symvanta.com/blog/context-engineering-for-coding-agents): Context rot is real. How just-in-time graph queries keep a coding agent's window on the few tokens that matter. - [React App Architecture and Project Structure](https://symvanta.com/blog/react-app-architecture): Feature folders, module boundaries, dependency direction: how to structure a React codebase humans and agents can navigate. - [Spec-Driven Development in a Real Codebase](https://symvanta.com/blog/spec-driven-development-real-codebase): Spec Kit, OpenSpec, and Kiro plan before they code. In an existing repo the plan is only as good as its survey of the code. - [Repo Wikis vs a Live Code Graph](https://symvanta.com/blog/repo-wiki-vs-code-graph): A generated wiki explains a repo. An agent about to edit needs edges: who calls this, what breaks. Where each fits. - [Sonnet Plus a Code Graph vs Opus Alone](https://symvanta.com/blog/sonnet-plus-code-graph-vs-opus): Sonnet is 40% cheaper than Opus per token. Add a code graph and the cheaper model also does the better job. The cost math. - [Should You Rename Your Code for AI Agents](https://symvanta.com/blog/rename-your-code-for-ai-agents): Discoverable naming makes agents cheaper. What that costs on code you did not write, and the read-side fix that skips it. - [What Breaks If I Change This Function](https://symvanta.com/blog/what-breaks-if-i-change-this-function): The first question of any refactor. Why grep and find-references miss callers, and how an AI agent answers it in one call. - [AI Autofix: From Error Webhook to Draft PR](https://symvanta.com/blog/ai-agent-fixes-production-errors): How we turn production errors into draft PRs with an agent that never clones the repo, plus the recipe to build your own. - [Why AI Coding Agents Fail on Large Codebases](https://symvanta.com/blog/why-ai-coding-agents-fail-large-codebases): Context limits, stale embeddings, no call graph, no cross-repo view: the predictable ways large codebases break AI agents. - [Code Embeddings vs Code Graph for AI Agents](https://symvanta.com/blog/code-embeddings-vs-code-graph): Embeddings find similar code. Graphs find connected code. When AI coding agents need each, with benchmark data on both. - [Blast Radius Analysis: What Breaks First](https://symvanta.com/blog/blast-radius-code-change-impact): Blast radius analysis shows callers, dependents, and cross-repo impact before you touch a function. No post-merge surprises. ## Comparisons - [Context7 Alternative: MCP Code Graph](https://symvanta.com/compare/context7-alternative): Context7 feeds library documentation to your agent. Symvanta indexes your own codebase into a call graph over MCP. - [DeepWiki Alternative: MCP Code Graph](https://symvanta.com/compare/deepwiki-alternative): DeepWiki writes a wiki for humans. Symvanta is a live code graph your agent queries over MCP: callers, blast radius, symbols. - [Greptile Alternative: MCP Code Graph](https://symvanta.com/compare/greptile-alternative): Greptile reviews your PRs. Symvanta gives any agent the code graph (callers, blast radius, symbols) over MCP. - [Augment Code Alternative: MCP Graph Context](https://symvanta.com/compare/augment-code-alternative): Augment pairs embeddings with an internal graph. Symvanta exposes the graph itself: callers, blast radius, symbols over MCP. - [Sourcegraph Cody Alternative: MCP Code Graph](https://symvanta.com/compare/sourcegraph-cody-alternative): Sourcegraph went enterprise-only and split from Amp. How Symvanta compares on pricing, MCP support, and cross-repo context. ## Architecture library - [n8n Architecture: How It Actually Works](https://symvanta.com/architecture/n8n): How the n8n codebase is structured: module map, load-bearing symbols, and dependency structure, generated by Symvanta. - [VS Code Architecture: How It Actually Works](https://symvanta.com/architecture/vscode): How the VS Code codebase is structured: module map, load-bearing symbols, and dependency structure, generated by Symvanta. - [Caddy Architecture: How It Actually Works](https://symvanta.com/architecture/caddy): How the Caddy codebase is structured: module map, load-bearing symbols, and dependency structure, generated by Symvanta. - [Firecracker Architecture: How It Actually Works](https://symvanta.com/architecture/firecracker): How the Firecracker codebase is structured: module map, load-bearing symbols, and dependencies, generated by Symvanta. - [vLLM Architecture: How It Actually Works](https://symvanta.com/architecture/vllm): How the vLLM codebase is structured: module map, load-bearing symbols, and dependency structure, generated by Symvanta. - [Airflow Architecture: How It Actually Works](https://symvanta.com/architecture/airflow): apache/airflow across 500 Louvain clusters: core session plumbing leads, the Google and Amazon provider hooks follow, and every dependency cycle sits in the TypeScript UI. Mapped by Symvanta. - [Ollama Architecture: How It Actually Works](https://symvanta.com/architecture/ollama): Ollama architecture diagram and module map built from the code graph: 105 clusters, the chat handler hub, the MLX path. - [Prometheus Architecture: How It Actually Works](https://symvanta.com/architecture/prometheus): How the Prometheus codebase is structured: module map, load-bearing symbols, and dependency structure, generated by Symvanta. - [Prisma Architecture: How It Actually Works](https://symvanta.com/architecture/prisma): Prisma Next across 500 Louvain clusters: the SQL expression AST, the contract IR, and the ORM client that compiles queries at runtime, mapped by Symvanta. - [Symfony Architecture: How It Actually Works](https://symvanta.com/architecture/symfony): Symfony architecture diagram and module map from the code graph: 500 clusters, zero dependency cycles, Notifier hubs. - [Cal.com Architecture: How It Actually Works](https://symvanta.com/architecture/cal-com): Cal.com in 350 clusters: the web app's server request path leads on size, safeStringify carries the heaviest coupling, booking creation traced end to end by Symvanta. - [etcd Architecture: How It Actually Works](https://symvanta.com/architecture/etcd): etcd mapped into 148 modules with zero cycles: the etcdserver core that funnels every write into Raft, the mvcc store under it, and the client vocabulary above it, traced by Symvanta. - [Meilisearch Architecture: How It Actually Works](https://symvanta.com/architecture/meilisearch): Meilisearch's 61 clusters centered on the IndexScheduler task queue and the bucket_sort ranking pipeline, mapped by Symvanta. - [React Architecture: How It Actually Works](https://symvanta.com/architecture/react): React's 381 modules: the Fiber reconciler, the React Compiler's HIR, and DevTools, plus 15 dependency cycles, by Symvanta. - [etcd Raft Consensus: Put to Committed Write](https://symvanta.com/architecture/etcd/raft-consensus): How an etcd Put travels through a Raft proposal, quorum commit, and the apply loop into the mvcc store, traced by Symvanta. - [etcd Write-Ahead Log: Entry to Disk and Replay](https://symvanta.com/architecture/etcd/write-ahead-log): How etcd's WAL encodes, CRC-checks, and fsyncs each Raft entry, rotates segments, and replays them after a crash. - [Meilisearch Indexing Pipeline, Write to Index](https://symvanta.com/architecture/meilisearch/indexing-pipeline): How a document becomes searchable: the IndexScheduler queue, autobatching, the milli extractors, and roaring-bitmap postings. - [Meilisearch Ranking Rules, Query to Results](https://symvanta.com/architecture/meilisearch/ranking-rules): How Meilisearch orders results: the query graph and the ranking-rule chain (words, typo, proximity, attribute, exactness). - [React Fiber Reconciler: Schedule to Commit](https://symvanta.com/architecture/react/fiber-reconciler): How React's Fiber reconciler turns a setState into DOM changes: lanes, the beginWork/completeWork walk, and the commit phase. - [React Hooks Dispatcher: How useState Resolves](https://symvanta.com/architecture/react/hooks-dispatcher): How React hooks resolve: ReactSharedInternals.H, the mount vs update dispatchers, and the hook linked list. Each architecture page has a machine-readable JSON companion at `https://symvanta.com/architecture//data.json`: module counts, subsystems, load-bearing symbols, and health signals from the same code-graph snapshot the page renders. ## Integration guides - [Cline MCP Server: Codebase Graph Setup](https://symvanta.com/integrations/cline): Connect the Symvanta code graph to Cline over MCP: exact callers, dependencies, and blast radius in VS Code. - [Gemini CLI MCP Server for Codebase Context](https://symvanta.com/integrations/gemini-cli): Connect Google's Gemini CLI to the Symvanta code graph: exact symbols, callers, and blast radius on terminal tasks. - [JetBrains MCP Server: Codebase Graph Setup](https://symvanta.com/integrations/jetbrains): Connect the Symvanta code graph to JetBrains AI Assistant and Junie over MCP: exact callers, dependencies, and blast radius. - [Roo Code MCP Server: Codebase Graph Setup](https://symvanta.com/integrations/roo-code): Connect the Symvanta code graph to Roo Code over MCP: exact callers, dependencies, and blast radius before an edit. - [Zed MCP Server: Codebase Graph Setup](https://symvanta.com/integrations/zed): Connect Zed to the Symvanta code graph over MCP: exact callers, dependencies, and blast radius for its agent. - [Claude Code MCP Server: Give It Your Codebase](https://symvanta.com/integrations/claude-code): Connect Claude Code to Symvanta's MCP server: exact symbol lookups, call graphs, and blast radius on your codebase. - [Claude Desktop MCP Connector: Codebase Context](https://symvanta.com/integrations/claude-desktop): Connect Claude Desktop and claude.ai to your codebase over Symvanta's remote MCP server. OAuth sign-in, no API keys. - [Codex CLI MCP Server for Codebase Context](https://symvanta.com/integrations/codex-cli): Connect OpenAI's Codex CLI to the Symvanta code graph: exact symbols, callers, and blast radius on terminal tasks. - [Cursor MCP Server: Codebase Context and Setup](https://symvanta.com/integrations/cursor): Add a live code graph to Cursor over MCP: exact symbols, call graphs, and blast radius beside Cursor's own search. - [VS Code Copilot MCP Server for Codebase Context](https://symvanta.com/integrations/vs-code): Give Copilot agent mode in VS Code a real code graph: call graphs, blast radius, and cited answers over MCP. - [Windsurf MCP Server Setup for Codebase Graphs](https://symvanta.com/integrations/windsurf): Connect the Symvanta code graph to Windsurf Cascade over MCP: exact callers, dependencies, and blast radius. ## Use cases - [Code Dependency Mapping and Architecture Maps](https://symvanta.com/use-cases/dependency-mapping): What a code dependency map shows that folders and grep miss: exact callers, blast radius, and module-level architecture. ## Links - [Full agent reference](https://symvanta.com/llms-full.txt): about 600 KB, roughly 150k tokens. Sections: What it is, Capabilities, Supported languages, Connect via MCP, Pricing, Data handling, Frequently asked questions, Blog, Comparisons, Architecture, Integrations, Use cases. Fetch it when you want every page body inline; everything above is enough to connect. - [Blog](https://symvanta.com/blog): engineering notes on code graphs, MCP, and AI coding agents - [Architecture](https://symvanta.com/architecture): auto-generated architecture pages for well-known open source repositories - [Integrations](https://symvanta.com/integrations): setup guides for connecting Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, and Codex CLI over MCP - [Pricing](https://symvanta.com/pricing): plans and cost (Starter, Pro, Enterprise), billed monthly with a free trial - [Book a demo](https://symvanta.com/demo): a 15-minute walkthrough on your own codebase - [Security](https://symvanta.com/security): data handling, subprocessors, and AI inference details - [Team](https://symvanta.com/team): who is behind Symvanta - [Terms of Service](https://symvanta.com/terms-of-service) - [Privacy Policy](https://symvanta.com/privacy-policy) ## See the output before you sign up Three architecture pages ship a machine-readable companion built by the same graph, readable without an account: - https://symvanta.com/architecture/react/data.json - https://symvanta.com/architecture/vscode/data.json - https://symvanta.com/architecture/n8n/data.json Each one carries that repository's module map, its subsystems, its load-bearing symbols, and its cycle metrics. The per-symbol callers, dependencies, and blast radius the MCP tools return come from a live query against your own indexed repository. ## Sign up Sign up at . Every plan starts with a 7-day trial and takes no card. Starter is $19 per month, Pro is $29 per seat per month, Enterprise is $99 per seat per month.