Azure DevOps MCP Server with PAT Authentication

Azure DevOps MCP Server with PAT Authentication

Enables interaction with Azure DevOps services through Personal Access Token authentication. Provides 75 tools for managing work items, builds, repositories, pull requests, and other DevOps operations via both CLI and HTTP API interfaces.

Category
访问服务器

README

Azure DevOps MCP Server with PAT Authentication

A Model Context Protocol (MCP) server for Azure DevOps that uses Personal Access Token (PAT) authentication instead of Azure CLI. This server provides both CLI and HTTP API interfaces for interacting with Azure DevOps services.

Deploy to Render

✨ Features

  • 🔑 PAT Authentication: Uses Personal Access Tokens instead of Azure CLI
  • 🌐 HTTP API: REST API endpoints for web applications
  • 📡 MCP Protocol: Full Model Context Protocol support
  • 🚀 Deploy Ready: Configured for Render.com deployment
  • 🛠️ 75 Tools: Comprehensive Azure DevOps functionality

🏗️ Architecture

This server provides two interfaces:

  1. CLI Interface (src/index.ts) - Traditional MCP server via stdin/stdout
  2. Web Interface (src/server-web.ts) - HTTP REST API for web deployment

🔧 Available Tools (75 Total)

Work Items (19 tools)

  • wit_get_work_item - Get work item by ID
  • wit_create_work_item - Create new work item
  • wit_update_work_item - Update work item fields
  • wit_my_work_items - Get user's assigned work items
  • wit_add_work_item_comment - Add comments
  • wit_list_backlogs - List team backlogs
  • wit_link_work_item_to_pull_request - Link work items to PRs
  • And 12 more...

Builds (9 tools)

  • build_get_builds - List builds
  • build_run_build - Trigger new build
  • build_get_log - Get build logs
  • build_get_status - Check build status
  • And 5 more...

Repositories (18 tools)

  • repo_create_pull_request - Create pull requests
  • repo_list_pull_requests_by_repo - List PRs
  • repo_get_pull_request_by_id - Get PR details
  • repo_list_branches_by_repo - List branches
  • repo_search_commits - Search commits
  • And 13 more...

Search (3 tools)

  • search_code - Search repositories
  • search_wiki - Search wiki pages
  • search_workitem - Search work items

Other Categories

  • Work Management (3 tools): Iterations and teams
  • Releases (2 tools): Release definitions and deployments
  • Wiki (5 tools): Wiki page management
  • Test Plans (6 tools): Test management
  • Core (3 tools): Projects and teams
  • Advanced Security (2 tools): Security alerts

See complete tool list

🚀 Quick Start

Option 1: Deploy to Render.com (Recommended)

  1. Fork this repository
  2. Deploy to Render:
    • Go to render.com
    • Create new Web Service
    • Connect your forked repository
    • Set environment variables (see below)
  3. Set Environment Variables:
    AZURE_DEVOPS_ORG=your-organization-name
    AZURE_DEVOPS_PAT=your-personal-access-token
    
  4. Deploy and get your URL: https://your-service.onrender.com

Option 2: Local Development

# Clone repository
git clone https://github.com/ennuiii/DevOpsMcpPAT.git
cd DevOpsMcpPAT

# Install dependencies
npm install

# Set environment variables
export AZURE_DEVOPS_ORG="your-org"
export AZURE_DEVOPS_PAT="your-pat-token"

# Build and start
npm run build
npm start

# Server will be available at http://localhost:3000

🔑 Environment Variables

Required

Variable Description Example
AZURE_DEVOPS_ORG Your Azure DevOps organization name contoso
AZURE_DEVOPS_PAT Personal Access Token your-token-here

Optional

Variable Description Default
PORT HTTP server port 3000
NODE_ENV Node.js environment production

🎫 Creating a Personal Access Token

  1. Go to Azure DevOps: https://dev.azure.com/{your-organization}
  2. Click User SettingsPersonal Access Tokens
  3. Click "New Token"
  4. Configure scopes:
    • Work Items: Read & Write
    • Code: Read & Write
    • Build: Read & Execute
    • Release: Read, Write & Execute
    • Project and Team: Read
    • Analytics: Read
    • Test Management: Read & Write

📡 API Endpoints

Health & Info

  • GET / - API documentation
  • GET /health - Health check

Tools

  • GET /api/tools - List all available tools
  • POST /api/tools/{toolName} - Call specific tool

MCP Protocol

  • POST /mcp - JSON-RPC 2.0 endpoint

🧪 Example Usage

Get Work Item

curl -X POST https://your-service.onrender.com/api/tools/wit_get_work_item \
  -H "Content-Type: application/json" \
  -d '{"id": 123, "project": "MyProject"}'

List Projects

curl -X POST https://your-service.onrender.com/api/tools/core_list_projects \
  -H "Content-Type: application/json" \
  -d '{}'

Search Code

curl -X POST https://your-service.onrender.com/api/tools/search_code \
  -H "Content-Type: application/json" \
  -d '{"searchText": "function", "project": ["MyProject"]}'

🏗️ Project Structure

├── src/
│   ├── index.ts              # CLI MCP server (PAT auth)
│   ├── server-web.ts         # HTTP server wrapper
│   ├── tools/                # Tool implementations
│   │   ├── workitems.ts     # Work item tools
│   │   ├── builds.ts        # Build tools
│   │   ├── repos.ts         # Repository tools
│   │   └── ...              # Other tool categories
│   ├── prompts.ts           # MCP prompts
│   └── utils.ts             # Utilities
├── package.json             # Dependencies & scripts
├── tsconfig.json           # TypeScript config
├── render.yaml             # Render deployment config
├── Dockerfile              # Container config
└── README.md               # This file

🔄 Differences from Original

Feature Original Azure DevOps MCP This PAT Version
Authentication Azure CLI / DefaultAzureCredential Personal Access Token
Dependencies Requires @azure/identity No Azure Identity SDK
Setup Requires az login Just needs PAT token
Multi-tenant Yes (via --tenant flag) No (PAT is org-specific)
Web Interface No Yes (HTTP API)
Deployment Local only Render.com ready

🛠️ Development

Build

npm run build

Development Mode

npm run dev

Testing

# Test CLI version
export AZURE_DEVOPS_PAT="your-token"
echo '{}' | node dist/index.js your-org

# Test web version
npm start
curl http://localhost:3000/health

📚 Complete Tool Reference

<details> <summary>Click to expand all 75 tools</summary>

Work Items (19 tools)

  1. wit_list_backlogs - List team backlogs
  2. wit_list_backlog_work_items - List backlog work items
  3. wit_my_work_items - Get user's work items
  4. wit_get_work_items_batch_by_ids - Batch get work items
  5. wit_get_work_item - Get single work item
  6. wit_list_work_item_comments - List work item comments
  7. wit_add_work_item_comment - Add work item comment
  8. wit_add_child_work_items - Create child work items
  9. wit_link_work_item_to_pull_request - Link to PR
  10. wit_get_work_items_for_iteration - Get iteration work items
  11. wit_update_work_item - Update work item
  12. wit_get_work_item_type - Get work item type
  13. wit_create_work_item - Create work item
  14. wit_get_query - Get query definition
  15. wit_get_query_results_by_id - Execute query
  16. wit_update_work_items_batch - Batch update
  17. wit_work_items_link - Link work items
  18. wit_work_item_unlink - Unlink work items
  19. wit_add_artifact_link - Link artifacts

Builds (9 tools)

  1. build_get_definitions - List build definitions
  2. build_get_definition_revisions - Get definition history
  3. build_get_builds - List builds
  4. build_get_log - Get build logs
  5. build_get_log_by_id - Get specific log
  6. build_get_changes - Get build changes
  7. build_run_build - Trigger build
  8. build_get_status - Get build status
  9. build_update_build_stage - Update build stage

Repositories (18 tools)

  1. repo_create_pull_request - Create PR
  2. repo_update_pull_request - Update PR
  3. repo_update_pull_request_reviewers - Manage reviewers
  4. repo_list_repos_by_project - List repositories
  5. repo_list_pull_requests_by_repo - List PRs by repo
  6. repo_list_pull_requests_by_project - List PRs by project
  7. repo_list_pull_request_threads - List PR threads
  8. repo_list_pull_request_thread_comments - List thread comments
  9. repo_list_branches_by_repo - List branches
  10. repo_list_my_branches_by_repo - List my branches
  11. repo_get_repo_by_name_or_id - Get repository
  12. repo_get_branch_by_name - Get branch
  13. repo_get_pull_request_by_id - Get PR
  14. repo_reply_to_comment - Reply to PR comment
  15. repo_create_pull_request_thread - Create PR thread
  16. repo_resolve_comment - Resolve PR comment
  17. repo_search_commits - Search commits
  18. repo_list_pull_requests_by_commits - Find PRs by commits

Search (3 tools)

  1. search_code - Search code repositories
  2. search_wiki - Search wiki pages
  3. search_workitem - Search work items

Work Management (3 tools)

  1. work_list_team_iterations - List team iterations
  2. work_create_iterations - Create iterations
  3. work_assign_iterations - Assign iterations to team

Releases (2 tools)

  1. release_get_definitions - List release definitions
  2. release_get_releases - List releases

Wiki (5 tools)

  1. wiki_list_wikis - List wikis
  2. wiki_get_wiki - Get wiki details
  3. wiki_list_pages - List wiki pages
  4. wiki_get_page_content - Get page content
  5. wiki_create_or_update_page - Create/update page

Test Plans (6 tools)

  1. testplan_list_test_plans - List test plans
  2. testplan_create_test_plan - Create test plan
  3. testplan_add_test_cases_to_suite - Add test cases
  4. testplan_create_test_case - Create test case
  5. testplan_list_test_cases - List test cases
  6. testplan_show_test_results_from_build_id - Get test results

Core (3 tools)

  1. core_list_project_teams - List project teams
  2. core_list_projects - List projects
  3. core_get_identity_ids - Get identity IDs

Advanced Security (2 tools)

  1. advsec_get_alerts - Get security alerts
  2. advsec_get_alert_details - Get alert details

</details>

🐛 Troubleshooting

Common Issues

Authentication Failed

  • Verify PAT token is valid and not expired
  • Check token has required scopes
  • Ensure organization name is correct

Service Won't Start

  • Check environment variables are set
  • Verify Node.js version >= 20.0.0
  • Check logs for specific error messages

Tool Execution Fails

  • Ensure PAT has permissions for the specific operation
  • Check project/repository names are correct
  • Verify work item IDs exist

📄 License

MIT License - see LICENSE file for details.

🤝 Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Add tests if applicable
  5. Submit a pull request

🔗 Links

⭐ Star History

If this project helped you, please consider giving it a star! ⭐

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选