Get details of the authenticated user (id, displayName, email)

List all Azure DevOps organizations accessible to the current authentication

List all projects in an organization

Get details of a specific project

Get comprehensive details of a project including process, work item types, and teams

Get details of a specific repository

Get detailed information about a repository including statistics and refs

List repositories in a project

Get content of a file or directory from a repository

Displays a hierarchical tree view of files and directories across multiple Azure DevOps repositories within a project, based on their default branches

Displays a hierarchical tree view of files and directories within a single repository starting from an optional path

Create a new branch from an existing one

Create a commit on an existing branch using file changes.

• Provide plain branch names (no "refs/heads/").

• ⚠️ Each file path may appear only once per commit request—combine all edits to a file into a single change entry.

• Prefer multiple commits when you have sparse or unrelated edits; smaller focused commits keep review context clear.

🎯 RECOMMENDED: Use the SEARCH/REPLACE format (much easier, no line counting!).

Option 1: SEARCH/REPLACE format (EASIEST) Simply provide the exact text to find and replace:

{
  "changes": [{
    "path": "src/api/services/function-call.ts",
    "search": "return axios.post(apiUrl, payload, requestConfig);",
    "replace": "return axios.post(apiUrl, payload, requestConfig).then(r => { processResponse(r); return r; });"
  }]
}

The server fetches the file, performs the replacement, and generates the diff automatically. No line counting, no hunk headers, no context lines needed!

Option 2: UNIFIED DIFF format (Advanced) If you prefer full control, provide complete unified diffs:

• Each patch MUST have complete hunk headers: @@ -oldStart,oldLines +newStart,newLines @@

• CRITICAL: Every @@ marker MUST include line numbers. Do NOT use @@ without line ranges.

• Include 3-5 context lines before and after changes.

• For deletions: --- a/filepath and +++ /dev/null

• For additions: --- /dev/null and +++ b/filepath

Example unified diff:

{
  "changes": [{
    "patch": "diff --git a/file.yaml b/file.yaml\n--- a/file.yaml\n+++ b/file.yaml\n@@ -4,7 +4,7 @@ spec:\n spec:\n   type: ClusterIP\n   ports:\n-    - port: 8080\n+    - port: 9090\n       targetPort: http\n"
  }]
}

List recent commits on a branch including file-level diff content for each commit

List work items in a project

Get details of a specific work item

Create a new work item

Update an existing work item

Add or remove links between work items

Get comments and discussion history for a specific work item

Upload a file and attach it to a work item. The file is read from the local filesystem, uploaded to Azure DevOps, and linked to the specified work item.

Download an attachment from Azure DevOps and save it to the local filesystem. The attachment ID can be obtained from the work item relations.

Delete an attachment from a work item. The attachment ID can be obtained from the work item relations.

Search for code across repositories in a project

Search for content across wiki pages in a project

Search for work items across projects in Azure DevOps

Create a new pull request, including reviewers, linked work items, and optional tags

Get a pull request by ID (no repositoryId required; best for Azure DevOps Server where PR IDs are project-scoped)

List pull requests in a repository

Get comments from a specific pull request

Add a comment to a pull request (repositoryId optional; derived from pullRequestId when omitted)

Update an existing pull request with new properties, manage reviewers and work items, and add or remove tags

Get the files changed in a pull request, their unified diffs, source/target branch names, and the status of policy evaluations

Summarize the latest status checks and policy evaluations for a pull request.

• Surfaces pipeline and run identifiers so you can jump straight to the blocking validation.

• Pair with pipeline tools (e.g., get_pipeline_run, pipeline_timeline) to inspect failures in depth.

Update the status of a comment thread in a pull request (repositoryId optional; derived from pullRequestId when omitted)

List pipelines in a project

Get details of a specific pipeline

List recent runs for a pipeline

Get details for a specific pipeline run

Download a file from a pipeline run artifact and return its textual content

Retrieve the timeline of stages and jobs for a pipeline run, to reduce the amount of data returned, you can filter by state and result

Retrieve a specific pipeline log using the timeline log identifier

Trigger a pipeline run

Get details of wikis in a project

Get the content of a wiki page

Create a new wiki in the project

Update content of a wiki page

List pages within an Azure DevOps wiki

Create a new page in a wiki. If the page already exists at the specified path, it will be updated.