These docs are in English. If you prefer German, write us at beta@clickprobe.ai.

ClickProbe IDE Integration

clickprobe-proxy --agent-stdio is a stdio MCP server that exposes 9 tools to your coding agent:

Tool	Scope	What it does
`clickprobe.trigger_test`	`agent:write`	Start a new exploration session for a project
`clickprobe.get_bugs`	`agent:read`	List open bugs from recent sessions
`clickprobe.get_bug_detail`	`agent:read`	Full detail on a specific bug (screenshots, repro steps)
`clickprobe.retest_bug`	`agent:write`	Queue a session to re-test a known bug
`clickprobe.session_status`	`agent:read`	Check the status and cost of a session
`clickprobe.query_knowledge_graph`	`agent:read`	Query explored pages and elements
`clickprobe.resolve_bug`	`agent:resolve`	Mark a bug resolved / wont_fix / duplicate
`clickprobe.annotate_bug`	`agent:resolve`	Append a free-text note to a bug’s notes thread
`clickprobe.link_pr`	`agent:resolve`	Attach a PR/MR URL to a bug

See Resolve bugs from your IDE for the step-by-step guide and example transcript.

Before you start

Have a proxy binary on PATH. Download from clickprobe.ai/downloads or build from source: cd proxy && go build -o clickprobe-proxy .
Have a ClickProbe account. Sign up at app.clickprobe.ai.
Log in once: clickprobe-proxy login — this stores tokens in your OS keychain.

Claude Code — .mcp.json snippet, first-time setup, test call
Cursor — mcp_settings.json snippet, where to put it
VSCode GitHub Copilot — settings.json snippet, Copilot agent-mode setup
Resolve bugs from your IDE — cheat sheet + example transcript for the 3 resolve-scope tools
Auto-close bugs via commit message (GitHub & GitLab) — passive close on merge, no IDE plugin needed

See troubleshooting.md for common issues: keychain prompts, 401 loops, Windows path quoting, WSL, Docker.