depmap
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
depmap
A monorepo is easy to lose track of: which packages actually depend on which other packages in the set, what sits at the top with nothing depending on it, what sits at the bottom depending on nothing internal, and whether the internal graph loops back on itself. depmap takes the package graph — every package's name and the names it depends on — and draws the whole map:
Per-package entries — for every package, its internal dependencies (
depends_on), the packages that depend on it (depended_by), andexternal_count: how many of its dependency names point outside the set. External names are counted, never mapped, and never an error — a package may freely depend on libraries the monorepo does not contain.Edges, roots, and leaves — every internal dependency as a
{from, to}edge, the roots (packages nothing internal depends on), and the leaves (packages with no internal dependencies).Cycles, two ways —
cyclic_packageslists every package that lies on any cycle: members of a strongly connected component of more than one package, plus any package that depends on itself. Alongside it,cyclereports one concrete cycle, found by a depth-first search that visits names and dependencies in ascending order. A cycle is a finding, not an error.A Mermaid graph — the map rendered as a
graph TDdiagram you can paste into any Mermaid renderer. Package names that are not valid Mermaid ids get a sanitised id (@scope/appbecomes_scope_app) with a declaration line tying the id back to the real name.
Duplicate entries in one package's dependencies are
de-duplicated before mapping, and every list in the result
is sorted ascending, so the same graph always yields
exactly the same map. Malformed input — a missing or empty
package list, a missing or duplicate package name, a
wrongly typed field — is a validation error naming the
offending path (for example
packages[1].dependencies[0] must be a string), and no
partial map is produced. The computation is pure and
local: no network, no configuration, no files read beyond
the input you pass in.
CLI
npx @reneturcios/depmap map --input args.json
npx @reneturcios/depmap --versionargs.json contains the full arguments object:
{
"packages": [
{ "name": "core" },
{ "name": "lib", "dependencies": ["core"] },
{ "name": "app", "dependencies": ["lib", "react"] }
]
}dependencies defaults to [] per package; here react
is external to the set, so it appears only in app's
external_count. The map is printed as JSON:
{
"packages": [
{ "name": "app", "depends_on": ["lib"], "depended_by": [], "external_count": 1 },
{ "name": "core", "depends_on": [], "depended_by": ["lib"], "external_count": 0 },
{ "name": "lib", "depends_on": ["core"], "depended_by": ["app"], "external_count": 0 }
],
"edges": [
{ "from": "app", "to": "lib" },
{ "from": "lib", "to": "core" }
],
"roots": ["app"],
"leaves": ["core"],
"has_cycle": false,
"cycle": [],
"cyclic_packages": [],
"mermaid": "graph TD\n app --> lib\n lib --> core"
}Exit codes: 0 on success, 1 on a runtime error (including
an unreadable or invalid input file, or invalid input), 2
on a usage error.
Related MCP server: genpark-monorepo-dependency-cycle-detector-skill
MCP server
npx -y @reneturcios/depmap mcpMCP client config:
{
"mcpServers": {
"depmap": {
"command": "npx",
"args": ["-y", "@reneturcios/depmap", "mcp"]
}
}
}Tools
map_internal_dependencies— Map a monorepo's internal dependencies.packages(array, required, at least one) — packages as{name, dependencies?}objects;nameis unique across the set, and eachdependenciesentry either names another supplied package (internal) or anything else (external, counted only)
Returns
{packages, edges, roots, leaves, has_cycle, cycle, cyclic_packages, mermaid}.
Docker
docker run -i ghcr.io/cloudcorprecords/depmap
docker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/depmap map --input /w/args.jsonDevelopment
npm install
npm run build # tsc -> dist/
npm test # tsx --test test/*.test.ts (pure local, no network)
npm run dev # run the CLI from sourceLicense
MIT — Copyright (c) 2026 Rene Turcios
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Generate SBOMs, scan vulnerabilities, and analyze dependencies from local projects or Git repos.
Dev-registry data: npm/PyPI/Docker/VS Code packages, dep graphs, vulns, 50+ ecosystems.
Scan packages and lockfiles (npm, PyPI, Go, Maven, Cargo, NuGet) for vulnerabilities and malware.
Package versions, licences and known vulnerabilities for npm, PyPI, crates, Go, Maven, NuGet
Related MCP Servers
- AlicenseAqualityDmaintenanceIndexes a mono-repo into a knowledge graph and provides MCP tools to query code structure—packages, components, routes, HTTP calls—without file reads or grep round-trips.722 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables coding agents to analyze monorepo dependency graphs, detect and resolve circular dependencies, and plan a topological build order via Tarjan SCC and Kahn algorithms. It exposes deterministic, zero-dependency Python AST static analysis over MCP for auditing and refactoring codebases.7-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables coding agents to analyze Python source with AST-based static analysis, detect circular dependencies across monorepo packages via Tarjan SCC, and produce a topological build order with Kahn's algorithm along with refactoring plans and graph metrics. Runs with zero external dependencies over MCP from Claude Desktop, Cursor, or any compliant client.-
- AlicenseNot gradedqualityBmaintenanceEnables mapping a dependency graph of jobs or tests to reveal parallelizable levels, sequential versus parallel time, critical path, cycle detection, and optional greedy worker schedules.64 npmMIT