{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-azure-devops","slug":"azure-devops","name":"Azure DevOps","type":"mcp","url":"https://github.com/microsoft/azure-devops-mcp","page_url":"https://unfragile.ai/azure-devops","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-azure-devops__cap_0","uri":"capability://tool.use.integration.work.item.crud.operations.via.mcp","name":"work-item-crud-operations-via-mcp","description":"Enables AI agents to create, read, update, and delete Azure DevOps work items (user stories, bugs, tasks) through MCP protocol handlers that map to Azure DevOps REST API v7.0+ endpoints. The MCP server translates agent tool calls into authenticated HTTP requests, handling field validation, state transitions, and relationship management (parent-child links, dependencies) while maintaining Azure DevOps data model constraints.","intents":["I want my AI agent to automatically create bug reports from error logs with proper severity and assignment","I need to programmatically update work item status and add comments based on CI/CD pipeline results","I want to bulk-modify work items (e.g., change sprint assignment) through natural language commands to an agent"],"best_for":["DevOps teams automating work item lifecycle management","AI agent builders integrating project management into autonomous workflows","Teams migrating from REST API polling to event-driven MCP patterns"],"limitations":["MCP protocol adds ~100-200ms latency per operation vs direct REST calls due to serialization overhead","Field customization limited to Azure DevOps organization's configured work item types and custom fields","Batch operations require sequential MCP calls; no native bulk API wrapping in MCP layer","No real-time work item change notifications; polling-based updates only"],"requires":["Azure DevOps organization with API access enabled","Personal Access Token (PAT) with 'Work Items (Read & Write)' scope","MCP client implementation (Claude Desktop, custom agent framework, etc.)","Network connectivity to dev.azure.com or on-premises Azure DevOps Server"],"input_types":["structured JSON (work item fields, IDs, query filters)","natural language (agent interprets intent and maps to API parameters)"],"output_types":["structured JSON (work item objects with all fields)","operation status (success/failure with error details)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-azure-devops__cap_1","uri":"capability://search.retrieval.query.work.items.with.wiql.execution","name":"query-work-items-with-wiql-execution","description":"Allows agents to execute Work Item Query Language (WIQL) queries against Azure DevOps through MCP tool handlers, translating natural language search intents into WIQL syntax and executing them via the Azure DevOps Query API. Results are returned as structured work item collections with full field hydration, supporting filtering by state, assignee, sprint, tags, and custom fields while respecting project-level security permissions.","intents":["I want my agent to find all open bugs assigned to a specific team member across multiple projects","I need to query work items matching complex criteria (e.g., 'high priority AND in current sprint AND not closed') to feed into downstream automation","I want to retrieve work items by tag or custom field values for reporting or triage workflows"],"best_for":["Agents performing intelligent work item triage and routing","Automation workflows that need to discover work items matching dynamic criteria","Teams building AI-powered dashboards or reporting on top of Azure DevOps"],"limitations":["WIQL syntax complexity may require agent fine-tuning to generate correct queries; malformed WIQL returns API errors","Query results limited to 20,000 items per execution; pagination required for large result sets","No real-time query subscriptions; agents must poll for changes","Custom field queries require knowledge of exact field reference names (not display names)"],"requires":["Azure DevOps organization with query API enabled","PAT with 'Work Items (Read)' scope minimum","MCP client with tool-calling capability","Knowledge of WIQL syntax or agent prompt engineering to generate valid queries"],"input_types":["WIQL query string (direct or generated by agent)","natural language search intent (agent translates to WIQL)"],"output_types":["JSON array of work item objects with all requested fields","metadata (total count, query execution time)"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-azure-devops__cap_10","uri":"capability://data.processing.analysis.custom.field.and.process.template.querying","name":"custom-field-and-process-template-querying","description":"Enables agents to query custom field definitions, work item type schemas, and process template configurations through MCP handlers that call the Process and Work Item Type APIs. Agents can discover available custom fields, their data types and allowed values, and work item type workflows, enabling schema-aware automation that adapts to organization-specific configurations.","intents":["I want my agent to discover what custom fields are available in my organization before creating work items","I need to validate that a field value is within the allowed values for a custom field before updating","I want to understand the workflow states for a work item type to ensure state transitions are valid"],"best_for":["Agents performing schema-aware work item creation and updates","Workflows that need to adapt to organization-specific process templates","Teams building intelligent form validation and field mapping"],"limitations":["Process template queries are read-only; agents cannot modify process templates via MCP","Custom field definitions are cached; changes require agent restart or cache invalidation","Allowed values for dropdown fields may be large; pagination required for comprehensive enumeration","Process template inheritance (inherited vs custom fields) adds complexity to schema discovery"],"requires":["Azure DevOps organization with process template access","PAT with 'Work Items (Read)' scope","MCP client with schema caching capability","Project ID or work item type name for queries"],"input_types":["project ID, work item type name, field reference name"],"output_types":["field definition objects (name, type, allowed values, required)","work item type schema (fields, workflow states, transitions)"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-azure-devops__cap_2","uri":"capability://automation.workflow.pipeline.execution.triggering.and.monitoring","name":"pipeline-execution-triggering-and-monitoring","description":"Enables agents to trigger Azure Pipelines (CI/CD builds and releases) through MCP handlers that call the Pipelines API, passing parameters and queue options, then poll pipeline run status to monitor execution progress. The MCP server translates agent intents into pipeline queue requests, tracks run state transitions (queued → in-progress → completed), and surfaces logs/artifacts for downstream processing.","intents":["I want my agent to trigger a deployment pipeline when a work item reaches 'ready for deployment' status","I need to monitor a running pipeline and notify stakeholders when it completes or fails","I want to queue a build with specific parameters (branch, variables) based on agent decision logic"],"best_for":["Teams automating CI/CD workflows with intelligent decision gates","Agents coordinating multi-stage deployments with approval workflows","DevOps teams building self-healing or auto-remediation systems"],"limitations":["Pipeline execution is asynchronous; agents must implement polling loops with configurable intervals (default ~30s)","No native webhook support in MCP layer; agents cannot receive push notifications of pipeline state changes","Large pipeline logs (>10MB) may timeout or require chunked retrieval","Pipeline parameters must match exact variable names and types defined in pipeline YAML"],"requires":["Azure DevOps project with Pipelines enabled","PAT with 'Build (Read & Execute)' scope","MCP client with async/polling capability","Pipeline definitions already configured in Azure Pipelines"],"input_types":["pipeline ID or name","pipeline parameters (key-value pairs matching pipeline variables)","queue options (branch, source version, etc.)"],"output_types":["pipeline run object (ID, status, start/end times)","logs (text stream)","artifacts (file references)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-azure-devops__cap_3","uri":"capability://search.retrieval.repository.code.access.and.metadata.retrieval","name":"repository-code-access-and-metadata-retrieval","description":"Allows agents to retrieve repository metadata, file contents, and commit history from Azure Repos through MCP handlers that call the Git API. Agents can fetch specific file versions, list directory contents, retrieve commit logs with diffs, and access branch information, enabling code-aware decision-making and context enrichment for downstream tasks.","intents":["I want my agent to fetch the current version of a configuration file to validate deployment parameters","I need to retrieve recent commit history for a file to understand what changed and why","I want to check if a specific branch exists and get its latest commit before triggering a build"],"best_for":["Agents performing code-aware automation (e.g., validating code changes before deployment)","Workflows that need to correlate code changes with work items or pipeline failures","Teams building intelligent code review or compliance automation"],"limitations":["Large file retrieval (>100MB) may timeout; chunked reading required","Diff generation for binary files not supported; text-only diffs available","No real-time file change subscriptions; agents must poll for updates","Repository access limited by PAT permissions; cannot bypass Azure DevOps security model"],"requires":["Azure Repos repository (Git or TFVC)","PAT with 'Code (Read)' scope minimum","MCP client with file I/O capability","Repository URL or project/repo identifiers"],"input_types":["repository path, file path, branch/commit reference","query parameters (recursive listing, include history, etc.)"],"output_types":["file content (text or binary)","directory listing (JSON with file metadata)","commit history (JSON array with commit objects, diffs)"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-azure-devops__cap_4","uri":"capability://data.processing.analysis.test.results.querying.and.analysis","name":"test-results-querying-and-analysis","description":"Enables agents to query test execution results from Azure Test Plans through MCP handlers that retrieve test runs, test cases, and failure details. Agents can filter by test plan, test suite, execution date, and outcome (passed/failed/skipped), then analyze failure patterns to identify flaky tests or systemic issues for automated remediation or reporting.","intents":["I want my agent to check if a specific test suite passed in the latest pipeline run before approving deployment","I need to identify flaky tests (tests that fail intermittently) to flag for investigation","I want to retrieve test failure details and correlate them with code changes to identify root causes"],"best_for":["Teams automating test-driven deployment gates","QA automation workflows that need to analyze test trends","Agents performing intelligent test failure triage and root cause analysis"],"limitations":["Test results API has high latency for large test runs (>10k tests); pagination required","Flakiness detection requires historical data collection; single run insufficient for pattern detection","Test failure details limited to logs and attachments; no automatic stack trace parsing","Test Plans API less mature than Work Items API; some features may have limited MCP coverage"],"requires":["Azure Test Plans configured in project","PAT with 'Test Management (Read)' scope","MCP client with data aggregation capability","Test runs already executed (cannot trigger test execution directly via this capability)"],"input_types":["test plan ID, test suite ID, test run ID","filters (date range, outcome, configuration)"],"output_types":["test run objects (metadata, outcome, duration)","test case results (individual test outcomes with details)","failure logs and attachments"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-azure-devops__cap_5","uri":"capability://automation.workflow.pull.request.lifecycle.management","name":"pull-request-lifecycle-management","description":"Allows agents to create, review, update, and complete pull requests in Azure Repos through MCP handlers that call the Pull Request API. Agents can create PRs with specific source/target branches, add reviewers, post comments, approve/reject reviews, and merge PRs with policy enforcement, enabling automated code review workflows and merge gates.","intents":["I want my agent to create a pull request when a feature branch is ready for review","I need to automatically approve or request changes on a PR based on code analysis results","I want to merge a PR only after all required reviewers have approved and CI checks pass"],"best_for":["Teams automating code review workflows with intelligent approval gates","Agents performing automated code quality checks and policy enforcement","DevOps teams building self-service merge automation"],"limitations":["PR creation requires source branch to exist and have commits; cannot create empty PRs","Merge policies (required reviewers, build validation) enforced by Azure DevOps; agents cannot bypass them","Comment threading limited to top-level comments; nested replies not supported via API","PR status transitions (draft → ready, abandoned) have specific preconditions; agents must validate state before transitions"],"requires":["Azure Repos Git repository","PAT with 'Code (Read & Write)' scope","MCP client with state machine handling","Source and target branches must exist in repository"],"input_types":["source branch, target branch, PR title/description","reviewer identities, approval/rejection decisions","merge options (squash, rebase, etc.)"],"output_types":["PR object (ID, status, reviewers, approval state)","merge result (success/failure with policy violation details)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-azure-devops__cap_6","uri":"capability://automation.workflow.release.deployment.orchestration","name":"release-deployment-orchestration","description":"Enables agents to manage release definitions and deployments through MCP handlers that call the Release Management API. Agents can create releases, trigger deployments to specific environments, approve/reject stage deployments, and monitor deployment status across multiple stages, enabling intelligent deployment orchestration with approval gates and rollback capabilities.","intents":["I want my agent to create a release and deploy it to staging after all tests pass","I need to approve a production deployment only after verifying health checks and stakeholder sign-off","I want to monitor multi-stage deployments and automatically rollback if health metrics degrade"],"best_for":["Teams automating multi-stage deployment workflows with approval gates","Agents performing intelligent release orchestration with health-based decisions","DevOps teams building self-healing deployment systems"],"limitations":["Release Management API is legacy; newer Azure Pipelines Environments API recommended but may have different MCP coverage","Deployment approvals are asynchronous; agents must poll for approval status","Rollback requires manual intervention or custom runbook execution; not directly exposed via Release API","Stage deployment order is fixed by release definition; agents cannot dynamically reorder stages"],"requires":["Azure Pipelines Release definitions configured","PAT with 'Release (Read & Manage)' scope","MCP client with async polling and approval handling","Target environments already defined in release definition"],"input_types":["release definition ID, artifact version, environment name","approval decisions (approve/reject with comments)"],"output_types":["release object (ID, status, artifact version)","deployment object (environment, status, approval state, logs)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-azure-devops__cap_7","uri":"capability://search.retrieval.team.and.project.membership.querying","name":"team-and-project-membership-querying","description":"Allows agents to query team membership, project permissions, and user identities through MCP handlers that call the Identity and Graph APIs. Agents can retrieve team members, check user permissions for specific resources, and resolve user identities by email or display name, enabling permission-aware automation and user-targeted notifications.","intents":["I want my agent to find the current team lead to assign a critical bug","I need to check if a user has permission to approve a deployment before granting approval","I want to notify all team members in a specific project when a deployment completes"],"best_for":["Agents performing permission-aware automation and access control","Workflows that need to route tasks to specific team members","Teams building intelligent notification and escalation systems"],"limitations":["User identity resolution may return multiple matches for common names; agents must disambiguate","Permission checks are point-in-time; cached results may become stale if permissions change","Graph API access limited by organization settings; some user attributes may not be queryable","Team membership changes are not real-time; agents must poll for updates"],"requires":["Azure DevOps organization with Graph API enabled","PAT with 'User Profile (Read)' scope","MCP client with identity resolution logic","User email addresses or display names for lookups"],"input_types":["team ID, project ID, user email/display name","resource ID for permission checks"],"output_types":["user/team objects (identity, email, display name)","permission objects (resource, permission level)"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-azure-devops__cap_8","uri":"capability://automation.workflow.board.and.sprint.state.management","name":"board-and-sprint-state-management","description":"Enables agents to manage board state, sprint planning, and work item board position through MCP handlers that call the Board and Iteration APIs. Agents can move work items between board columns, update sprint assignments, manage board settings, and retrieve board state snapshots, enabling visual workflow automation and sprint planning assistance.","intents":["I want my agent to automatically move a work item to 'Done' when its associated pipeline completes successfully","I need to help with sprint planning by suggesting work items to add based on team velocity","I want to retrieve the current board state to analyze workflow bottlenecks"],"best_for":["Teams automating kanban/scrum workflow transitions","Agents assisting with sprint planning and capacity management","Workflows that need to synchronize work item state with external systems"],"limitations":["Board column transitions must respect workflow rules defined in work item type; agents cannot bypass validation","Sprint assignment changes are constrained by sprint dates; cannot assign to past sprints","Board customizations (swimlanes, columns) are organization-specific; agents must adapt to board configuration","Board state snapshots are point-in-time; no historical board state retrieval"],"requires":["Azure Boards configured in project","PAT with 'Work Items (Read & Write)' scope","MCP client with board state awareness","Knowledge of board column names and workflow rules"],"input_types":["work item ID, target column/sprint","board configuration queries"],"output_types":["board state (work items by column, swimlane)","sprint metadata (dates, capacity, assigned items)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-azure-devops__cap_9","uri":"capability://automation.workflow.notification.and.subscription.management","name":"notification-and-subscription-management","description":"Allows agents to create and manage event subscriptions and notifications through MCP handlers that call the Service Hooks and Notifications APIs. Agents can subscribe to Azure DevOps events (work item changes, pipeline completions, PR updates) and configure notifications to external systems, enabling event-driven automation and alerting without polling.","intents":["I want my agent to subscribe to work item changes and trigger downstream automation when specific fields change","I need to send notifications to Slack or Teams when a deployment completes or fails","I want to set up webhooks to external systems when pull requests are created"],"best_for":["Teams building event-driven automation on top of Azure DevOps","Agents that need to react to Azure DevOps events in real-time","Workflows integrating Azure DevOps with external notification systems"],"limitations":["Service Hooks require external webhook endpoint; agents must provide callback URL","Event filtering is limited to predefined event types and basic conditions; complex filtering requires webhook-side logic","Subscription management is asynchronous; agents must track subscription IDs for updates/deletion","Webhook delivery is not guaranteed; agents must implement retry logic and idempotency"],"requires":["Azure DevOps organization with Service Hooks enabled","PAT with 'Service Hooks (Read & Write)' scope","MCP client with webhook endpoint capability or integration with external webhook service","External system capable of receiving HTTP POST callbacks"],"input_types":["event type (work item created, pipeline completed, etc.)","filter criteria (project, work item type, etc.)","webhook URL or notification target"],"output_types":["subscription object (ID, event type, filter, target)","event payload (event details, resource, timestamp)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":27,"verified":false,"data_access_risk":"high","permissions":["Azure DevOps organization with API access enabled","Personal Access Token (PAT) with 'Work Items (Read & Write)' scope","MCP client implementation (Claude Desktop, custom agent framework, etc.)","Network connectivity to dev.azure.com or on-premises Azure DevOps Server","Azure DevOps organization with query API enabled","PAT with 'Work Items (Read)' scope minimum","MCP client with tool-calling capability","Knowledge of WIQL syntax or agent prompt engineering to generate valid queries","Azure DevOps organization with process template access","PAT with 'Work Items (Read)' scope"],"failure_modes":["MCP protocol adds ~100-200ms latency per operation vs direct REST calls due to serialization overhead","Field customization limited to Azure DevOps organization's configured work item types and custom fields","Batch operations require sequential MCP calls; no native bulk API wrapping in MCP layer","No real-time work item change notifications; polling-based updates only","WIQL syntax complexity may require agent fine-tuning to generate correct queries; malformed WIQL returns API errors","Query results limited to 20,000 items per execution; pagination required for large result sets","No real-time query subscriptions; agents must poll for changes","Custom field queries require knowledge of exact field reference names (not display names)","Process template queries are read-only; agents cannot modify process templates via MCP","Custom field definitions are cached; changes require agent restart or cache invalidation","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.32,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:02.371Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=azure-devops","compare_url":"https://unfragile.ai/compare?artifact=azure-devops"}},"signature":"MBWB5fRhCb2l/aTwdiBTbpGNzI1KFinOng/3+GesleLDTI9+nAMuJiOhGvC0V0+6w0fAA+YJfQ9C9AhTn4h2AA==","signedAt":"2026-06-21T22:03:01.629Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/azure-devops","artifact":"https://unfragile.ai/azure-devops","verify":"https://unfragile.ai/api/v1/verify?slug=azure-devops","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}