Azure DevOps icon

CONNECT APP

Build with Azure DevOps

Plan smarter, collaborate better, and ship faster with a set of modern dev services

Infrastructure & Cloud

  • OAuth

MCP

Give your agent Azure DevOps tools

Every Azure DevOps action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Azure DevOps account for each tool call — you store no tokens.

// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
  new URL("https://remote.mcp.pipedream.net/v3"),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "x-pd-project-id": "{project_id}",
        "x-pd-environment": "production",
        "x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
        "x-pd-app-slug": "azure_devops",
      },
    },
  },
)

const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)

const { tools } = await mcp.listTools()

// e.g. run Add Pull Request Reviewer:
const result = await mcp.callTool({
  name: "azure_devops-add-pull-request-reviewer",
  arguments: {
    organization: "Organization",
    project: "Project",
  },
})

API PROXY

Call the Azure DevOps API directly

For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Azure DevOps API with the connected user's credentials attached. You store no tokens and write no refresh logic.

const resp = await pd.proxy.get({
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  accountId: "apn_xxxxxxx",
  url: "https://app.vssps.visualstudio.com/_apis/profile/profiles/Me",
})

// Any allowed Azure DevOps endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.

SDK

Run Azure DevOps actions from your backend

Connect a user's Azure DevOps account once, then run Add Pull Request Reviewer on their behalf from your own code — TypeScript, Python, or plain HTTP.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "azure_devops-add-pull-request-reviewer",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    azure_devops: { authProvisionId: "apn_xxxxxxx" },
    organization: "Organization",
    project: "Project",
  },
})

TOOLS

Azure DevOps actions

On-demand operations your product or agent can configure and run on behalf of a connected user.

EVENTS

Azure DevOps triggers

Event sources your backend can deploy for users and receive through a webhook.

REFERENCE

App details

Reference metadata for the Azure DevOps connector in the Pipedream registry.

App slug
azure_devops
Authentication
OAuth
Categories
Infrastructure & Cloud
Actions
73
Triggers
1
API proxy
Available

OAuth scopes

These are the scopes Pipedream's managed Azure DevOps OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.

  • vso.analytics
  • vso.auditlog
  • vso.build_execute
  • vso.code_manage
  • vso.dashboards_manage
  • vso.entitlements
  • vso.extension.data_write
  • vso.extension_manage
  • vso.gallery_manage
  • vso.graph_manage
  • vso.identity_manage
  • vso.loadtest_write
  • vso.machinegroup_manage
  • vso.memberentitlementmanagement_write
  • vso.notification_diagnostics
  • vso.notification_manage
  • vso.packaging_manage
  • vso.profile_write
  • vso.project_manage
  • vso.release_manage
  • vso.serviceendpoint_manage
  • vso.symbols_manage
  • vso.taskgroups_manage
  • vso.test_write
  • vso.threads_full
  • vso.variablegroups_manage
  • vso.wiki_write
  • vso.work_full