RepoPilot

googleapis/mcp-toolbox · Architecture

A static read of how googleapis/mcp-toolbox is wired together — module coupling, layering, and circular dependencies — derived from its import graph.

A
Architecture grade
score 95/100
1
Import cycles
lower is better
355
Modules parsed
966 edges
99%
Layeredness
clean-layer ratio

Most-depended-on modules

These are the highest-fan-in files — change them and the blast radius is largest. Read them first.

  • internal/testutils/mocks.go167 importers · radius 167
  • internal/server/api.go157 importers · radius 163
  • internal/sources/cache.go139 importers · radius 238
  • internal/util/parameters/common.go87 importers · radius 210
  • internal/util/errors.go70 importers · radius 238
  • internal/group/group.go35 importers · radius 37
  • internal/prompts/arguments.go33 importers · radius 195
  • internal/server/primitives/primitives.go28 importers · radius 31

Modules (24)

Source directories grouped from the import graph. Each links to a per-module page with its files and how it couples to the rest.

Circular dependencies (1)

  • internal/server/static/js/toolDisplay.js to internal/server/static/js/runTool.js to internal/server/static/js/toolDisplay.js

Ask AI about googleapis/mcp-toolbox

Grounded in the actual source code. Pick a starter question or write your own.

Or write your own question

Informational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.