@om-surushe/efficient-ado
Enables AI assistants to interact with Azure DevOps through an MCP server with 34 tools for PRs, work items, repos, and branches, optimized for token efficiency and agent-first workflows.
README
@om-surushe/efficient-ado
LLM-optimized Azure DevOps workflows for AI assistants
Efficient ADO is a Model Context Protocol (MCP) server that provides AI assistants with streamlined access to Azure DevOps. Built with agent-first design principles, it minimizes round trips, reduces token usage, and provides rich contextual responses.
Features
- 🎯 Agent-First Design - Composite tools reduce round trips
- ⚡ Token Efficient - Tiered responses (summary/standard/detailed)
- 🤖 LLM-Optimized - Rich context + suggested actions in every response
- 🚀 Fast - Built with TypeScript, optimized for performance
- 📦 Complete - 34 tools covering PRs, work items, repos, branches
- 🔄 Composite Workflows - Multi-step operations in single calls
- 🧠 Error Guidance - Errors tell agents HOW to fix issues
Installation
npm install @om-surushe/efficient-ado
Quick Start
Configuration
Create a .env file:
AZDO_ORG_URL=https://dev.azure.com/your-org
AZDO_PAT=your-personal-access-token
AZDO_PROJECT=your-project # optional
AZDO_REPO=your-repo # optional
PAT Requirements:
- Code (Read & Write)
- Pull Request Threads (Read & Write)
- Work Items (Read & Write)
Usage with Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"efficient-ado": {
"command": "npx",
"args": ["@om-surushe/efficient-ado"],
"env": {
"AZDO_ORG_URL": "https://dev.azure.com/your-org",
"AZDO_PAT": "your-pat-here",
"AZDO_PROJECT": "your-project",
"AZDO_REPO": "your-repo"
}
}
}
}
Usage with OpenClaw / Cline / Other MCP Clients
Similar configuration - use stdio transport with environment variables.
Available Tools (34 Total)
Foundation
setup_workspace- Configure credentials and verify connection
Pull Request Workflows
Discovery:
list_prs- List PRs with filters (creator, reviewer, status)get_pr- Get PR details with reviewers and statusstart_review- COMPOSITE - Get PR + comments + reviewers in one call
Review & Approval:
vote_on_pr- Approve (10), approve with suggestions (5), wait (-5), reject (-10)manage_reviewers- Add/remove reviewersquick_approve- COMPOSITE - Approve + merge if ready
Merge:
check_merge_readiness- Verify all merge requirementscomplete_pr- Merge PR with completion options
Comments & Threads:
list_comments- List all threads (general + inline)add_comment- Add general or inline commentreply_to_thread- Reply to existing threadupdate_thread_status- Mark thread as fixed/active/wontFix/closedaddress_comment- COMPOSITE - Reply + resolve in one call
Files & Diffs:
get_pr_changes- List changed files with statsget_file_diff- Get file diff (side-by-side comparison)get_file_content- Get file content at PR commit
PR Lifecycle:
create_pr- Create PR with work items, reviewers, auto-completeupdate_pr- Update title, description, draft statusabandon_pr- Close PR without mergingreactivate_pr- Reopen abandoned PR
Work Items
get_work_item- Get work item by ID with relationslist_my_work_items- List work items assigned to youcreate_work_item- Create new task/bug/storyupdate_work_item- Update work item fieldsadd_work_item_comment- Add discussion commentlink_work_item- Link work items (parent/child/related)
Repos & Branches
list_repositories- List repos in projectlist_branches- List branches in repocreate_branch- Create new branch from sourcelist_commits- List commits with filtersget_commit- Get commit detailscompare_branches- Compare two branches
Daily Workflow
get_my_work- COMPOSITE - Dashboard: my PRs + reviews + work items
Usage Examples
Daily Standup
> "What do I need to work on today?"
Agent uses: get_my_work()
Response includes:
- PRs you created (3 active, 1 draft)
- PRs needing your review (2 pending vote)
- Work items assigned to you (5 tasks, 2 bugs)
Code Review
> "Review PR #1805"
Agent uses: start_review(prId=1805)
Gets in one call:
- PR details (title, description, status, branches)
- All comment threads (23 general + 5 inline)
- Reviewers and their votes
- Changed files overview
Then:
> "Show me the changes to config.ts"
Agent uses: get_file_diff(prId=1805, path="config.ts")
Returns side-by-side diff with line numbers
Addressing Feedback
> "Reply 'Fixed indentation' and mark thread 12345 as resolved"
Agent uses: address_comment(
prId=1805,
threadId=12345,
reply="Fixed indentation",
status="fixed"
)
One call handles both reply and status update
Approving & Merging
> "Approve PR #1805 and merge if ready"
Agent uses: quick_approve(prId=1805)
One call:
1. Approves PR (vote=10)
2. Checks merge requirements
3. Merges if all policies pass
4. Or tells you what's blocking
Creating Work from Feedback
> "Create a bug for the memory leak in thread 12345"
Agent uses:
1. list_comments(prId=1805) to get thread details
2. create_work_item(
type="Bug",
title="Memory leak in cache handler",
description="Details from PR review..."
)
3. link_work_item(workItemId=123, prId=1805)
Three calls link bug to the PR discussion
Design Philosophy
Agent-First
Every tool response includes:
- Current state - What's happening now
- Statistics - Quick metrics
- Blockers - What's preventing progress (if any)
- Suggested actions - What to do next with exact tool names
Token Efficient
Responses have levels:
- Summary (~200 tokens) - Quick status check
- Standard (~800 tokens) - Most common use
- Detailed (~3000 tokens) - When agent needs everything
Error Messages That Help
Errors tell agents HOW to fix issues:
{
"error": {
"code": "MERGE_BLOCKED",
"blockers": [
{
"reason": "Insufficient approvals (1/2)",
"howToFix": "Call vote_on_pr(vote=10) to approve",
"relatedTools": ["vote_on_pr"]
}
]
}
}
Development
git clone https://github.com/om-surushe/efficient-ado.git
cd efficient-ado
npm install
npm run build
Status
- [x] Phase 1: Foundation + setup
- [x] Phase 2: Pull request workflows (15 tools)
- [x] Phase 3: Work items (6 tools)
- [x] Phase 4: Repos & branches (6 tools)
- [x] Phase 5: PR creation & update (4 tools)
- [x] Phase 6: Composite workflows (2 tools)
Total: 34 tools complete and ready for use! 🎉
Future Enhancements
- [ ] Pipeline/build tools
- [ ] Team/project management
- [ ] Wiki/documentation tools
- [ ] Artifact management
- [ ] Test plan integration
License
MIT License - see LICENSE for details.
Author
Om Surushe
- GitHub: @om-surushe
- npm: @om-surushe
Related Packages
- @om-surushe/efficient-ticktick - LLM-optimized TickTick task management
- @om-surushe/efficient-search - LLM-optimized web search
Part of the Efficient MCP series - LLM-optimized tools for AI assistants.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。