These docs are in English. If you prefer German, write us at beta@clickprobe.ai.
ClickProbe + Claude Code
Add clickprobe-proxy as a stdio MCP server so Claude Code’s coding agent can call clickprobe.* tools.
Project-local config (.mcp.json)
Create or edit .mcp.json in your project root:
{
"mcpServers": {
"clickprobe": {
"command": "clickprobe-proxy",
"args": ["--agent-stdio"]
}
}
}
If clickprobe-proxy is not on your PATH, use the full path:
{
"mcpServers": {
"clickprobe": {
"command": "/usr/local/bin/clickprobe-proxy",
"args": ["--agent-stdio"]
}
}
}
Windows example:
{
"mcpServers": {
"clickprobe": {
"command": "C:\\Users\\you\\bin\\clickprobe-proxy.exe",
"args": ["--agent-stdio"]
}
}
}
User-global config (~/.claude/mcp.json)
To make ClickProbe available in every project:
{
"mcpServers": {
"clickprobe": {
"command": "clickprobe-proxy",
"args": ["--agent-stdio"]
}
}
}
First-time setup
- Install
clickprobe-proxy(build from source or download a release binary). - Add the
.mcp.jsonsnippet above to your project. - Log in:
clickprobe-proxy login— opens your browser, stores tokens in the OS keychain. - Start (or restart) Claude Code:
claude— it picks up the new MCP server. - Verify: ask Claude Code to call
clickprobe.get_bugsfor your project ID.
Test it
Open a Claude Code chat in your project directory and ask:
Use clickprobe.get_bugs to list open bugs for project <your-project-id>.
Expected output shape:
{
"bugs": [
{
"id": "b1234...",
"type": "no_response",
"severity": "major",
"title": "Button 'Delete All' has no response",
"first_seen_at": "2026-04-21T10:00:00Z",
"confirmed": false
}
]
}
If the agent returns "I can't connect to ClickProbe" or a login-hint error, run clickprobe-proxy login again.
Environment variable override
To use a self-hosted ClickProbe cloud:
{
"mcpServers": {
"clickprobe": {
"command": "clickprobe-proxy",
"args": ["--agent-stdio"],
"env": {
"CLICKPROBE_API_URL": "https://api.your-instance.example.com"
}
}
}
}
If something breaks → troubleshooting.md