"How to interact with an Azure DevOps repository" matching MCP servers:

A local MCP server that connects Claude Desktop, Claude Code, and Claude Chat to your Azure DevOps organization, enabling querying work items, reviewing pull requests, triggering pipelines, searching code, managing test plans, and updating wikis using plain language.

Enables AI assistants to interact with Azure DevOps projects, including work items, test results, Git repositories, and dependency analysis via the Model Context Protocol.

Provides a read-only MCP bridge that lets Claude Web inspect workspace files, git state, and recorded test results while Codex remains the sole executor of changes.

Provides DevOps and testing tools for full-stack applications, including UI testing, security audits, CI/CD validation, and Rust/Tauri support.

This MCP server lets GitHub Copilot fetch Azure Boards work items by URL or ID and generate QA test cases from the ticket content.

Enables test execution and management through MCP clients, allowing retrieval of projects, listing tests, executing tests with browser selection, and monitoring results.

Enables turning requirements documents into RFCs, functional test scenarios, and a traceability matrix, with tools to parse, diff, and verify coverage.

Automates the conversion of Figma designs into TypeScript React components and integrates with GitHub to create pull requests for the generated code. It includes visual regression testing with Playwright and accessibility validation to ensure implementations match the original designs.

Enables agents to turn a plain-language description of a device into a complete, validated build package — parts list, 3D-printable parts, wiring, firmware code, picture assembly guide, and tests — that anyone can assemble without electronics experience.

Enables AI agents to inspect Git repositories for changes across committed, staged, unstaged, and untracked scopes, and run allowlisted validation commands with structured results.

Provides a testable gateway path for running a local MCP-style server in hosted-like conditions, with tenant-isolated reads, approval-denied writes, deterministic failures, and smoke-test verification.

Enables a language model to run four deterministic data checks it cannot argue with — column-contract validation with an explicit quarantine list, arithmetic reconciliation of opening/movements/closing, distinct entity counting against row counts, and duplicate detection returned for human review — each answering with structured findings and row/column locators. Failures come back as results with reasons, so the model reports exactly which rows and columns are broken rather than asserting the data is clean.

MCP server for Xray Cloud test management that enables importing automation results and managing tests, test executions, and test sets in Jira.

Automates downloading mobile game performance data from PerfDog and converts it to Tableau-ready CSV format with device statistics, FPS metrics, and time-series data.

Enables migration of test automation projects from WebDriverIO to Playwright using AST-based transformations. Provides tools for analyzing tests, converting syntax, refactoring to Page Object Model, and generating migration reports.

Provides a framework for running multiple MCP servers using FastAPI, stdio, and streamable-http transports, with an echo tool for testing and integration with MCP Inspector.

Enables a stateless, horizontally scaled MCP server using the 2026-07-28 specification, with tools for load testing and instance-aware operations.

An MCP server that enables Claude to create and manage TestRail test cases directly from Jira or Azure DevOps user stories. It provides tools for section management and automated test case creation with built-in format enforcement and traceability links.

An MCP server that diagnoses Flutter + Stripe (flutter_stripe) setup issues — so Claude can check your project automatically.

Read-only MCP server that exposes the agentic-os governance, SDLC, and Quality Engineering methodology to any MCP host. It never writes to your repository and never executes code — it serves the methodology, plans an install, and verifies it, handing any commands back to the host to run.