Skip to main content

​
Tool Coverage

The table below shows which MCP clients each Aspex tool works with. aspex doctor detects all installed clients automatically by probing their config file paths - no flags required. aspex trace reads the log files each client already writes to disk - no proxy, no interception. Clients marked - do not yet write MCP tool calls to a parseable log.

​
Config File Locations

​
Claude Desktop

​
Claude Code

Claude Code keeps MCP servers in three places, and aspex scan reads all of them: Connectors added through claude.ai (the remote connector directory) are configured in the cloud and have no local file. aspex scan cannot see them; aspex scan --with-trace lists them as “in use but not in any scanned config” from aspex trace logs, and aspex scan inspect <url> can scan one directly.

​
Cursor

Cursor also supports per-project overrides at .cursor/mcp.json in the workspace root.

​
VS Code

MCP servers are declared under "github.copilot.chat.mcp.servers" in settings.json. Per-workspace config lives in .vscode/mcp.json.

​
Windsurf

​
Cline

Cline stores MCP configuration inside VS Code’s extension storage. The effective path depends on your VS Code profile:

​
Roo-Cline

Same structure as Cline but under the Roo-Cline extension ID:

​
Continue

MCP servers are declared under the "mcpServers" key in config.json.

​
Zed

MCP servers are declared under "context_servers" in Zed’s settings.json.

​
Notes

  • aspex scan reads all config files read-only and never modifies them.
  • The env block values inside config files are never read or reported - only key names are surfaced in findings, so secrets stay local.
  • Paths marked above are for default single-profile installs. Custom --user-data-dir or multi-profile setups may differ.

​
Requesting Support for Additional Clients

Don’t see your client listed? Open a GitHub issue with the client name and its config file path. If you’d like to contribute support yourself, see CONTRIBUTING.md - adding a new client typically means adding its config path to the detector and a fixture file to testdata/configs/.