For the complete documentation index, see llms.txt. This page is also available as Markdown.

observal scan

Discover MCP servers, hooks, and telemetry configuration across your harness configs. scan is read-only -- it shows what you have without modifying any files.

To install session telemetry hooks, use observal doctor patch. MCP commands and URLs are never rewritten.

Synopsis

observal scan [--harness <harness>]

Options

Option
Description

--harness <harness>

Scope to one harness: cursor, kiro, claude-code, codex, copilot, copilot-cli, opencode, antigravity, goose, pi

If you run observal scan with no flags, it auto-detects every installed harness and scans each in turn.

What it does

  1. Finds MCP config files:

    • Claude Code: ~/.claude/settings.json

    • Kiro: .kiro/settings/mcp.json (project) or ~/.kiro/settings/mcp.json (home)

    • Cursor: .cursor/mcp.json

    • Copilot: .vscode/mcp.json

    • Antigravity: .agents/mcp_config.json or ~/.gemini/antigravity-cli/mcp_config.json

    • Goose: ~/.config/goose/config.yaml (the extensions key)

    • Copilot CLI: ~/.copilot/mcp-config.json

  2. Lists every MCP server found and its direct command or URL.

  3. Reports installed session telemetry hooks.

No files are written. No servers are contacted. No registration happens.

Example

Output:

Scoping to a single harness

What to do next

Once you see what's installed, instrument it:

Exit codes

Code
Meaning

0

At least one harness config found

1

Server unreachable / auth failed

3

No harness configs found

Last updated

Was this helpful?