Skip to main content

Install

Requirements: Node.js >= 24.

npm install
npm run build

This produces dist/mcp/index.js — the stdio MCP server entry point.

:::caution Distribution channel not finalized This section documents the source build (clone → npm install → npm run build), which is what's confirmed working today. A packaged distribution (npm package, container image, or GitHub release) is not yet decided — this page will be updated once it is. Don't build tooling against an assumed package name or image tag; none is official yet. :::

Add it to your MCP client​

Point it at the workspace root directory that contains your sibling repos as immediate subdirectories:

{
  "mcpServers": {
    "crossrepo-graph": {
      "command": "node",
      "args": ["/absolute/path/to/crossrepo-graph/dist/mcp/index.js", "/absolute/path/to/your-workspace"]
    }
  }
}

The workspace root is a required positional argument — the server fails fast with a clear error if it's missing or not a directory, rather than starting silently and failing later once a tool is called.

Restarting after an update​

If you already have a connected MCP session open when Desnarl's code changes (a version upgrade, a config change), restart that session's connection — not just the server process — to pick up any change in tool shape.

Next​

  • Self-hosted deployment — ingestion auth, the network-queryable CI endpoint, staleness monitoring, and storage.
  • MCP tool reference — what crossrepo_impact, crossrepo_consumers, and crossrepo_schema_refs actually return.