Azuredevops MCP Abc071c4

MCP运维云端

提供方 techsouvik

运维云端 stdio · 本地进程 Token 社区 / 第三方 Claude DesktopClaudeCursor
查看接入方式

一个为Azure DevOps提供AI增强工作流管理的后端系统,支持REST和WebSocket API,集成LLM实现智能查询与自动化任务管理。

一句话选型结论

按资料字段整理

Azuredevops MCP Abc071c4 属于运维云端类 MCP 服务器,stdio · 本地进程,Token,可直接接入 Claude Desktop、Claude、Cursor,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式stdio · 本地进程 鉴权Token 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

DevOps自动化JavaScript本地部署AI工作流Azure集成智能查询任务管理

安装与配置

stdio · 本地进程 Token
客户端在本机拉起子进程,数据不出本机
docker run -d \

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Docker,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Azuredevops MCP Abc071c4当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方techsouvik上游标注的维护方 techsouvik
分类运维云端本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Docker本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

16.6 KB
来自项目仓库与上游目录的原文,未做删改

AI-Powered Azure DevOps Assistant (Backend)

A backend system to power conversational, AI-augmented workflows in Azure DevOps. This project provides REST and WebSocket APIs for integrating with Azure DevOps Boards using user-supplied Personal Access Tokens (PAT). AI features can be enabled using LLM providers like OpenRouter.ai or OpenAI.


Table of Contents

  • Architecture
  • Features
  • Getting Started
  • Environment Variables
  • API Reference
  • WebSocket Events
  • Security
  • Deployment
  • License

Architecture

High-Level System Design```

Frontend (Chat UI)
|
v
Backend API <-----> Azure DevOps (PAT)
|
v
AI/LLM Service (OpenRouter, OpenAI, etc.)


### Components

- **Express/Node.js API server:** Exposes REST and Socket.IO endpoints
- **Azure DevOps Integration:** Uses user-supplied Personal Access Token (PAT) per session/request
- **AI Services (Optional):** Connects to LLM providers for natural language queries and workflow recommendations
- **Stateless Backend:** No persistent storage of tokens; all auth handled per request

---

## Features

### Work Item Management
- Create, update, reassign, and describe user stories, issues, and tasks
- Move work items between sprints
- View work item details by ID

### Sprint and Board Views
- Get current sprint status
- Overview of all recent sprints
- List and filter items by sprint, type, and state

### Smart Search &amp; Query
- Search work items by keyword
- Filter by type, state, and sprint
- Find unassigned items, child tasks, and linked bugs

### AI Capabilities
- Ask natural language questions about sprints and backlog
- AI-generated summaries of sprints and boards
- Risk and blocker identification
- Planning focus recommendations

---

## Getting Started

### Prerequisites

- Node.js v14 or higher (for local development)
- npm or yarn
- Docker and Docker Compose (for Docker deployment)
- Azure DevOps organization and project
- Azure DevOps Personal Access Token (PAT) with Work Items read/write permissions
- (Optional) OpenRouter/OpenAI API key for AI features

---

## Installation &amp; Setup

### Option 1: Local Development (Without Docker)

#### Step 1: Clone the Repository```bash
git clone https://github.com/your-username/azure-devops-chatbot-backend.git
cd azure-devops-chatbot-backend

Step 2: Install Dependencies```bash

npm install


#### Step 3: Configure Environment Variables

Copy the example environment file and configure it:```bash
cp .env.example .env

Edit .env file with your configuration:```env

Server Configuration

PORT=3001
NODE_ENV=development
LOG_LEVEL=info

CORS Configuration (optional)

CORS_ORIGIN=*

Azure DevOps Configuration (Optional - can be provided per request via headers)

AZURE_ORG_URL=https://dev.azure.com/your-org
AZURE_PROJECT=your-project-name

Azure DevOps PAT for MCP Server (Required for MCP server only)

AZURE_DEVOPS_PAT=your-azure-devops-personal-access-token

AI Service Configuration (Optional)

OPENROUTER_API_KEY=your-openrouter-api-key
OPENAI_API_KEY=your-openai-api-key

Application URL

APP_URL=http://localhost:3001


&gt; **Important Notes:**
&gt; - For **REST API**: Azure DevOps PAT is provided per request via `Authorization: Bearer ` header
&gt; - For **MCP Server**: `AZURE_DEVOPS_PAT` must be set in `.env` file
&gt; - `AZURE_ORG_URL` and `AZURE_PROJECT` are optional if provided via request headers

#### Step 4: Start the Server

**Start the main API server:**```bash
npm start

The server will run at http://localhost:3001 by default.

Development mode with auto-reload:```bash
npm run dev


**Start the MCP server (separate process):**```bash
npm run mcp

MCP server in development mode:```bash
npm run mcp:dev


#### Step 5: Verify Installation

Check if the server is running:```bash
curl http://localhost:3001/api/health

Expected response:```json
{
"status": "healthy",
"timestamp": "2024-01-15T10:30:00.000Z",
"service": "azure-devops-chatbot-backend"
}


---

### Option 2: Docker Deployment

#### Step 1: Clone the Repository```bash
git clone https://github.com/your-username/azure-devops-chatbot-backend.git
cd azure-devops-chatbot-backend

Step 2: Configure Environment Variables

Create a .env file in the project root:```bash
cp .env.example .env


Edit `.env` with your configuration (see environment variables section below).

#### Step 3: Build and Run with Docker

**Option A: Using Docker Compose (Recommended)**```bash
# Build and start the container
docker-compose up -d

# View logs
docker-compose logs -f

# Stop the container
docker-compose down

Option B: Using Docker directly```bash

Build the Docker image

docker build -t azure-devops-backend .

Run the container

docker run -d \
--name azure-devops-backend \
-p 3001:3001 \
--env-file .env \
-v $(pwd)/logs:/app/logs \
azure-devops-backend

View logs

docker logs -f azure-devops-backend

Stop the container

docker stop azure-devops-backend
docker rm azure-devops-backend


#### Step 4: Verify Installation```bash
curl http://localhost:3001/api/health

Environment Variables

Complete Environment Variables Reference

Create a .env file in the root of your project. You can copy from .env.example:```bash
cp .env.example .env


#### Server Configuration

| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| `PORT` | No | `3001` | Port on which the server will run |
| `NODE_ENV` | No | `development` | Environment mode (`development`, `production`) |
| `LOG_LEVEL` | No | `info` | Logging level (`error`, `warn`, `info`, `debug`) |
| `CORS_ORIGIN` | No | `*` | CORS allowed origins (use `*` for all, or specific domain) |
| `APP_URL` | No | `http://localhost:3001` | Application URL (used for OpenRouter API) |

#### Azure DevOps Configuration

| Variable | Required | Description |
|----------|----------|-------------|
| `AZURE_ORG_URL` | Optional* | Azure DevOps organization URL (e.g., `https://dev.azure.com/your-org`) |
| `AZURE_PROJECT` | Optional* | Azure DevOps project name |
| `AZURE_DEVOPS_PAT` | Required for MCP | Azure DevOps Personal Access Token (required for MCP server) |

&gt; **Note:**
&gt; - For **REST API**: `AZURE_ORG_URL` and `AZURE_PROJECT` can be provided via request headers (`x-org-url`, `x-project`) or environment variables
&gt; - For **REST API**: PAT is provided per request via `Authorization: Bearer ` header
&gt; - For **MCP Server**: `AZURE_DEVOPS_PAT`, `AZURE_ORG_URL`, and `AZURE_PROJECT` must be set in environment variables

#### AI Service Configuration (Optional)

| Variable | Required | Description |
|----------|----------|-------------|
| `OPENROUTER_API_KEY` | Optional | OpenRouter API key for AI features |
| `OPENAI_API_KEY` | Optional | OpenAI API key for AI features |

&gt; **Note:** AI API keys can also be provided per request in the request body for REST API endpoints.

### Environment Variables by Use Case

#### For REST API Only (No MCP)```env
PORT=3001
NODE_ENV=development
LOG_LEVEL=info

# Optional: Default values (can be overridden via headers)
AZURE_ORG_URL=https://dev.azure.com/your-org
AZURE_PROJECT=your-project-name

# Optional: AI features
OPENROUTER_API_KEY=your-key
OPENAI_API_KEY=your-key

Note: PAT is provided per request via Authorization header.

For MCP Server Only```env

PORT=3001
NODE_ENV=development

Required for MCP Server

AZURE_DEVOPS_PAT=your-azure-devops-pat
AZURE_ORG_URL=https://dev.azure.com/your-org
AZURE_PROJECT=your-project-name

Optional: AI features

OPENROUTER_API_KEY=your-key
OPENAI_API_KEY=your-key


#### For Both REST API and MCP Server```env
PORT=3001
NODE_ENV=development
LOG_LEVEL=info
CORS_ORIGIN=*
APP_URL=http://localhost:3001

# Required for MCP Server, optional defaults for REST API
AZURE_DEVOPS_PAT=your-azure-devops-pat
AZURE_ORG_URL=https://dev.azure.com/your-org
AZURE_PROJECT=your-project-name

# Optional: AI features
OPENROUTER_API_KEY=your-key
OPENAI_API_KEY=your-key

Creating Azure DevOps PAT

  1. Go to Azure DevOps: https://dev.azure.com/{your-org}
  2. Click on your profile picture → Security
  3. Click Personal access tokens → + New Token
  4. Configure the token:
    - Name: Azure DevOps Assistant
    - Organization: Select your organization
    - Expiration: Set appropriate expiration
    - Scopes: Select Work Items (Read & Write)
  5. Click Create and copy the token (you won't see it again)

Running the Services

Main API Server

The main API server provides REST endpoints and WebSocket support.

Start:```bash
npm start


**Development mode:**```bash
npm run dev

With Docker:```bash
docker-compose up -d


### MCP Server

The MCP server runs as a separate process for integration with AI assistants.

**Start:**```bash
npm run mcp

Development mode:```bash
npm run mcp:dev


&gt; **Note:** The MCP server communicates via stdio and is typically launched by MCP-compatible clients (Claude Desktop, Cursor, etc.) rather than run directly. See docs.md for client integration instructions.

---

## Quick Start Examples

### Local Development```bash
# 1. Clone and install
git clone &lt;repository-url&gt;
cd azure-devops-chatbot-backend
npm install

# 2. Configure environment
cp .env.example .env
# Edit .env with your values

# 3. Start the server
npm run dev

# 4. Test the API
curl http://localhost:3001/api/health

Docker Deployment```bash

1. Clone repository

git clone <repository-url>
cd azure-devops-chatbot-backend

2. Configure environment

cp .env.example .env

Edit .env with your values

3. Start with Docker Compose

docker-compose up -d

4. Check logs

docker-compose logs -f

5. Test the API

curl http://localhost:3001/api/health


### Testing API Endpoints```bash
# Health check (no auth required)
curl http://localhost:3001/api/health

# Get work item (requires PAT in header)
curl http://localhost:3001/api/workitems/12345 \
  -H &quot;Authorization: Bearer &lt;your-pat&gt;&quot; \
  -H &quot;x-org-url: https://dev.azure.com/your-org&quot; \
  -H &quot;x-project: your-project&quot;

API Reference

All endpoints require Authorization: Bearer in headers unless otherwise stated.

Health Check

Method Endpoint Description
GET /api/health Check API health

Work Item APIs

Method Endpoint Description Parameters
POST /api/workitems Create a new work item type, title, description, sprint
GET /api/workitems/:id Get details of a work item by ID id
PATCH /api/workitems/:id/state Update the state of a work item id, newState
PATCH /api/workitems/:id/sprint Move work item to another sprint id, sprintId
GET /api/workitems List/filter/search all work items type, sprint, state, keywords
GET /api/workitems/:id/children List child tasks for a work item id
GET /api/workitems/:id/linked-bugs List bugs linked to a work item id

Sprint APIs

Method Endpoint Description Parameters
GET /api/sprints/current Get a summary of the current sprint -
GET /api/sprints View an overview of all sprints -
GET /api/sprints/:sprintId/items List items in a specific sprint sprintId, type

Search and Query APIs

Method Endpoint Description Parameters
GET /api/search Search work items using keywords query, type, state, sprint

Unassigned Queries

Method Endpoint Description
GET /api/workitems/unassigned/todo List unassigned items in "To Do" state

AI-Powered APIs

Method Endpoint Description Body Parameters
POST /api/ai/query NLP/Natural language queries question, context, openrouter_api_key (optional)
POST /api/ai/summarize AI-powered Sprint/Board summary scope, id, openrouter_api_key (optional)
POST /api/ai/suggestions/risks AI-generated risk identification sprintId (optional), openrouter_api_key (optional)
POST /api/ai/suggestions/focus AI recommendations for planning/focus context, openrouter_api_key (optional)

> Note: For AI endpoints, you may include an openrouter_api_key in the POST body for per-user/provider LLM selection.


WebSocket Events (Socket.IO)

The backend provides real-time communication via Socket.IO at /socket.io.

Client → Server Events

  • authenticate – Send PAT and optional AI key for session
  • chat_message – Send chat messages
  • devops_action – Trigger work item/sprint actions
  • ai_query – Send natural language/AI queries

Server → Client Events

  • response – Response to actions/queries in real time
  • error – Error/event reporting
  • status_update – Progress updates for long-running operations

Security

  • No persistent storage of PATs or AI keys; all tokens are in-memory/stateless per session
  • All operations are performed using the user's supplied PAT (principle of least privilege)
  • PAT should be scoped to Work Items (read/write only)
  • Use HTTPS/TLS for production deployments
  • Validate and sanitize all user inputs
  • Rate limiting recommended for production

Deployment

Supported Platforms

  • Azure App Service
  • AWS EC2 / Elastic Beanstalk
  • Google Cloud Platform
  • Vercel
  • Heroku
  • Docker
  • Any Node.js-compatible platform

Docker Deployment

See Installation & Setup section above for detailed Docker instructions.

Quick Docker commands:```bash

Using Docker Compose (recommended)

docker-compose up -d

Using Docker directly

docker build -t azure-devops-backend .
docker run -d -p 3001:3001 --env-file .env --name azure-devops-backend azure-devops-backend


### Environment Configuration

All configuration should use environment variables. Never hardcode secrets. See Environment Variables section for complete reference.

---

## Project Structure```
azure-devops-chatbot-backend/
├── src/
│   ├── routes/
│   │   ├── workitems.js
│   │   ├── sprints.js
│   │   ├── search.js
│   │   └── ai.js
│   ├── services/
│   │   ├── azureDevOps.js
│   │   └── aiService.js
│   ├── middleware/
│   │   ├── auth.js
│   │   └── errorHandler.js
│   ├── mcp/
│   │   └── server.js
│   ├── utils/
│   │   ├── logger.js
│   │   └── helpers.js
│   └── index.js
├── .env
├── .gitignore
├── package.json
├── docs.md
└── README.md

License

MIT License


Contributing

Pull requests are welcome! For major changes, please open an issue first to discuss what you would like to change.


Support

For issues or questions, please open a GitHub issue or contact the maintainers.


Notes

  • This backend is designed for a chat-based frontend UI where users input their PAT directly
  • APIs and sockets are stateless and secure
  • To enable AI features, supply an OpenRouter/OpenAI API key via frontend or environment
  • The backend does not store any user credentials or tokens persistently

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Azuredevops MCP Abc071c4 怎么安装?

在客户端按下面的安装命令接入:docker run -d \。装完在客户端配置里引用同一个包或端点。

Azuredevops MCP Abc071c4 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Azuredevops MCP Abc071c4 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Azuredevops MCP Abc071c4 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Azuredevops MCP Abc071c4 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Azuredevops MCP Abc071c4 能提供哪些能力?

资料显示能力标签包括 JavaScript、Claude、AI工作流。具体工具清单以官方文档为准。

Azuredevops MCP Abc071c4 需要什么运行环境?

运行时为 Docker;属于本地进程,需要在本机装好运行环境。

Azuredevops MCP Abc071c4 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。