BranchDeploy
BranchDeploy lets Claude deploy Azure DevOps work items exactly the way the Deploy button on the ticket does. Give Claude a ticket number and BranchDeploy resolves the work item's project, its linked Azure Repos branch or pull request, the target environment and that environment's configured Azure Pipeline, then shows you the plan before anything runs. Claude can't pick an arbitrary branch or pipeline. Everything comes from your project configuration and each environment's branch rules, and every deploy needs your explicit confirmation of a preview. What you can do: - Deploy a ticket to QA, staging or UAT: "Deploy ticket 2372 to UAT" - See what's deployed where: recent deployments by project, environment or work item - Follow a run from queued to succeeded or failed, with a link to the pipeline run - List the environments configured for each project - Draft customer-facing release notes from recent deployments, preview the exact public output, and publish only after you confirm Requirements: a BranchDeploy workspace connected to your Azure DevOps organisation through the BranchDeploy Marketplace extension, and an Azure DevOps PAT saved by a workspace admin for previews and deploys. Any plan can list environments, check history and status, and preview deploys; Pro adds deploying from Claude and release notes. Built for teams using Azure Boards, Azure Repos and Azure Pipelines together. Not for GitHub, GitLab or other CI systems.
Choose a connection option
13 tool names reported
Source-declared tools. Availability can depend on the connection and permissions; these are not runtime test results.
Claude connector directory ↗ · Observed 2026-11-01 · Completeness not established
archive_release_notecreate_release_note_draftdeployget_deployment_historyget_deployment_statusget_work_item_detailslist_environmentslist_release_note_candidateslist_release_notespreview_deploypreview_release_notepublish_release_noteupdate_release_note_draft
Sources and provenance
- Claude connector directoryClaude tier: community · Observed
- Official MCP RegistryObserved
Grouping basis: endpoint. Exact endpoints or package sets can be grouped automatically; other relationships require evidence review. This does not verify publisher affiliation, connection health, or equivalent capabilities.