AI Assistant Integration (MCP)

Deploy Azure DevOps branches from your AI coding assistant using the Model Context Protocol.

Supported Clients

• Claude Desktop
• Claude in VS Code (via MCP extension)
• Cursor
• Any MCP-compatible AI client

Prerequisites

• BranchDeploy Pro licence
• Azure DevOps PAT connected (see account settings)
• At least one webhook environment configured and synced

Setup

Step 1: Connect Azure DevOps

In your BranchDeploy account at branch-deploy.dev/account, add an Azure DevOps PAT with Work Items (Read) and Code (Read) scopes. If you already did this for the Teams bot, skip this step.

Step 2: Generate an MCP API key

In your account page, go to Settings → MCP API Key and click Generate Key. Copy the key — it is shown once only.

Step 3: Add to your AI client

Claude Desktop — edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "branchdeploy": {
      "url": "https://api.branch-deploy.dev/mcp",
      "headers": {
        "Authorization": "Bearer your-mcp-api-key"
      }
    }
  }
}

Cursor — go to Settings → MCP Servers → Add Server and enter the same URL and header.

Step 4: Try it

Ask your AI assistant:

• "Deploy ticket 1234 to UAT"
• "What environments are configured for project Website?"
• "Show me recent deployments for the Website project"

The AI will always show you what it is about to deploy and ask for confirmation before triggering anything.

How It Works

1. You say "deploy #1234 to UAT"
2. The AI calls BranchDeploy to resolve the linked branch on ticket 1234
3. The AI presents the branch and environment and asks you to confirm
4. After you confirm, the AI calls BranchDeploy to trigger your webhook
5. Your deployment system receives the signed webhook and starts the deployment

Troubleshooting

"Invalid MCP API key"
Regenerate the key in your account settings and update your client config.

"No Azure DevOps PAT configured"
Add a PAT at branch-deploy.dev/account → Connect Azure DevOps.

"Work item not found"
Check the ticket number and ensure the PAT has access to that project.

"No webhook environments"
Configure a webhook environment in the Azure DevOps extension and click Sync Config.