RepoPilot

modelcontextprotocol / inspector

Search modelcontextprotocol/inspector

GitHub

Code

How modelcontextprotocol/inspector is laid out, and where to start for common changes.

A
Architecture grade
score 99/100
0
Import cycles
lower is better
373
Files mapped
57 imports between them
96%
Layering
of imports point one way

From the map of which files import which, built when the code was last read in full. It shows what depends on what, not a reading order.

Module map

Shade by
Entry points and orchestratorsFoundationStandalonecore205 files · 100+ commitsvitest.shared1 file · 14 commitsclients502 files · 100+ commitstest-servers15 files · 79 commitseslint.config1 file · 7 commitsvitest.setup.shared1 file · 1 commit

6 modules, 2 links. A link means one module imports another; thicker lines mean more imports. Links come from 373 of 799 source files, so the real counts are higher. Select a module to trace it: blue lines go to what it uses, orange lines come from what uses it.

core20510100+Foundation
vitest.shared11014Foundation
clients50202100+Entry or leaf
test-servers150079Standalone
eslint.config1007Standalone
vitest.setup.shared1001Standalone

Where to start reading

  1. Repository root
  2. Repository root
  3. Likely public API
  4. Likely public API
  5. Likely start-up file
  6. Likely start-up file
  7. Suggested starting pointAI
  8. Suggested starting pointAI

Find files for a task

AI

Add a new MCP protocol handler

  • Define the new protocol message types in the schema validation layer
  • Implement handler logic in the core client
  • Add integration test to test server

Add OAuth provider support

  • Register provider in browser auth providers list
  • Implement provider-specific OAuth flow
  • Persist credentials in storage layer

Add a new CLI command

  • Add error handling specific to CLI output format

Add support for a new MCP server configuration type

  • Extend the configuration schema
  • Add config parsing logic

Change the public API

Trace runtime behavior

Add or update tests

Change build or automation

RepoPilot lists up to 500 files, so a file missing here may still exist.

  • Files marked “likely” are guessed from their names.
  • Some entry points named in the manifest are build output or are missing from the file list, so their source is not shown.

Code quality and hotspots

Largest source files

  • Branch points221 per file on average
  • Code issues0 errors, 53 warnings
  • Largest file6,517 lines
  • Hotspot load10 high-risk files

Static checks on the 15 largest source files.

Tests, CI and tooling

  • CIGitHub Actions6 workflows
  • Tests689 test filesJest/Vitest · 0.86 test files per source file (file count, not coverage)
  • Dependency updatesCodeQL

Test folders: clients/cli/__tests__ · clients/cli/__tests__/helpers

Hotspots

Files that change often and branch heavily, highest first. Branch points count if, loop, case, catch, ternary, && and || in the file.