Log inSubmit server
Agentmap logo

Agentmap

Maps TypeScript and JavaScript repositories for coding agents with eight MCP query tools and compiler-resolved dependency results.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Agentmap

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "agentmap": {
      "command": "npx",
      "args": [
        "-y",
        "@raymondchins/agentmap"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @raymondchins/agentmap

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 9d ago.

Overview

The agentmap MCP server builds a TypeScript/JavaScript import and symbol graph for repository navigation. It exposes eight MCP query tools alongside CLI queries for finding symbols, tracing dependents, mapping repositories, and routing requests automatically. ts-morph resolves compiler configuration, path aliases, package subpaths, and monorepo workspaces instead of relying on text matches. Reach for it when an agent needs focused repository context or an accurate change-impact view without sending whole files to the model.

Use cases

  • Find an existing helper before writing new code
  • Trace files affected by a dependency change
  • Locate the source definition of a symbol
  • Generate a token-bounded repository map
  • Refresh repository context after commits

Key features

  • TypeScript compiler-based import and symbol graph
  • Eight MCP query tools
  • Symbol, dependency, map, and automatic queries
  • Resolution for aliases and monorepo workspaces
  • Cached local repository maps
  • Post-commit rebuild and agent guidance hooks

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

Not checked yetLast checked Today

We have not completed a health check for this listing yet.

7/15 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @raymondchins/agentmap (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars50Stargazers on the source repository.
npm downloads464Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Agentmap works

What agentmap does

The agentmap MCP server gives coding agents a queryable map of a TypeScript or JavaScript repository. Its graph connects files and symbols through resolved imports and definitions, allowing an agent to ask targeted repository-navigation questions instead of reading broad file lists or dumping the project into context. Vue single-file components are also supported.

The package is aimed at tasks such as locating an existing helper, finding the file that defines a symbol, identifying files affected by a change, and producing a ranked repository digest under a token budget.

How it works

agentmap uses ts-morph, which relies on the TypeScript compiler rather than text matching. The graph can account for tsconfig path mappings, Vite and webpack aliases, #imports subpaths, and monorepo workspaces. It also follows re-export chains to identify the file that actually declares a symbol.

The CLI provides five query modes: --find for symbols or existing functionality, --relates for a file's dependents and change impact, --map for a ranked repository digest, --any for automatic query routing, and the default map command for repository status. A personalized PageRank ranking is applied across file and symbol graphs. The command-line examples report an approximately 1.2-second cold build and approximately 0.1-second cached query, though timings depend on the repository and environment.

The agentmap MCP server operates locally. A cache is stored at .claude/agentmap/map.json; cached results are used for a clean tree at the same HEAD, while uncommitted supported-language edits trigger a rebuild.

Setup and configuration

Run the scoped npm package with Node.js 20 or newer:

Terminal
npx @raymondchins/agentmap --relates path/to/file.ts

The scoped package name matters because the unscoped agentmap name refers to another package. From a repository checkout, commands can also be run with node agentmap.mjs.

For automatic maintenance and agent guidance, run:

Terminal
npx @raymondchins/agentmap --install-hooks
npx @raymondchins/agentmap --install-skill

The hooks rebuild the map after commits, while the skill installation is documented for Claude Code, Cursor, Codex, Gemini, OpenCode, and Copilot.

Tools and capabilities

The agentmap MCP server and CLI support these grounded capabilities:

  • Search for a symbol or existing helper with --find.
  • Trace files that depend on a selected file with --relates.
  • Generate a ranked repository map with --map and an optional --tokens N budget.
  • Route an arbitrary request with --any.
  • Report repository graph information, including file counts, feature counts, and a top hub.
  • Detect unresolved-import health through an edgeCoverage signal and warnings.

Limitations and notes

Coverage is limited to TypeScript, JavaScript, and Vue SFC repositories. A small, single-file lookup may cost more than direct cat and grep, so the tool is not automatically cheaper for every query. Its published token figures are estimates based on character counts divided by four, and describe context-token volume rather than answer quality or elapsed time.

--relates returns the complete dependent set, which can be longer than a simple filename list. That trades shorter output for dependency precision. Results also depend on imports resolving correctly; the tool reports map health rather than silently treating an incomplete graph as reliable.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Agentmap

agentmap is an MCP server that connects coding agents to local TypeScript and JavaScript repositories through an import and symbol graph. Its main tools support finding symbols, tracing file dependents, generating ranked repository maps, and routing arbitrary queries, with eight MCP query tools described by the project.

Install it with the scoped npm command `npx @raymondchins/agentmap`; Node.js 20 or newer is required. Run `--install-hooks` to rebuild after commits and `--install-skill` to add the documented agent guidance for supported clients.

Yes, Cursor is one of the clients named for the `--install-skill` setup.

It supports TypeScript and JavaScript, including Vue single-file components.

No, it requires neither an API key nor network access.

Related MCP servers

All in Coding Agents All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAgentmap AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/agentmap?style=directory)](https://allmcps.com/mcp/agentmap)
HTML Embed
<a href="https://allmcps.com/mcp/agentmap"><img src="https://allmcps.com/api/badge/agentmap?style=directory" alt="Agentmap on AllMCPs" /></a>