How do I select an installed MCP Inspector interface without downloading tools?
Inspector examples can invoke package runners that fetch dependencies automatically. Choose an existing approved Inspector executable and its documented interface before diagnosing Montage, keeping a bounded protocol check separate from installation, environment changes or weakening local proxy security. Use the installed Inspector’s help to select a real supported interface before copying quickstart syntax. This diagnostic needs no downloader, local protection bypass or model invocation, and its result remains specific to the tested developer-tool path.
Help me select an installed MCP Inspector interface without downloading tools. Identify an already installed Inspector or approved project command. With supported approved auth, inspect discovery and execute only signals_status if appropriate. No writes.Locate the existing executable
Identify an already installed Inspector or approved project command. Do not run an automatic downloader just because the documentation’s quickstart uses a package runner. An existing approved command should be identified before any invocation, avoiding a quickstart that silently downloads another Inspector version during the diagnostic.
Inspect installed help
Check which web, CLI or TUI workflow this version supports. Match flags to the installed interface rather than assuming every release accepts identical argument combinations. The installed help determines supported interfaces and flag combinations; a web example and a CLI example should not be batched together speculatively.
Preserve proxy security
Keep Inspector’s local proxy access controls and tokens private. Local proxy authorization is distinct from Montage account authorization and must not be disabled to make a diagnostic screen easier to access. Local proxy tokens remain private diagnostic-tool credentials and must not be confused with remote Montage consent or shown in a shared demonstration.
Target remote HTTP deliberately
Use documented --server-url and --transport http arguments for the hosted endpoint. A stdio launch command tests a different server mechanism and cannot establish the same remote behavior. The documented remote arguments identify the hosted target without launching a subprocess, preserving the distinction between server transport and local diagnostic machinery.
Report a bounded result
With supported approved auth, inspect discovery and execute only signals_status if appropriate. State the installed interface used and any blocker without claiming that launching Inspector alone certified downstream client interoperability. A working Inspector path remains Inspector-specific proof, not certification that a separate editor with different configuration and storage can authorize the same account.
Keep the boundaries clear.
- Local proxy tokens remain private diagnostic-tool credentials and must not be confused with remote Montage consent or shown in a shared demonstration.
- A working Inspector path remains Inspector-specific proof, not certification that a separate editor with different configuration and storage can authorize the same account.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.