Get started free
All integrations

Azure DevOps integration

Azure DevOps REST API for managing projects, repositories, pipelines, work items, and builds. Create and track work items, trigger CI/CD pipelines, manage Git repositories, and coordinate software development workflows.

29 toolsOAuthAPI docs

Common Azure DevOps use cases

  • automate release management
  • checking run status
  • searching work items
  • checking build status
  • merging pull requests
  • automating PR creation
  • cleaning up work items
  • listing CI/CD pipelines
  • monitoring build status
  • triggering CI/CD builds

What you can do with Azure DevOps

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Work item, 6 operations

  • POSTcreate_work_item

    Creates a new work item (Bug, Task, User Story, Epic, etc.) using JSON Patch operations.

  • DELETEdelete_work_item

    Deletes a work item, moving it to the recycle bin or permanently destroying it.

  • GETget_work_item

    Gets a single work item with all its fields, relations, and history.

  • GETlist_work_items_by_ids

    Retrieves multiple work items by their IDs in a single batch request. Returns fields, relations, and links as specified.

  • POSTquery_work_items_wiql

    Executes a WIQL query to search and filter work items. Returns matching work item IDs for batch fetching.

  • PATCHupdate_work_item

    Updates fields on an existing work item using JSON Patch operations.

Pipeline, 5 operations

  • GETget_pipeline

    Gets details of a specific pipeline including its configuration and folder.

  • GETget_pipeline_run

    Gets details of a specific pipeline run including state, result, and timing.

  • GETlist_pipeline_runs

    Lists all runs for a specific pipeline with their status and results.

  • GETlist_pipelines

    Lists all pipelines defined in an Azure DevOps project.

  • POSTrun_pipeline

    Triggers a pipeline run with optional branch, variables, and template parameters.

Pull request, 4 operations

  • POSTcreate_pull_request

    Creates a new pull request from a source branch to a target branch with title and optional reviewers.

  • GETget_pull_request

    Gets details of a specific pull request including status, reviewers, and merge info.

  • GETlist_pull_requests

    Lists pull requests in a Git repository with filters for status, creator, and target branch.

  • PATCHupdate_pull_request

    Updates a pull request's title, description, status, or merge options. Set status to 'completed' to merge.

Build, 3 operations

  • GETget_build

    Gets details of a specific build including status, result, timeline, and source info.

  • GETlist_builds

    Lists builds in a project with filtering by status, result, definition, and branch.

  • POSTqueue_build

    Queues a new build for a specified build definition with optional branch and parameters.

Project, 3 operations

  • POSTcreate_project

    Creates a new team project in the Azure DevOps organization. Returns an operation reference for tracking creation progress.

  • GETget_project

    Gets details of a specific Azure DevOps project including name, description, state, and capabilities.

  • GETlist_projects

    Lists all team projects in the Azure DevOps organization. Returns project name, ID, state, visibility, and last update time.

Repository, 3 operations

  • POSTcreate_repository

    Creates a new empty Git repository in the specified Azure DevOps project.

  • GETget_repository

    Gets details of a specific Git repository including default branch, size, and URLs.

  • GETlist_repositories

    Lists all Git repositories in a specified Azure DevOps project.

Release, 2 operations

  • POSTcreate_release

    Create a new release from a release definition

  • GETlist_releases

    List releases in a project.

Branch, 1 operation

  • GETlist_branches

    List Git branches and refs in a repository, optionally filtered by prefix.

Commit, 1 operation

  • GETget_commits

    Get commits from a Git repository, optionally filtered by path

Complete pull request, 1 operation

  • PATCHcomplete_pull_request

    Complete (merge) a pull request by setting its status to completed

Use Azure DevOps from Claude Code, Cursor or Codex

Connect Azure DevOps in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Azure DevOps operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Azure DevOps

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Azure DevOps once

    Add your Azure DevOps connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Azure DevOps integration FAQ

What can you do with the Azure DevOps integration?
LiveContext exposes 29 operations on Azure DevOps, covering work item, pipeline, pull request and build. Common uses include automate release management, checking run status and searching work items.

Popular integrations

Browse the whole catalog