Problem
Follow-up to #62 (--scope local for ase setup install/update/... and ase setup mcp activate/deactivate).
Now that ASE can be registered at user, project, or local scope, there's no way to check where it's actually active:
claude plugin list does show the ASE plugin's scope and enabled/disabled state, so that part is covered.
claude mcp list does not expose scope per server at all, and has no --scope filter. So distinguishing "this MCP server is registered at local in this project" from "it leaked onto user scope" currently requires calling claude mcp get <name> by hand for each of the servers in the mcpServers registry.
Request
Add an ase setup status [--tool] [--scope] command that reports:
- the ASE plugin's registration scope + enabled/disabled state (via
claude plugin list)
- for each server in the
mcpServers registry, whether it's registered and at which scope (via claude mcp get <name> — scope is already in that output, just not surfaced anywhere aggregated)
mcpInstalled() in tool/src/ase-setup.ts already calls mcp get <name> per server today and only checks the exit code, so this looks like it would mostly be surfacing data that's already being fetched, not new plumbing.
Happy to elaborate if useful.
Problem
Follow-up to #62 (
--scope localforase setup install/update/...andase setup mcp activate/deactivate).Now that ASE can be registered at
user,project, orlocalscope, there's no way to check where it's actually active:claude plugin listdoes show the ASE plugin's scope and enabled/disabled state, so that part is covered.claude mcp listdoes not expose scope per server at all, and has no--scopefilter. So distinguishing "this MCP server is registered atlocalin this project" from "it leaked ontouserscope" currently requires callingclaude mcp get <name>by hand for each of the servers in themcpServersregistry.Request
Add an
ase setup status [--tool] [--scope]command that reports:claude plugin list)mcpServersregistry, whether it's registered and at which scope (viaclaude mcp get <name>— scope is already in that output, just not surfaced anywhere aggregated)mcpInstalled()intool/src/ase-setup.tsalready callsmcp get <name>per server today and only checks the exit code, so this looks like it would mostly be surfacing data that's already being fetched, not new plumbing.Happy to elaborate if useful.