azure-devops-mcp-replacement-for-openclaw

# Azure DevOps Skill

Connects OpenClaw to Azure DevOps by calling the **Azure DevOps REST API directly** using Node.js scripts. No MCP server, no npm install — only Node.js built-in modules are used.

---

## Setup

### Required environment variables

| Variable | Description |
|---|---|
| `AZURE_DEVOPS_ORG` | Your org name only — e.g. `contoso` (NOT the full URL) |
| `AZURE_DEVOPS_PAT` | Personal Access Token (see scopes below) |

```bash
export AZURE_DEVOPS_ORG=contoso
export AZURE_DEVOPS_PAT=your-pat-here
```

### Required PAT scopes

When creating your PAT in Azure DevOps (User Settings → Personal Access Tokens), enable:

| PAT scope label | Covers |
|---|---|
| **Work Items – Read** (vso.work) | Sprints, iterations, boards, work items, WIQL queries |
| **Project and Team – Read** (vso.project) | Projects list, teams list |
| **Code – Read** (vso.code) | Repos, pull requests |
| **Build – Read** (vso.build) | Pipelines, builds |
| **Test Management – Read** (vso.test) | Test plans, suites |
| **Wiki – Read & Write** (vso.wiki) | Wiki pages |

> ⚠️ "Team Dashboard" scope does NOT cover sprints or iterations. You need **Work Items – Read** for those.

---

## ADO Hierarchy Reference

Understanding the hierarchy avoids 401 errors:

```
Organization  (AZURE_DEVOPS_ORG)
  └── Project          e.g. "B2B Pharmacy Mob"
        └── Team       e.g. "B2B_New_Design"   ← teams live inside projects
              └── Sprint/Iteration  e.g. "F09-03 T26-03-26"
                    └── Work Items (User Stories, Bugs, Tasks…)
```

- **Teams** are NOT sub-projects. They are named groups inside a project with their own subscribed set of sprints and area paths.
- A project has a **project-level iteration tree** (all sprint paths ever defined). Each team subscribes to a subset of those paths.
- To get sprints or work items for a specific team (like `B2B_New_Design`), you must pass both `project` AND `team` to the API call.

---

## External Endpoints

| Endpoint | Used by |
|---|---|...

# azure-devops — OpenClaw Skill

> Interact with Azure DevOps from OpenClaw. No MCP required — pure REST API via Node.js built-ins.

## What it does

- 📁 **Projects & Teams** — list projects, teams, and sprint iterations
- 🗂️ **Work Items** — list, get, create, update, query via WIQL, view current sprint
- 🔀 **Repos & PRs** — list repos, get repo details, browse pull requests
- 🚀 **Pipelines & Builds** — list pipelines, view runs, inspect builds
- 📖 **Wikis** — list wikis, read and write pages
- 🧪 **Test Plans** — list test plans and suites

## Requirements

- Node.js 18+
- An Azure DevOps organization
- A Personal Access Token (PAT)

## Setup

### 1. Create a PAT

Go to `https://dev.azure.com/<your-org>/_usersSettings/tokens` and create a token with these scopes:

- Work Items: Read & Write
- Code: Read
- Build: Read
- Release: Read
- Test Management: Read
- Wiki: Read & Write
- Project and Team: Read

### 2. Configure environment

```bash
export AZURE_DEVOPS_ORG=contoso
export AZURE_DEVOPS_PAT=your_pat_here
```

Or via `~/.openclaw/openclaw.json`:

```json
{
  "skills": {
    "entries": {
      "azure-devops": {
        "enabled": true,
        "env": {
          "AZURE_DEVOPS_ORG": "contoso",
          "AZURE_DEVOPS_PAT": "your_pat_here"
        }
      }
    }
  }
}
```

### 3. Install

```bash
clawhub install azure-devops
```

Or manually:

```bash
cp -r azure-devops/ ~/.openclaw/skills/
```

No `npm install` needed — all scripts use Node.js built-in `https`.

## Usage Examples

```
List my ADO projects
Show work items in the Contoso project
Get current sprint for team "Backend" in project "Contoso"
Create a bug titled "Login page 500 error" in project "Contoso"
List repos in the Contoso project
Show open pull requests in repo "backend-api"
List pipelines in project "Contoso"
Get the wiki page /Architecture/Overview from the Contoso wiki
```

## Script Reference

| Script | Commands |
|---|---|
| `scripts/projects.js` | `list`, `get <project>` |
| `scripts...