googleapis/mcp-toolbox · internal/server/static/js

Import graph

The internal/server/static/js module of googleapis/mcp-toolbox — the files it contains, which are most load-bearing, and how it couples to the rest of the codebase. Derived from the import graph.

Files

Total in-degree

Modules imported

Importing modules

A file in this module participates in a circular import — see the architecture overview.

Files in this module

Ranked by in-degree — how many other files import each one. The top of the list is where the module's weight sits.

sanitize.js3 in · 0 out · radius 6
toolDisplay.js2 in · 3 out · radius 4
loadTools.js2 in · 2 out · radius 2
auth.js1 in · 1 out · radius 5
runTool.js1 in · 1 out · radius 4

Depends on

Modules this one imports from (with the number of import edges).

Imports nothing else in the repo — a foundation/leaf module.

Depended on by

Modules that import from this one — its blast radius if you change it.

Nothing else in the repo imports this module directly.

Ask AI about googleapis/mcp-toolbox

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

What does this repo do, in one paragraph?How would I get started using it?What are the main alternatives?Show me the entry point.

Or write your own question

Informational only. Module boundaries are inferred from source directories and the import graph at the time of analysis; they can be incomplete or stale.