---
title: "Azure DevOps"
description: "List organization projects; List Git repositories in a project; Read one work item."
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Azure DevOps

<p>List organization projects; List Git repositories in a project; Read one work item.</p>

<details data-command-index><summary>What you can do (3)</summary>
<h2>What you can do</h2>
<p>Available commands: 3 (3 read, 0 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/azure-devops#command-azure-devops-projects-list">List organization projects</a> — <code>azure-devops.projects.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/azure-devops#command-azure-devops-repositories-list">List Git repositories in a project</a> — <code>azure-devops.repositories.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/azure-devops#command-azure-devops-workitems-get">Read one work item</a> — <code>azure-devops.workitems.get</code></td>
<td>Read</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/azure-devops">Connect and use</a></p>
<p>Open the integration&#39;s connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for Azure DevOps, then enter the issued values in the connection form below.</p>
<ol>
<li>Register a confidential web application in Microsoft Entra ID, configure its web redirect URI to the Tooluse.net callback shown in the connection and add delegated Azure DevOps user_impersonation permission. An administrator grants consent where required by tenant policy. Enter Azure DevOps organization and the Azure DevOps OAuth client ID/secret (or use an Tooluse.net platform OAuth connection), save and choose Authorize. Tooluse.net uses Entra authorization code with PKCE and offline_access for the Azure DevOps resource, not retired Azure DevOps OAuth registration. The delegated permission is broad: actual project/repository/work-item access remains constrained by the signed-in user, organization policy and selected Tooluse.net read commands. This subset has no pipeline starts, Git writes or work-item edits. To revoke upstream access, remove the app grant or disable the enterprise application in Entra as permitted by your tenant policy; disconnecting Tooluse.net removes the local grant.</li>
</ol>
<p><a href="https://learn.microsoft.com/azure/devops/integrate/get-started/authentication/entra-oauth">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>Azure DevOps organization</td>
<td>Required</td>
</tr>
<tr>
<td>Access token (optional with OAuth)</td>
<td>Optional</td>
</tr>
<tr>
<td>azure-devops OAuth client ID</td>
<td>Optional</td>
</tr>
<tr>
<td>azure-devops OAuth client secret</td>
<td>Optional</td>
</tr>
<tr>
<td>Registered OAuth redirect URI (optional)</td>
<td>Optional</td>
</tr>
<tr>
<td>Return URL after authorization</td>
<td>Optional</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "query": {
      "api-version": "7.1",
      "$top": 10
    }
  }
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-azure-devops-projects-list">
<summary><span>List organization projects — <code>azure-<wbr>devops.<wbr>projects.<wbr>list</code></span></summary>
<p>List organization projects. One explicit request/page; no automatic retries or pagination.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/azure-devops?command=azure-devops.projects.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.api-version</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>const: &quot;7.1&quot;; minLength: 1; maxLength: 1000</code></td>
</tr>
<tr>
<td><code>query.$top</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td><code>minimum: 1; maximum: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/azure-devops/commands/azure-devops.projects.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "api-version": "7.1",
    "$top": 10
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-azure-devops-repositories-list">
<summary><span>List Git repositories in a project — <code>azure-<wbr>devops.<wbr>repositories.<wbr>list</code></span></summary>
<p>List Git repositories in a project. One explicit request/page; no automatic retries or pagination.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/azure-devops?command=azure-devops.repositories.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.project</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1; maxLength: 128</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.api-version</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>const: &quot;7.1&quot;; minLength: 1; maxLength: 1000</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/azure-devops/commands/azure-devops.repositories.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "project": "demo-project"
  },
  "query": {
    "api-version": "7.1"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-azure-devops-workitems-get">
<summary><span>Read one work item — <code>azure-<wbr>devops.<wbr>workitems.<wbr>get</code></span></summary>
<p>Read one work item. One explicit request/page; no automatic retries or pagination.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/azure-devops?command=azure-devops.workitems.get">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1; maxLength: 1000; pattern: &quot;^[0-9]+$&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.api-version</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>const: &quot;7.1&quot;; minLength: 1; maxLength: 1000</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/azure-devops/commands/azure-devops.workitems.get">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  },
  "query": {
    "api-version": "7.1"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://learn.microsoft.com/azure/devops/integrate/get-started/authentication/entra-oauth">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/azure-devops/index.mdx