Troubleshooting¶
Common issues and solutions for mcpbr.
Docker Issues¶
Docker Not Running¶
Symptom: Error connecting to Docker daemon
Solution:
Pre-built Image Not Found¶
Symptom: Warning about falling back to building from scratch
Solution: This is normal for some tasks. You can manually pull:
Or disable pre-built images to always build from scratch:
Orphaned Containers¶
Symptom: Old mcpbr containers consuming resources
Solution:
Performance Issues¶
Slow on Apple Silicon¶
Symptom: Tasks take much longer than expected on M1/M2/M3 Macs
Explanation: mcpbr uses x86_64 Docker images that run via emulation on ARM64.
Solutions:
-
Install Rosetta 2 for better emulation:
-
Reduce concurrency to avoid resource contention:
-
Increase timeouts:
Task Timeouts¶
Symptom: Tasks fail with "Timeout" error
Solutions:
-
Increase timeout in config:
-
Reduce max iterations if agent is looping:
-
Use a faster model for testing:
API Issues¶
API Key Not Set¶
Symptom: "ANTHROPIC_API_KEY environment variable not set"
Solution:
Add to your shell profile (.bashrc, .zshrc) for persistence.
API Key Invalid¶
Symptom: Authentication errors from Anthropic API
Solutions:
-
Verify the key format (should start with
sk-ant-): -
Check key permissions in Anthropic Console
-
Ensure no extra whitespace:
Rate Limiting¶
Symptom: API rate limit errors
Solutions:
-
Reduce concurrency:
-
Add delays between tasks (requires code modification)
-
Check your API tier limits in Anthropic Console
CLI Issues¶
Claude CLI Not Found¶
Symptom: "Claude Code CLI (claude) not found in PATH"
Solution:
If installed but not found, check your PATH includes npm global binaries:
Command Not Found: mcpbr¶
Symptom: "mcpbr: command not found"
Solutions:
-
Ensure mcpbr is installed:
-
Check it's in your PATH:
-
Use the full path or module:
MCP Server Issues¶
Server Not Starting¶
Symptom: "Warning: MCP server add failed"
Solutions:
-
Test the server independently:
-
Check environment variables:
-
Verify the command exists:
Tools Not Appearing¶
Symptom: MCP tools not being used by the agent
Possible causes:
- Server not registering tools correctly
- Tool descriptions unclear
- Built-in tools sufficient for the task
Debug steps:
-
Enable verbose logging:
-
Check per-instance logs for tool registration
- Review tool_usage in results JSON
Evaluation Issues¶
Patch Not Applying¶
Symptom: "Patch does not apply" error
Explanation: The agent's changes don't apply cleanly to the original repository state.
This can happen when:
- Agent modified files that conflict with test patches
- Agent created files instead of modifying existing ones
- Git state is inconsistent
Note: This is often an agent behavior issue, not an mcpbr bug.
Tests Failing¶
Symptom: Tests fail even though patch applies
Debug steps:
-
Check per-instance logs for test output:
-
Review the fail_to_pass results in JSON output
-
The agent may have made an incorrect fix
No Patch Generated¶
Symptom: "No changes made by Claude Code"
Possible causes:
- Agent didn't find a solution
- Agent made changes then reverted them
- Max iterations reached without completing
Solutions:
-
Increase max_iterations:
-
Review logs to understand agent behavior
Getting Help¶
Gathering Debug Information¶
When reporting issues, include:
# Version info
mcpbr --version
python --version
docker --version
# Environment
echo $ANTHROPIC_API_KEY | head -c 10 # First 10 chars only
# Run with verbose logging
mcpbr run -c config.yaml -n 1 -vv --log-dir debug-logs/
Where to Get Help¶
- GitHub Issues - Bug reports
- GitHub Discussions - Questions
Common Log Locations¶
| Log Type | Location |
|---|---|
| Per-instance logs | --log-dir directory |
| Single log file | --log-file path |
| Docker logs | docker logs <container_id> |