Bridge DeepGraph Connector

Bridge Claude Code to DeepGraph analysis services for cross-repository code intelligence, enabling architectural comparisons and dependency tracking across multiple projects.

When to Use This MCP Server

Connect this server when you need to:

• Compare architectural patterns and dependency structures across multiple repositories or microservices in a distributed system
• Track cross-repository dependencies where one project imports packages or APIs from another, mapping the full dependency chain
• Generate organization-wide code metrics and architectural reports spanning multiple codebases simultaneously

Consider alternatives when:

• You are analyzing a single repository where a standard DeepGraph provider or framework-specific server provides sufficient depth
• You need real-time code collaboration features rather than static architectural analysis

Quick Start

Configuration

Copy
name: bridge-deepgraph-connector
type: mcp
category: deepgraph

Example Connection

Copy
claude mcp:connect bridge-deepgraph-connector

Available Tools

cross-repo-graph:     Build dependency graphs spanning multiple repositories
compare-architectures: Compare structural patterns between two project graphs
shared-deps:          Identify shared dependencies and version conflicts across projects
api-surface:          Map public API surfaces and their consumers across repositories
migration-impact:     Analyze the impact of changes in one repo on dependent repositories

Core Concepts

Cross-Repository Analysis Overview

Aspect	Details
Transport	stdio-based MCP process with multi-project configuration support
Scope	Analyzes multiple repositories or monorepo packages simultaneously
Graph Merging	Combines individual project graphs into a unified dependency view
API Tracking	Traces published package interfaces to their consumer callsites
Versioning	Tracks dependency version ranges and detects conflicts across projects

Cross-Repository Architecture

Claude Code IDE
    |
    v
[MCP Client] --stdio--> [DeepGraph Bridge]
                              |
                    +---------+---------+
                    |         |         |
                    v         v         v
              [Repo A]   [Repo B]   [Repo C]
              Graph       Graph      Graph
                    \         |         /
                     [Graph Merger Engine]
                              |
                              v
                    [Cross-Repo Analysis]
                     /        |        \
               Shared     API        Impact
               Deps      Surface    Analysis

Configuration

Parameter	Type	Default	Description
repositories	string[]	required	List of local paths or repository URLs to include in analysis
package_registry	string	npm	Package registry to resolve cross-project dependencies (npm, pypi, crates)
include_private	boolean	true	Include private/internal packages in cross-repository dependency analysis
cache_graphs	boolean	true	Cache individual project graphs to speed up repeated cross-repo analyses
max_repos	integer	20	Maximum number of repositories to analyze in a single cross-repo operation

Best Practices

1. Map Microservice Dependencies First - Before making breaking changes to a shared library or API, use cross-repo-graph to identify every consuming service. This dependency map prevents unintended breakage in downstream services.

2. Detect Version Conflicts Early - Run shared-deps across all repositories in your organization to find conflicting dependency versions. Divergent versions of the same package across services can cause subtle runtime incompatibilities in production.

3. Use API Surface Analysis for Contract Testing - The api-surface tool reveals which functions and types from one repository are used by others. Use this information to establish contract tests that verify API compatibility before publishing new versions.

4. Cache Graphs for Large Organizations - Enable graph caching when analyzing many repositories. Cached graphs make iterative analysis significantly faster since unchanged repositories do not need to be re-parsed on each run.

5. Run Impact Analysis Before Major Releases - Use migration-impact to simulate the effect of upgrading a shared dependency or modifying a public API. The analysis shows exactly which files, functions, and tests in downstream repositories would be affected.

Common Issues

1. Memory Exhaustion with Many Repositories - Analyzing dozens of large repositories simultaneously can exhaust available memory. Reduce max_repos or analyze subsets of related repositories rather than the entire organization at once.

2. Private Repository Access Denied - Cross-repo analysis requires read access to all specified repositories. Ensure your file system permissions or Git credentials allow access to every repository in the configuration.

3. Stale Cache Produces Outdated Results - When cache_graphs is enabled, changes to source repositories are not reflected until the cache is refreshed. Clear cached graphs for repositories that have been recently modified before running cross-repo analysis.