mcp-ado·integration·active

Azure DevOps MCP

Pulls work items + repos; pushes test plans, suites, and runs. Handles ADO test points and outcome states with full bi-directional sync.

TARA EVAN ARIAtrigger · mcp⌘ MCP · Microsoft

Azure DevOps MCP

Pulls work items and repos; pushes test plans, suites, and runs. Handles ADO test points and outcome states with full bi-directional sync.

What flows in

·Work items (User Stories, Bugs, Tasks, Test Cases)

·Repository metadata (branches, pull requests, build status)

·Test plan + test suite hierarchy

·Iteration paths (sprints) + area paths (teams)

What flows out

·New test cases generated by EVAN

·Test runs with per-point outcomes

·Work item updates when ARIA recommendations are accepted

·Build pipeline updates (ADO pipelines API for setting custom statuses)

ADO-specific concepts

Test points

ADO uses "test points" to represent the intersection of (test case × configuration × suite). The connector handles this correctly — when EVAN runs the same test case against three browser configs, the outcome is split across three test points, not collapsed into one.

Outcome states

ADO has 14 possible outcome states (Passed, Failed, Blocked, NotApplicable, NotExecuted, etc.). The connector maps EVAN's simpler pass/fail model to the right ADO state:

·EVAN pass → ADO Passed

·EVAN fail → ADO Failed (with stack trace as a comment)

·EVAN skipped (locator-healer detected real removal) → ADO NotApplicable

·EVAN flaky (passed on retry) → ADO Passed with a flake annotation

Area + iteration paths

Work items in ADO are scoped by hierarchical paths (MyOrgBackendAuthTeam\). The connector resolves paths from short names when possible, falling back to a one-time mapping prompt.

Authentication

PAT (Personal Access Token) with scopes:

·vso.work_write — read/write work items

·vso.test_write — read/write test plans + runs

·vso.code — read repos, push branches if remediation requires

·vso.build — read build status

→The connector refuses to use vso.work_full (the broader scope) even if offered. Minimum scope is policy.

Pull request remediation

When SARA'sRemediation Generator produces a fix, the connector can open a PR directly:

·Creates a feature branch

·Pushes the diff

·Opens a PR with the remediation description

·Links the PR to the originating work item

The PR is opened as draft by default — engineering reviews before merge.

Server

mcp://dev.azure.com/mcp

Vendor

Microsoft.

MCP server endpoint

mcp://dev.azure.com/mcp

vendor · Microsoft

Related · integration

Sprint Context Loader

sprint-context-loader

Pulls sprint metadata — name, dates, team, release tag, prior trend data — directly from connected issue trackers via MCP.

Jira MCP

mcp-jira

Bidirectional Jira connector. TARA pulls stories from sprints; ARIA pushes findings, recommendations, and quality reports back as issues, comments, or sprint reviews.

TestRail MCP

mcp-testrail

Pulls existing test cases and execution history; pushes EVAN-generated tests and run results back as cases, runs, and milestone reports.

GitHub MCP

mcp-github

Reads PRs, issues, code search; opens PRs containing EVAN-generated automation, SARA remediation patches, and ARIA-recommended changes.

Confluence MCP

mcp-confluence

Reads PRDs and ACs from Confluence pages as TARA input. Publishes ARIA's quality reports back as Confluence pages with embedded charts.

Slack MCP

mcp-slack

Real-time notifications when SARA finds Critical issues, LEO breaches an SLO, or ARIA's trend detector flags a regression. Routed to the right channel by component.