Server data from the Official MCP Registry
Internal dependency map for monorepo packages, as structured data and a Mermaid graph.
About
Internal dependency map for monorepo packages, as structured data and a Mermaid graph.
Security Report
depmap is a pure local monorepo dependency mapper with no network calls, no shell or eval usage, no credentials, and no filesystem access beyond the user-supplied input file. Its permissions (file_read for the CLI input, stdio MCP transport) match its stated purpose, and the code has strict input validation with path-naming errors. No meaningful security findings were identified. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.
8 files analyzed · 4 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-cloudcorprecords-depmap": {
"args": [
"-y",
"@reneturcios/depmap"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
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 --version
args.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.
MCP server
npx -y @reneturcios/depmap mcp
MCP 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.json
Development
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 source
License
MIT — Copyright (c) 2026 Rene Turcios
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
