Ado MCP Server C285dae3

MCP运维云端

提供方 cakriwut · 包名 @smithery/cli

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

提供与Azure DevOps的集成服务,允许Cline和Roo Code与Azure DevOps服务交互。

一句话选型结论

按资料字段整理

Ado MCP Server C285dae3 属于运维云端类 MCP 服务器,stdio · 本地进程,Token,可直接接入 Claude、Cline,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

支持客户端

适用场景

AzureDevOpsTypeScript本地部署集成服务开发工具项目管理CI/CD

安装与配置

stdio · 本地进程 Token
客户端在本机拉起子进程,数据不出本机
npx -y @smithery/cli install @cakriwut/ado-mcp-server --client claude

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

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

    连接成功后客户端会列出约 29 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

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

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

部署与发布

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

监控与告警

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

选择建议

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

值得选的地方

  • 资料标注 29 个工具,覆盖面较广,能满足多种调用。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cline,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Ado MCP Server C285dae3当前 29 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

服务器档案

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

详细介绍

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

Azure DevOps MCP (ADO-MCP-Server) for Cline

This Model Context Protocol (MCP) server provides integration with Azure DevOps, allowing Cline and Roo Code to interact with Azure DevOps services.

The project repository is located at: https://github.com/cakriwut/ado-mcp-server

Prerequisites

  • Node.js (v20 LTS or higher)
  • npm (comes with Node.js)
  • A Cline installation
  • Azure DevOps account with access tokens

Installation

Installing via Smithery

To install Azure DevOps MCP Server (ADO-MCP-Server) automatically via Smithery:```bash
npx -y @smithery/cli install @cakriwut/ado-mcp-server --client claude


### Manual Installation
1. Clone this repository:```bash
git clone https://github.com/cakriwut/ado-mcp-server.git
cd ado-mcp-server
  1. Install dependencies:```bash
    npm install

3. Build the server:```bash
npm run build

Note: The build output (build/ directory) is not included in version control. You must run the build command after cloning the repository.

Configuration

1. Get Azure DevOps Personal Access Token (PAT)

  1. Go to Azure DevOps and sign in
  2. Click on your profile picture in the top right
  3. Select "Security"
  4. Click "New Token"
  5. Give your token a name and select the required scopes:
    - Code (read, write) - For Pull Request operations
    - Work Items (read, write) - For Work Item management
    - Build (read, execute) - For Pipeline operations
    - Wiki (read, write) - For Wiki operations
    - Project and Team (read) - For Project and Board information
  6. Copy the generated token

2. Configure MCP Settings

Add the server configuration to your MCP settings file:

For Roo Code (VSCode extension)

Configuration file location: %APPDATA%/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json

For Cline Desktop App

Configuration file location: %LOCALAPPDATA%/Claude/claude_desktop_config.json

Add the following configuration to the mcpServers object:```json
{
"mcpServers": {
"azure-devops-mcp-server": {
"command": "node",
"args": ["C:/absolute/path/to/ado-mcp-server/build/index.js"],
"env": {
"AZURE_DEVOPS_ORG": "your-organization",
"AZURE_DEVOPS_PAT": "your-personal-access-token",
"AZURE_DEVOPS_PROJECT": "your-project-name"
},
"disabled": false,
"autoApprove": []
}
}
}


Replace the following values:
- `C:/absolute/path/to/ado-mcp-server`: The absolute path to where you cloned this repository (use forward slashes)
- `your-organization`: Your Azure DevOps organization name
- `your-project-name`: Your Azure DevOps project name
- `your-personal-access-token`: The PAT you generated in step 1

#### Important Notes for Windows Users
- Use forward slashes (/) in the path, not backslashes (\)
- Provide the full absolute path to the build/index.js file
- Restart Roo Code or Cline after making changes to the configuration

## Available Tools

### Work Items
- `get_work_item`: Get a work item by ID
- `list_work_items`: Query work items using WIQL
- `create_work_item`: Create a new work item (Bug, Task, User Story)
- `update_work_item`: Update an existing work item
- `search_work_items`: Search for work items using text search
- `add_work_item_comment`: Add a comment to a work item
- `get_work_item_comments`: Get comments from a work item

### Boards
- `get_boards`: Get available boards in the project

### Pipelines
- `list_pipelines`: List all pipelines in the project
- `trigger_pipeline`: Execute a pipeline

### Pull Requests
- `list_pull_requests`: List pull requests
- `create_pull_request`: Create a new pull request
- `update_pull_request`: Update a pull request

### Wiki
- `get_wikis`: List all wikis in the project
- `list_wiki_pages`: List pages in a wiki
- `get_wiki_page`: Get a wiki page by path
- `create_wiki`: Create a new wiki
- `update_wiki_page`: Create or update a wiki page
- `create_wiki_page`: Create a new wiki page
- `search_wiki_page`: Search for pages in a wiki by text

### Projects
- `list_projects`: List all projects in the Azure DevOps organization

## Command Line Interface (CLI)

ADO-MCP-Server includes a command-line interface that allows you to interact with Azure DevOps directly from the terminal. The CLI is available as `azure-devops-cli` after building the project.

### Environment Setup

Before using the CLI, set up your environment variables:```powershell
# PowerShell
$env:AZURE_DEVOPS_ORG = "your-organization"
$env:AZURE_DEVOPS_PROJECT = "your-project-name"
$env:AZURE_DEVOPS_PAT = "your-personal-access-token"

Common CLI Commands

Work Items```powershell

Get a work item by ID

node .\build\cli\index.js work-item get -i 42

Search for work items

node .\build\cli\index.js work-item search -s "bug"

Create a new task

node .\build\cli\index.js work-item create -t "Task" -d '[{"op":"add","path":"/fields/System.Title","value":"New Task"}]'

Add a comment to a work item

node .\build\cli\index.js work-item add-comment -i 42 -t "This is a comment added via CLI"

Get comments from a work item

node .\build\cli\index.js work-item get-comments -i 42


#### Wiki```powershell
# List all wikis in the project
node .\build\cli\index.js wiki list

# Get a wiki page
node .\build\cli\index.js wiki page -w <wikiIdentifier> -p "/path/to/page" --include-content

# Search wiki pages
node .\build\cli\index.js wiki search -w <wikiIdentifier> -s "search term"

For more detailed CLI usage examples, see docs/wiki-cli-usage.md and docs/command-list.md.

Verification

  1. Restart Cline (or VSCode) after adding the configuration
  2. The Azure DevOps MCP server should now be listed in Cline's capabilities
  3. You can verify the installation using the MCP Inspector:```bash
    npm run inspector

## Troubleshooting

1. If the server isn't connecting:
   - Check that the path in your MCP settings is correct
   - Verify your Azure DevOps credentials
   - Check the Cline logs for any error messages

2. If you get authentication errors:
   - Verify your PAT hasn't expired
   - Ensure the PAT has all necessary scopes
   - Double-check the organization and project names

3. For other issues:
   - Run the inspector tool to verify the server is working correctly
   - Check the server logs for any error messages

## Development

To modify or extend the server:

1. Make your changes in the `src` directory
2. Run `npm run watch` for development
3. Build with `npm run build` when ready
4. Test using the inspector: `npm run inspector`

## Testing

The project includes test scripts for all MCP Server Commands. These tests help verify that the server can communicate with Azure DevOps correctly.

### Prerequisites for Testing

1. Make sure you have a valid `.env` file in the root directory with the following variables:```
   AZURE_DEVOPS_ORG=your-organization
   AZURE_DEVOPS_PROJECT=your-project
   AZURE_DEVOPS_PAT=your-personal-access-token
   ```

2. Install dependencies:```
   npm install
   ```

### Running Tests

#### Quick Tests

For a quick test of your Azure DevOps connection:```bash
npm run test:quick

This runs a simple JavaScript test that only tests the list_projects command.

For a more comprehensive test of all MCP Server Commands:```bash
npm run test:simple


This runs a simple JavaScript test that tests all the main commands in one file.

#### TypeScript Tests

To run all TypeScript tests:```bash
npm test

To run tests for specific command categories:bash npm run test:work-item # Test Work Item Tools npm run test:board # Test Board Tools npm run test:wiki # Test Wiki Tools npm run test:project # Test Project Tools npm run test:pipeline # Test Pipeline Tools npm run test:pull-request # Test Pull Request Tools

See the tests/README.md file for more information about the tests.

License

MIT License - See LICENSE for details

常见问题

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

在客户端按下面的安装命令接入:npx -y @smithery/cli install @cakriwut/ado-mcp-server --client claude。对应的包名是 @smithery/cli。装完在客户端配置里引用同一个包或端点。

Ado MCP Server C285dae3 怎么在 Claude、Cline 里配置?

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

Ado MCP Server C285dae3 收费吗?

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

Ado MCP Server C285dae3 需要 API Key 吗?

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

Ado MCP Server C285dae3 支持哪些客户端?

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

Ado MCP Server C285dae3 能提供哪些能力?

资料显示约 29 个工具;能力标签包括 Azure DevOps、集成服务、TypeScript、Claude、开发工具。具体工具清单以官方文档为准。

Ado MCP Server C285dae3 需要什么运行环境?

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

Ado MCP Server C285dae3 是本地还是远程?

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

热门专题

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

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