
BranchDeploy
dev.branch-deployv1.0.0Updated Oct 8, 2026
Deploy Azure DevOps work items to QA, staging or UAT by ticket number via Azure Pipelines.
Overview
AI-generated overview
Lets an assistant trigger Azure Pipelines deployments to QA, staging, or UAT by referencing an Azure DevOps work item ticket number.
- What it does
- BranchDeploy is a remote MCP server that connects an assistant to Azure Pipelines deployment workflows. According to its description, it deploys Azure DevOps work items to QA, staging, or UAT environments by ticket number. No individual tools are listed in the manifest, so the exact tool names and parameters are not documented here.
- When to use it
- Useful when a team tracks work in Azure DevOps and wants an assistant to kick off environment deployments from a ticket number without leaving the chat. It fits release or QA workflows where deployments are already driven by Azure Pipelines.
- Requirements
- A remote MCP endpoint at over streamable HTTP. The manifest declares no authentication, environment variables, or headers, but the underlying Azure DevOps and Azure Pipelines access must be configured on the service side.
Before you install
The server can trigger deployments, which change live QA, staging, or UAT environments. The manifest declares no authentication, so verify how access is actually controlled before connecting. Confirm which Azure DevOps organization and pipelines it can reach.
Installation
In SourceWeft
- Open BranchDeploy in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"branchdeploy": {
"type": "http",
"url": "https://mcp.branch-deploy.dev/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 8, 2026

