workspace-surface-audit

To audit your workspace for missing MCP servers and plugins, you run the surface audit to map capabilities and gaps across the repo, configured MCP servers, plugins, and connectors, returning a prioritized set of recommendations.

Identifying missing workflows in your Gemini CLI setup involves benchmarking your workspace capabilities against ECC-native primitives and official marketplace coverage to produce concrete next moves.

Yes, you can compare your current workspace surfaces to native ECC coverage by running a deterministic check for surface visibility and config presence, which benchmarks your setup against official marketplace coverage.

No, the workspace surface audit requires no dependencies to run, as it implements deterministic checks for surface visibility, config presence, and installed components directly within your active workspace.

To map exposed environment keys in your active workspace, you run an inventory check that audits the active harness targets, installed plugins, configured MCP servers, and exposed environment surfaces.

When mapping ECC capabilities, the limitation is that the audit only implements deterministic checks for surface visibility and config presence, meaning it provides recommendations rather than automatically installing missing components.