Agentmap MCP server

Read from the package source without running it. The installed server may list more.

• affected

  Which test files cover a source file, following import edges transitively — and, just as usefully, whether ANY do. Answers 'what do I re-run after changing this' before the edit, not after CI. Walks runtime AND type-only edges, so a file imported only via `import type` still reports its covering tests. An empty list is the ANSWER (nothing covers this file), not a lookup failure.

• any

  Unified router: resolve a query against the repo map (file → symbol → feature) then fall back to a live git-grep for string/copy/data literals. Best default for 'where is X' / reuse-before-rebuild.

• callers

  Compiler-accurate call graph: every call site that INVOKES a symbol, resolved by the TypeScript language service (not tree-sitter name-matching) — so a type-position mention, a re-export, or a same-named local in another file is never mis-attributed. Symbol-level blast radius: 'who breaks if I change this function'. A deliberate DEEP query — the first call warms the TS type-checker (seconds on a l

• calls

  Compiler-accurate OUTGOING call graph: every in-project symbol that a given symbol INVOKES, resolved by the TypeScript language service (not tree-sitter name-matching) — callee resolution follows real bindings (imports/re-exports) through to the actual declaration. Answers 'what does this function call / depend on'. node_modules and TS built-ins are excluded; dynamic dispatch and higher-order indi

• feature

  List all files belonging to a named feature plus its external dependents.

• features

  List every detected feature (top-level app/ route segment) with its file count.

• find

  Find every symbol whose name matches (substring, case-insensitive) — exported symbols plus non-exported top-level declarations. Use to locate a function/class/type before rebuilding it. A match reached through a re-export barrel carries `definedIn` — the file that actually declares it, resolved by the TypeScript checker through any number of barrel hops — or `external: true` when the origin is out

• hubs

  List the most important files in the repo by PageRank (the hubs everything imports). Read these first to understand a codebase.

• map

  Token-budgeted ranked digest of the codebase (PageRank + Aider-style symbol ranking). Optionally focus toward a file and/or set a token budget.

• relates

  Blast radius for a file: its exports, imports, direct dependents, and the files most related to it by random-walk relevance. Use before editing to see who breaks. `dependents` means 'breaks at RUNTIME'; files that depend on this one only through `import type` are listed separately as `typeOnlyDependents` — they break at COMPILE time when an export is renamed or removed, so check both before a rena

• route

  Resolve one URL path (e.g. '/dashboard/settings') to the files that serve it, including the layouts it nests under. Use to go from a bug report naming a URL straight to the code. Next.js App Router only.

• routes

  The Next.js App Router route table: every URL path the repo serves, with the file that serves it. Next.js only — on any other repo this returns an explicit `reason` rather than an empty list.

• search

  Rank symbols by BM25 lexical relevance for a VAGUE natural-language query (e.g. 'where's the auth retry logic', 'the function that dedupes symbols') — where exact `find`/`any` name matching fails. Tokenizes symbol names + path segments + feature + kind, scored by BM25 and fused with file PageRank. Best when you don't know the exact symbol name.

• symbols

  Top N globally ranked symbols (Aider-style importance). Defaults to 30.

• Code scan13 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityno repository or website to verify2/10

Safety score

65/100

higher than 20% of 679 Maps and travel servers

Tools

14

the typical Maps and travel server has 6

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

48

more than 95% of 333 Maps and travel servers

Downloads a week

658

more than 95% of 198 Maps and travel servers with a package

Grade history

• 2026-11-04downgradeA → Cscore 65

Agentmap: common questions

Is Agentmap MCP server safe?

With care: it is graded C, so read the findings first (65/100). Read the Agentmap safety report

How do I install Agentmap?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Agentmap need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Agentmap maintained?

The last commit was 57 days ago (2026-09-19). The latest release is v0.22.0.

What can I use instead of Agentmap?

Servers from other publishers that do the same job: Repo Graph MCP server, Osnova MCP server and Infranodus Infranodus MCP server.

How does Agentmap compare with other Maps and travel MCP servers?

safety score 65/100 (higher than 20% of 679 Maps and travel servers); tools 14 (the typical Maps and travel server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.