bitbucket

Current plans

Direct accepted alternatives

runtime · job 75%Cline · job 73%Gread · job 72%gitwhy · job 72%mistle · job 78%Claw Code · job 74%nyxory · job 72%sudocode · job 70%Ink · job 77%openclaude · job 73%buildkite · job 72%Bernstein · job 71%gitlab · job 81%gitea_mcp · job 72%gitlab_api · job 71%coding_tools_mcp · job 75%gitintel_mcp · job 74%nts_mcp_fs · job 77%gitlab_mcp_server · job 71%bitbucket_mcp_server · job 76%sync_worktrees · job 71%gitlab_ops_mcp · job 74%github_mcp_server · job 72%git_courer · job 77%buggazi · job 76%deploy_mcp · job 74%mcp_gitlab_server · job 72%repo_bridge · job 76%toke_local · job 74%agentic_ecos · job 72%Tokenectomy Git · job 77%Agent Env MCP · job 78%MCP GitHub Repository Orchestrator · job 75%GitWarren · job 70%Reachpad MCP · job 76%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.

Inspect histories

Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.

This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series