Easily install the Azure DevOps MCP Server for VS Code or VS Code Insiders:

This TypeScript project provides a local MCP server for Azure DevOps, enabling you to perform a wide range of Azure DevOps tasks directly from your code editor.

🚨 Public Preview: This project is in public preview. Tools and features may change before general availability.

1. 📺 Overview
2. 🏆 Expectations
3. ⚙️ Supported Tools
4. 🔌 Installation & Getting Started
5. 🔦 Usage
6. 📝 Troubleshooting
7. 🎩 Samples & Best Practices
8. 🙋‍♀️ Frequently Asked Questions
9. 📌 Contributing

The Azure DevOps MCP Server brings Azure DevOps context to your agents. Try prompts like:

• "List my ADO projects"
• "List ADO Builds for 'Contoso'"
• "List ADO Releases for 'Contoso'"
• "List ADO Repos for 'Contoso'"
• "List test plans for 'Contoso'"
• "List teams for project 'Contoso'"
• "List iterations for project 'Contoso'"
• "List my work items for project 'Contoso'"
• "List work items in current iteration for 'Contoso' project and 'Contoso Team'"

The Azure DevOps MCP Server is built from tools that are concise, simple, focused, and easy to use—each designed for a specific scenario. We intentionally avoid complex tools that try to do too much. The goal is to provide a thin abstraction layer over the REST APIs, making data access straightforward and letting the language model handle complex reasoning.

Interact with these Azure DevOps services:

• core_list_project_teams: Retrieve a list of teams for the specified Azure DevOps project.
• core_list_projects: Retrieve a list of projects in your Azure DevOps organization.
• core_get_identity_ids: Retrieve Azure DevOps identity IDs for a list of unique names.

• work_list_team_iterations: Retrieve a list of iterations for a specific team in a project.
• work_create_iterations: Create new iterations in a specified Azure DevOps project.
• work_assign_iterations: Assign existing iterations to a specific team in a project.

• wit_my_work_items: Retrieve a list of work items relevant to the authenticated user.
• wit_list_backlogs: Retrieve a list of backlogs for a given project and team.
• wit_list_backlog_work_items: Retrieve a list of backlogs for a given project, team, and backlog category.
• wit_get_work_item: Get a single work item by ID.
• wit_get_work_items_batch_by_ids: Retrieve a list of work items by IDs in batch.
• wit_update_work_item: Update a work item by ID with specified fields.
• wit_create_work_item: Create a new work item in a specified project and work item type.
• wit_list_work_item_comments: Retrieve a list of comments for a work item by ID.
• wit_get_work_items_for_iteration: Retrieve a list of work items for a specified iteration.
• wit_add_work_item_comment: Add a comment to a work item by ID.
• wit_add_child_work_items: Create one or more child work items of a specific work item type for the given parent ID.
• wit_link_work_item_to_pull_request: Link a single work item to an existing pull request.
• wit_get_work_item_type: Get a specific work item type.
• wit_get_query: Get a query by its ID or path.
• wit_get_query_results_by_id: Retrieve the results of a work item query given the query ID.
• wit_update_work_items_batch: Update work items in batch.
• wit_work_items_link: Link work items together in batch.

• wit_add_child_work_item: Replaced by wit_add_child_work_items to allow creating one or more child items per call.
• wit_close_and_link_workitem_duplicates: This tool is no longer needed. Finding and marking duplicates can be done with other tools.

• repo_list_repos_by_project: Retrieve a list of repositories for a given project.
• repo_list_pull_requests_by_repo: Retrieve a list of pull requests for a given repository.
• repo_list_pull_requests_by_project: Retrieve a list of pull requests for a given project ID or name.
• repo_list_branches_by_repo: Retrieve a list of branches for a given repository.
• repo_list_my_branches_by_repo: Retrieve a list of your branches for a given repository ID.
• repo_list_pull_requests_by_commits: List pull requests associated with commits.
• repo_list_pull_request_threads: Retrieve a list of comment threads for a pull request.
• repo_list_pull_request_thread_comments: Retrieve a list of comments in a pull request thread.
• repo_get_repo_by_name_or_id: Get the repository by project and repository name or ID.
• repo_get_branch_by_name: Get a branch by its name.
• repo_get_pull_request_by_id: Get a pull request by its ID.
• repo_create_pull_request: Create a new pull request.
• repo_update_pull_request_status: Update the status of an existing pull request to active or abandoned.
• repo_update_pull_request_reviewers: Add or remove reviewers for an existing pull request.
• repo_reply_to_comment: Replies to a specific comment on a pull request.
• repo_resolve_comment: Resolves a specific comment thread on a pull request.
• repo_search_commits: Searches for commits.
• repo_create_pull_request_thread: Creates a new comment thread on a pull request.

• build_get_definitions: Retrieve a list of build definitions for a given project.
• build_get_definition_revisions: Retrieve a list of revisions for a specific build definition.
• build_get_builds: Retrieve a list of builds for a given project.
• build_get_log: Retrieve the logs for a specific build.
• build_get_log_by_id: Get a specific build log by log ID.
• build_get_changes: Get the changes associated with a specific build.
• build_run_build: Trigger a new build for a specified definition.
• build_get_status: Fetch the status of a specific build.
• build_update_build_stage: Update the stage of a specific build.

• release_get_definitions: Retrieve a list of release definitions for a given project.
• release_get_releases: Retrieve a list of releases for a given project.

• testplan_create_test_plan: Create a new test plan in the project.
• testplan_create_test_case: Create a new test case work item.
• testplan_add_test_cases_to_suite: Add existing test cases to a test suite.
• testplan_list_test_plans: Retrieve a paginated list of test plans from an Azure DevOps project. Allows filtering for active plans and toggling detailed information.
• testplan_list_test_cases: Get a list of test cases in the test plan.
• testplan_show_test_results_from_build_id: Get a list of test results for a given project and build ID.

• search_code: Get code search results for a given search text.
• search_wiki: Get wiki search results for a given search text.
• search_workitem: Get work item search results for a given search text.

Clone the repository, install dependencies, and add it to your MCP client configuration.

VS Code and GitHub Copilot
Visual Studio 2022 and GitHub Copilot

For the best experience, use Visual Studio Code and GitHub Copilot.

1. Install VS Code or VS Code Insiders
2. Install Node.js 20+
3. Install Azure CLI
4. Open VS Code in an empty folder

Ensure you are logged in to Azure DevOps via the Azure CLI:

az login

After installation, select GitHub Copilot Agent Mode and refresh the tools list. Learn more about Agent Mode in the VS Code Documentation.

This installation method is the easiest for all users of Visual Studio Code.

🎥 Watch this quick start video to get up and running in under two minutes!

1. In your project, add a .vscode\mcp.json file with the following content:

{
  "inputs": [
    {
      "id": "ado_org",
      "type": "promptString",
      "description": "Azure DevOps organization name  (e.g. 'contoso')"
    }
  ],
  "servers": {
    "ado": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@azure-devops/mcp", "${input:ado_org}"]
    }
  }
}

2. Save the file, then click 'Start'.

3. In chat, switch to Agent Mode.
4. Click "Select Tools" and choose the available tools.
5. We strongly recommend creating a .github\copilot-instructions.md in your project and copying the contents from this copilot-instructions.md file. This will enhance your experience using the Azure DevOps MCP Server with GitHub Copilot Chat.

This installation method is recommended for advanced users and contributors who want immediate access to the latest updates from the main branch. It is ideal if you are developing new tools, enhancing existing features, or maintaining a custom fork.

Note: For most users, installing from the public feed is simpler and preferred. Use the source installation only if you need the latest changes or are actively contributing to the project.

1. Clone the repository.
2. Install dependencies:

npm install

3. Edit or add .vscode/mcp.json:

{
  "inputs": [
    {
      "id": "ado_org",
      "type": "promptString",
      "description": "Azure DevOps organization's name  (e.g. 'contoso')"
    }
  ],
  "servers": {
    "ado": {
      "type": "stdio",
      "command": "mcp-server-azuredevops",
      "args": ["${input:ado_org}"]
    }
  }
}

4. Start the Azure DevOps MCP Server.

5. In chat, switch to Agent Mode.
6. Click "Select Tools" and choose the available tools.
7. We strongly recommend creating a .github\copilot-instructions.md in your project and copying the contents from this copilot-instructions.md file. This will help you get the best experience using the Azure DevOps MCP Server in GitHub Copilot Chat.

See the How To section for details.

For the best experience, use Visual Studio Code and GitHub Copilot 👆.

1. Install VS Studio 2022 version 17.14 or later
2. Install Azure CLI
3. Open a project in Visual Studio.

Ensure you are logged in to Azure DevOps via the Azure CLI:

az login

This installation method is the easiest for all users of Visual Studio 2022.

🎥 Watch this quick start video to get up and running in under two minutes!

1. Add a .mcp.json file to the solution folder with the following content:

{
  "inputs": [
    {
      "id": "ado_org",
      "type": "promptString",
      "description": "Azure DevOps organization name  (e.g. 'contoso')"
    }
  ],
  "servers": {
    "ado": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@azure-devops/mcp", "${input:ado_org}"]
    }
  }
}

2. Save the file.

3. Add your organization name by clicking on the input option.

   

4. Open Copilot chat and switch to Agent Mode.

5. Click the "Tools" icon and choose the available tools.

   

6. We strongly recommend creating a .github\copilot-instructions.md in your project and copying the contents from this copilot-instructions.md file. This will enhance your experience using the Azure DevOps MCP Server with GitHub Copilot Chat.

1. Open GitHub Copilot in VS Code and switch to Agent mode.
2. Start the Azure DevOps MCP Server.
3. The server appears in the tools list.
4. Try prompts like "List ADO projects".

Prerequisites: Visual Studio 2022 v17.14+, Agent mode enabled in Tools > Options > GitHub > Copilot > Copilot Chat.

1. Switch to Agent mode in the Copilot Chat window.
2. Enter your Azure DevOps organization name.
3. Select desired ado tools.
4. Try prompts like "List ADO projects".

For more details, see Visual Studio MCP Servers documentation and the Getting Started Video.

See the Troubleshooting guide for help with common issues and logging.

Find sample prompts and best practices in our How-to Guide.

For answers to common questions about the Azure DevOps MCP Server, see the Frequently Asked Questions.

We welcome contributions! During preview, please file issues for bugs, enhancements, or documentation improvements.

See our Contributions Guide for:

• 🛠️ Development setup
• ✨ Adding new tools
• 📝 Code style & testing
• 🔄 Pull request process

This project follows the Microsoft Open Source Code of Conduct. For questions, see the FAQ or contact open@microsoft.com.

Thanks to all contributors who make this project awesome! ❤️

Generated with contrib.rocks

Licensed under the MIT License.

Trademarks: This project may include trademarks or logos for Microsoft or third parties. Use of Microsoft trademarks or logos must follow Microsoft’s Trademark & Brand Guidelines. Third-party trademarks are subject to their respective policies.