{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-azure-devopsmcp","slug":"npm-azure-devopsmcp","name":"@azure-devops/mcp","type":"mcp","url":"https://www.npmjs.com/package/@azure-devops/mcp","page_url":"https://unfragile.ai/npm-azure-devopsmcp","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-azure-devopsmcp__cap_0","uri":"capability://tool.use.integration.azure.devops.work.item.crud.operations.via.mcp.protocol","name":"azure devops work item crud operations via mcp protocol","description":"Enables Claude and other MCP clients to create, read, update, and delete work items (user stories, bugs, tasks) in Azure DevOps projects through standardized MCP tool calls. Translates MCP function schemas into Azure DevOps REST API calls, handling authentication via Personal Access Tokens (PAT) and marshaling work item fields (title, description, state, assignee, area path, iteration) between client and server.","intents":["Programmatically create bug reports from error logs or test failures without leaving Claude","Query and filter work items by project, iteration, or state to build context-aware task lists","Update work item status, assignee, or description in response to conversation context","Delete or archive completed work items as part of automated cleanup workflows"],"best_for":["Teams using Azure DevOps as their primary project management system","AI-assisted development workflows where Claude needs to interact with backlog items","DevOps engineers building autonomous agents that manage work item lifecycle"],"limitations":["Requires valid Azure DevOps Personal Access Token (PAT) with appropriate scopes — token leakage exposes work item access","No built-in caching of work item state — each query hits Azure DevOps REST API, adding latency for high-frequency operations","Limited to work item fields exposed by Azure DevOps REST API v7.0+ — custom fields may require additional mapping","No transactional support — bulk operations are sequential, not atomic"],"requires":["Azure DevOps organization and project with at least one team","Personal Access Token (PAT) with 'Work Items (read, write)' scope","Node.js 16+ runtime","MCP client compatible with tool-use-integration protocol (Claude, etc.)"],"input_types":["JSON-structured work item payloads (title, description, state, assignee, area path, iteration)","Query filters (project name, work item type, state, assigned to)","Work item IDs (integers)"],"output_types":["JSON work item objects with full metadata (ID, title, state, assignee, created date, updated date)","Paginated work item lists with query results","Operation confirmation responses (success/failure with error details)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-azure-devopsmcp__cap_1","uri":"capability://tool.use.integration.azure.devops.repository.and.git.operations.via.mcp","name":"azure devops repository and git operations via mcp","description":"Exposes git repository operations (clone, branch listing, commit history, pull request creation/review) and repository metadata queries through MCP tool calls. Translates MCP requests into Azure DevOps Git REST API calls, managing authentication and handling repository references (project, repo name, branch names) to enable Claude to interact with source control without direct git CLI access.","intents":["List branches and commits in a repository to understand code history and current state","Create pull requests programmatically with title, description, and source/target branches","Query commit history and file changes to provide context for code review or debugging","Retrieve repository metadata (default branch, clone URLs, permissions) for CI/CD setup"],"best_for":["Development teams using Azure Repos (Azure DevOps git) who want Claude to assist with PR creation and code review","CI/CD pipelines that need to query repository state or create PRs based on automated decisions","Developers building AI-assisted code review agents that need git history context"],"limitations":["No direct file read/write — repository operations are limited to git metadata and PR management, not file content manipulation","Commit history queries return paginated results; large repositories may require multiple API calls to retrieve full history","Pull request creation requires valid source and target branches — no automatic branch creation","No support for advanced git operations (rebase, cherry-pick, merge conflict resolution)"],"requires":["Azure DevOps organization with Git repositories (Azure Repos)","Personal Access Token (PAT) with 'Code (read, write)' scope","Node.js 16+ runtime","MCP client with tool-use-integration support"],"input_types":["Repository identifiers (project name, repository name)","Branch names (source and target for PR operations)","PR metadata (title, description, reviewers)","Commit/history query filters"],"output_types":["JSON branch lists with metadata (name, commit ID, last updated)","Commit history with author, message, date, and file changes","Pull request objects with status, reviewers, and merge state","Repository metadata (clone URLs, default branch, permissions)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-azure-devopsmcp__cap_2","uri":"capability://tool.use.integration.azure.devops.pipeline.and.build.execution.via.mcp","name":"azure devops pipeline and build execution via mcp","description":"Enables triggering, querying, and monitoring Azure Pipelines (CI/CD) builds through MCP tool calls. Translates MCP requests into Azure DevOps Pipelines REST API, handling pipeline definitions, build queuing, status polling, and artifact retrieval. Supports parameterized pipeline execution (passing variables to pipeline runs) and build log streaming for debugging.","intents":["Trigger a CI/CD pipeline run with custom parameters (branch, environment, feature flags) from Claude","Query build status and history to understand deployment state without manual dashboard checks","Retrieve build logs and artifacts for debugging failed builds or analyzing test results","Monitor pipeline execution and wait for completion before proceeding with dependent tasks"],"best_for":["DevOps teams automating CI/CD workflows with Claude-driven orchestration","Developers who want to trigger builds and check status from conversational AI without leaving Claude","Autonomous agents that need to manage deployment pipelines based on code changes or events"],"limitations":["Pipeline execution is asynchronous — no built-in polling/waiting mechanism; clients must implement their own status checks","Build logs are returned as plain text; no structured parsing of test results or error patterns","Limited to pipeline execution and status — no pipeline definition editing or creation","Artifact retrieval requires knowledge of artifact names; no discovery mechanism for available artifacts"],"requires":["Azure DevOps organization with configured Azure Pipelines","Personal Access Token (PAT) with 'Build (read, execute)' scope","Node.js 16+ runtime","MCP client with tool-use-integration support"],"input_types":["Pipeline ID or name","Build parameters (branch, variables, queue name)","Build ID for status/log queries"],"output_types":["Build execution confirmation with build ID and queue time","Build status objects (state, result, start/finish time, queued by)","Build logs as plain text or structured error summaries","Artifact metadata and download URLs"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-azure-devopsmcp__cap_3","uri":"capability://tool.use.integration.azure.devops.test.results.and.test.plan.management.via.mcp","name":"azure devops test results and test plan management via mcp","description":"Provides access to test execution results, test case management, and test plan operations through MCP tool calls. Translates MCP requests into Azure DevOps Test Management REST API, enabling queries of test runs, test case status, and test plan metadata. Supports filtering by test suite, configuration, and outcome (passed/failed/skipped) to enable Claude to analyze test health and create test cases.","intents":["Query test results from recent builds to identify failing tests and their error messages","Create or update test cases and test plans programmatically based on requirements","Retrieve test coverage metrics and test execution history for quality reporting","Filter test results by configuration, environment, or test suite to diagnose environment-specific failures"],"best_for":["QA teams using Azure Test Plans who want Claude to analyze test results and suggest fixes","DevOps engineers building autonomous test orchestration and reporting","Development teams integrating test health monitoring into AI-assisted workflows"],"limitations":["Test result queries are read-heavy; no built-in support for bulk test result updates or re-runs","Test case creation requires valid test suite and project context; no automatic test suite discovery","Error messages and stack traces are returned as plain text; no structured parsing of failure root causes","No support for test parameterization or data-driven test execution"],"requires":["Azure DevOps organization with Test Plans configured","Personal Access Token (PAT) with 'Test Management (read, write)' scope","Node.js 16+ runtime","MCP client with tool-use-integration support"],"input_types":["Test run ID or test plan ID","Test suite and test case identifiers","Filter criteria (outcome, configuration, tester)"],"output_types":["Test result objects with outcome, duration, error message, and stack trace","Test case metadata (title, steps, expected results, assigned tester)","Test plan summary with pass/fail counts and coverage metrics","Test execution history with trend data"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-azure-devopsmcp__cap_4","uri":"capability://tool.use.integration.azure.devops.project.and.team.configuration.queries.via.mcp","name":"azure devops project and team configuration queries via mcp","description":"Exposes project metadata, team membership, area paths, and iteration (sprint) information through MCP tool calls. Translates MCP requests into Azure DevOps Core REST API to retrieve organizational structure, team configurations, and project settings. Enables Claude to understand project context (available teams, iterations, area paths) for work item operations and team-aware task assignment.","intents":["List all teams and members in a project to understand organizational structure and find appropriate assignees","Retrieve current and upcoming iterations (sprints) to assign work items to the correct sprint","Query area paths to understand project structure and assign work items to the correct team area","Fetch project settings and permissions to validate operations before attempting them"],"best_for":["Teams managing complex multi-team projects who need Claude to understand organizational structure","Autonomous agents that need to discover available teams, iterations, and areas before creating work items","DevOps teams building context-aware task assignment and routing"],"limitations":["Read-only operations — no support for creating teams, iterations, or area paths","Team membership queries return basic info (name, email); no detailed permission or role information","Iteration queries return metadata but no work item counts or burndown data","Area path hierarchy is returned as flat list; no tree structure representation"],"requires":["Azure DevOps organization and project","Personal Access Token (PAT) with 'Project & Team (read)' scope","Node.js 16+ runtime","MCP client with tool-use-integration support"],"input_types":["Project name or ID","Team name or ID (optional for team-specific queries)"],"output_types":["Project metadata (name, description, visibility, default team)","Team list with member counts and descriptions","Team member objects (name, email, identity ID)","Iteration list with start/end dates and status (active, future, past)","Area path list with team ownership"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-azure-devopsmcp__cap_5","uri":"capability://tool.use.integration.azure.devops.release.and.deployment.management.via.mcp","name":"azure devops release and deployment management via mcp","description":"Exposes release pipeline operations (create releases, approve deployments, query release status) through MCP tool calls. Translates MCP requests into Azure DevOps Release Management REST API, handling release definitions, deployment approvals, and environment-specific deployment status. Supports querying release history and triggering deployments to specific environments with approval workflows.","intents":["Create a release from a build artifact and trigger deployment to a specific environment","Query release status and deployment progress across multiple environments","Approve pending deployments programmatically based on conditions or Claude's analysis","Retrieve release history and deployment logs for auditing and troubleshooting"],"best_for":["DevOps teams automating release workflows with Claude-driven approval and orchestration","Autonomous deployment agents that need to manage multi-environment releases","Teams implementing AI-assisted release management and deployment monitoring"],"limitations":["Release creation requires valid build artifact and release definition — no automatic release definition generation","Deployment approvals are manual operations; no automatic approval logic based on conditions","Release history queries are paginated; large release histories require multiple API calls","No support for release definition editing or creation"],"requires":["Azure DevOps organization with Release Pipelines configured","Personal Access Token (PAT) with 'Release (read, execute, manage approvals)' scope","Node.js 16+ runtime","MCP client with tool-use-integration support"],"input_types":["Release definition ID or name","Build artifact ID or version","Environment name for deployment targeting","Approval comments and decision (approve/reject)"],"output_types":["Release object with version, status, and created date","Deployment status per environment (pending, in progress, succeeded, failed)","Approval request objects with pending approvers and deadline","Release logs and deployment history"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":38,"verified":false,"data_access_risk":"high","permissions":["Azure DevOps organization and project with at least one team","Personal Access Token (PAT) with 'Work Items (read, write)' scope","Node.js 16+ runtime","MCP client compatible with tool-use-integration protocol (Claude, etc.)","Azure DevOps organization with Git repositories (Azure Repos)","Personal Access Token (PAT) with 'Code (read, write)' scope","MCP client with tool-use-integration support","Azure DevOps organization with configured Azure Pipelines","Personal Access Token (PAT) with 'Build (read, execute)' scope","Azure DevOps organization with Test Plans configured"],"failure_modes":["Requires valid Azure DevOps Personal Access Token (PAT) with appropriate scopes — token leakage exposes work item access","No built-in caching of work item state — each query hits Azure DevOps REST API, adding latency for high-frequency operations","Limited to work item fields exposed by Azure DevOps REST API v7.0+ — custom fields may require additional mapping","No transactional support — bulk operations are sequential, not atomic","No direct file read/write — repository operations are limited to git metadata and PR management, not file content manipulation","Commit history queries return paginated results; large repositories may require multiple API calls to retrieve full history","Pull request creation requires valid source and target branches — no automatic branch creation","No support for advanced git operations (rebase, cherry-pick, merge conflict resolution)","Pipeline execution is asynchronous — no built-in polling/waiting mechanism; clients must implement their own status checks","Build logs are returned as plain text; no structured parsing of test results or error patterns","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.6380125264898635,"quality":0.22,"ecosystem":0.3,"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-05-24T12:16:23.903Z","last_scraped_at":"2026-05-03T14:23:33.035Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":77452,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-azure-devopsmcp","compare_url":"https://unfragile.ai/compare?artifact=npm-azure-devopsmcp"}},"signature":"lPSR5I/gNrNLeVPIrnU3mx0RlSJT5DAUp2stKSSxy6Ozg76YujEzsAj/Lzk5irJbgePDEAVrF9gGHt0CCulVDQ==","signedAt":"2026-06-23T01:43:43.705Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-azure-devopsmcp","artifact":"https://unfragile.ai/npm-azure-devopsmcp","verify":"https://unfragile.ai/api/v1/verify?slug=npm-azure-devopsmcp","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"}}