Use Cases

Where CodeAtlas
earns its keep.

Five concrete jobs CodeAtlas does well today · architectural PR reviews, AI Code Review, MCP-powered AI assistants, API testing without Postman, and onboarding new contributors. All on a single live snapshot of your codebase.

Where it works.

11 languages & 40+ frameworks, plus mobile stacks and infrastructure-as-code.

JS / TypeScript

Express, Koa, Fastify, NestJS, Hono, Next.js, Nuxt, Remix, tRPC

Python

FastAPI, Django, Flask, Starlette, DRF

Java & Kotlin

Spring Boot, Micronaut, Ktor, JAX-RS

Go

Gin, Echo, Chi, Fiber

Rust

Actix, Axum, Rocket

PHP & Ruby

Laravel, Symfony, Rails, Sinatra

C# & Swift

ASP.NET, Minimal API, Vapor

Mobile & IaC

SwiftUI, Jetpack Compose, Flutter, React Native, AWS SAM/CDK, Serverless

Five jobs, live today.

01 / Architectural PR reviews

Review the architecture, not just the lines.

Open a PR. CodeAtlas paints a diff onto every diagram layer · added nodes in green, removed in red dashed, modified in amber. The same diff lives in the API surface, the sequence diagrams, the file graphs, and the system-design view, so a single PR shows its full architectural footprint.

  • Visual diffs across all six layers
  • API contract surface diff catches breaking changes
  • Architecture violations on the diagram where they live
Diff overlay across all six diagram layers
L1 System Design · diff vs main
LegacyAuthRemoved
OAuth2LayerAdded
AI Review · cluster:auth
3 high
JWT_SECRET fallback to empty string
process.env.JWT_SECRET || ''
auth.service.ts:24 · POST /api/users/login
N+1 query in feed loader
for (const a of articles) await getAuthor(a.id)
article.service.ts:88 · GET /api/articles/feed
Auth missing on PUT /user
auth.controller.ts:42 · PUT /api/user
Every finding quotes the actual source.3 / 3 evidence-gated
02 / AI Code Review

AI review you can actually trust.

Every finding quotes a verbatim line from your code. If the model invents an issue, the quote won't match your source and the finding gets filtered out before you see it. Auth issues land on the API row, N+1 queries on the sequence diagram, dead code on the file view · exactly where the fix lives.

  • Per-entry-point review · no hallucinated cross-refs
  • Your team's rules in plain text · up to 8 KB
  • OpenAI, Anthropic, OpenRouter, Ollama (local, no key)
03 / AI assistants with structure

Stop your assistant from grepping files.

npm install --save-dev @codeatlas/mcp auto-wires Claude Code, Cursor, Codex CLI, Gemini CLI, VS Code Copilot Chat, and Continue. Your assistant gets 51 structured tools · list routes, trace call paths, run SQL over the snapshot, get impact analysis · in tokens, not file-walks.

  • Zero-config install · daemon + configs in one command
  • Read-only SQL access · deterministic, no LLM in the loop
  • 5×–200× fewer tokens per architectural question
claude code · session
you → what HTTP routes touch the User table?
claude → calling codeatlas:query_snapshot…
SELECT method, path, handler FROM apis WHERE handler IN (SELECT caller FROM call_edges WHERE callee LIKE '%User%') ORDER BY method;
claude → 6 routes touch User:
GET /api/user
GET /api/profiles/:username
POST /api/users
POST /api/users/login
PUT /api/user
DELETE /api/profiles/:username/follow
68 tokens · 208× cheaper than file-walking
API Testing · chain runnerpassed
1.POST/api/users/login200
2.GET/api/user200
3.POST/api/articles201
4.PUT/api/articles/{{slug}}/favorite200
4 steps · env carried across · pre/post scripts in pm.* sandbox
04 / API testing, built in

Skip Postman. Test what you just shipped.

Every detected route shows up in the workbench · auto-derived, no JSON collection to maintain. Send, chain, script (Postman-style pm.* sandbox), OAuth2, SSE, WebSocket. Drop in your existing OpenAPI / Postman / Insomnia collections and they auto-merge.

  • Chain runner with extraction recipes + assertions
  • OAuth2 callback receiver baked in
  • AI-generated request bodies + test cases · evidence-gated
05 / Onboarding new contributors

Day-one mental model in one afternoon.

The guided Tour orders the routes a new contributor should learn first, fan-in ranked so tests, migrations, seeds, and library internals don't lead. The Knowledge Map distills the workspace into a navigable bird's-eye view of features, files, and tour stops. New hires get the map a senior engineer carries in their head · on day one.

  • Knowledge Map · domain + cluster + route overview
  • Tour · ranked walkthrough with “why this matters” blurbs
  • “Recent” mode highlights what changed since your last visit
Tour · codebase mode5 of 12
1
POST /api/users/login
Highest fan-in entry point. Start here.
2
GET /api/articles/feed
The main read path. 8 callers.
3
POST /api/articles
The main write path.
4
PUT /api/articles/:slug
Update path · auth required.
5
auth.service.ts::getCurrentUser
Cross-cutting · called by 12 routes.
here
← prevfan-in ranked · tests / migrations excludednext →

One install. Every editor.

Extensions for VS Code, Cursor, Windsurf, Antigravity. npm MCP standalone for Claude Code, Codex, Gemini, Continue, Copilot. Same engine.