What would you like to be added?
Add a built-in Bitbucket Cloud MCP toolset to HolmesGPT, following the same pattern as the existing GitHub MCP toolset (https://holmesgpt.dev/data-sources/builtin-toolsets/github-mcp/).
This would allow Holmes to:
- Investigate CI/CD pipeline failures on Bitbucket Pipelines
- Read PR diffs and context as part of investigations
- Raise fix PRs on Bitbucket Cloud in response to alerts
- Search code across Bitbucket repositories
Proposed Helm config (mirroring GitHub MCP):
mcpAddons:
bitbucket:
enabled: true
auth:
secretName: "bitbucket-mcp-token" # BITBUCKET_USERNAME + BITBUCKET_APP_PASSWORD / Bitbucket API TOKEN
Suggested upstream MCP server candidates to wrap:
Why is this needed?
Broader SCM coverage — many teams use Bitbucket Cloud as their primary source control and are blocked from Holmes's remediation workflows (e.g. auto-raising fix PRs) that GitHub users already benefit from today.
Bitbucket Cloud is widely adopted in enterprises running Kubernetes, making this a natural fit for HolmesGPT's user base. Without this, Bitbucket users must manually act on Holmes's findings rather than letting Holmes close the loop end-to-end.
Community MCP servers for Bitbucket already exist, meaning the integration effort is lower than building from scratch — it primarily requires containerising an upstream server and wiring it into the Helm chart as an mcpAddon, exactly as was done for GitHub.
What would you like to be added?
Add a built-in Bitbucket Cloud MCP toolset to HolmesGPT, following the same pattern as the existing GitHub MCP toolset (https://holmesgpt.dev/data-sources/builtin-toolsets/github-mcp/).
This would allow Holmes to:
Proposed Helm config (mirroring GitHub MCP):
mcpAddons:
bitbucket:
enabled: true
auth:
secretName: "bitbucket-mcp-token" # BITBUCKET_USERNAME + BITBUCKET_APP_PASSWORD / Bitbucket API TOKEN
Suggested upstream MCP server candidates to wrap:
Why is this needed?
Broader SCM coverage — many teams use Bitbucket Cloud as their primary source control and are blocked from Holmes's remediation workflows (e.g. auto-raising fix PRs) that GitHub users already benefit from today.
Bitbucket Cloud is widely adopted in enterprises running Kubernetes, making this a natural fit for HolmesGPT's user base. Without this, Bitbucket users must manually act on Holmes's findings rather than letting Holmes close the loop end-to-end.
Community MCP servers for Bitbucket already exist, meaning the integration effort is lower than building from scratch — it primarily requires containerising an upstream server and wiring it into the Helm chart as an mcpAddon, exactly as was done for GitHub.