mcp-ado-browser
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADO_ORG | Yes | Azure DevOps organization name (required). | |
| ADO_PROJECT | No | Default project scope (optional; org-wide otherwise). | |
| ADO_HEADLESS | No | Set to '0' to run work with a visible window. | |
| ADO_APP_WINDOW | No | Set to '0' to use a normal browser window for sign-in (instead of app mode). | |
| ADO_API_VERSION | No | Force an api-version for all areas. | |
| ADO_USER_DATA_DIR | No | Isolated persistent browser profile directory. | ~/.mcp-ado-browser/profile |
| ADO_BROWSER_CHANNEL | No | Browser channel: 'chrome' or 'msedge'. | chrome |
| ADO_CACHE_TTL_SECONDS | No | Global cache TTL in seconds. | 900 |
| ADO_CACHE_TTL_WORKITEM | No | Per-resource cache TTL in seconds for work items. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List ALL Azure DevOps projects the user can access in the organization (GET _apis/projects). Use this to discover projects to browse. |
| list_repositoriesA | List ALL Git repositories the user can access across the organization (GET _apis/git/repositories), or within one project. Returns id, name and owning project for each repo. |
| search_work_itemsA | Search/browse work items ORG-WIDE (cross-project) by default. Backend is WIQL (POST _apis/wit/wiql); pass |
| get_work_itemA | Get a single work item with $expand=all, including |
| get_work_item_commentsA | Get the full discussion for a work item (GET _apis/wit/workItems/{id}/comments — a SEPARATE endpoint, not part of $expand). |
| get_comment_detailsA | Resolve a work item (and optionally a specific comment) AND download all related attachments (work-item AttachedFile relations + attachments referenced in the comment body). Returns metadata + downloaded content stats (size, sha256). |
| search_pull_requestsA | Search pull requests ORG-WIDE by default, or within a repo (repoId) or a project. Filters: status, creatorId, targetRef. (GET _apis/git/pullrequests) |
| get_pull_requestA | Get a pull request with metadata, branches, reviewers and linked work items. Resolved org-wide — repoId may be a GUID or a repository name. |
| get_pull_request_commentsA | Get PR threads (system vs human). Resolved org-wide — repoId may be a GUID or a repository name. |
| search_feedsA | Browse Azure Artifacts feeds (GET feeds.dev.azure.com/_apis/packaging/feeds). Pass feedId to also list packages + versions. Each feed reports its |
| download_artifactA | Download a package artifact (.nupkg / .tgz) from a feed via the browser session (pkgs.dev.azure.com). Validates archive integrity (size, sha256, valid zip/tgz) for re-hosting. |
| authenticateA | Sign in to Azure DevOps by opening a VISIBLE browser window for interactive login (MFA included). Run this once (or whenever a tool returns AUTH_REQUIRED). The session is persisted on an isolated profile and reused headless afterward — no PAT or token is ever stored. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct resource/action: projects, repositories, work items, PRs, feeds, artifacts, and authentication. The only possible overlap is between get_work_item_comments and get_comment_details, but their descriptions clearly separate discussion retrieval from comment resolution plus attachment download.
Most tools follow a consistent verb_noun pattern (list_projects, search_work_items, get_pull_request). Minor deviations include get_comment_details (which omits 'work_item') and authenticate (verb-only), but these do not significantly hinder readability.
With 12 tools, the set is well-scoped for a browser-oriented Azure DevOps server. Each tool covers a meaningful browsing operation, and there is no redundancy or bloat.
The toolset provides good read-only coverage: listing and searching projects, repos, work items, PRs, and feeds, plus getting details and comments. Minor gaps include no explicit get_project or get_repository (though list tools return sufficient info) and no code search, but core browsing needs are met.