azure-devops-local-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP mode only: listen port (default: 3100) | 3100 |
| ADO_PAT | Yes | Personal Access Token | |
| ADO_ORG_URL | Yes | Organisation URL, e.g. https://dev.azure.com/myorg | |
| ADO_HTTP_HOST | No | HTTP mode only: bind address (default: 127.0.0.1; non-loopback requires ADO_HTTP_TOKEN) | 127.0.0.1 |
| ADO_LOG_LEVEL | No | debug, info, warn, error (default: info) | info |
| ADO_READ_ONLY | No | true registers only read tools — no writes possible | |
| ADO_HTTP_TOKEN | No | HTTP mode only: require Authorization: Bearer <token> on /mcp | |
| ADO_RATE_LIMIT | No | Max API requests per minute (default: 60) | 60 |
| ADO_API_VERSION | No | Azure DevOps REST API version, e.g. 7.2-preview (default) or 7.1 | 7.2-preview |
| ADO_DEFAULT_PROJECT | No | Default project name |
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 |
|---|---|
| ado_projects_listA | List all projects in the Azure DevOps organization. Use this first to discover available projects before using other tools. Returns project name, ID, description, state, url, and lastUpdateTime. |
| ado_workitems_queryA | Run a WIQL (Work Item Query Language) query against Azure DevOps and return matching work items. Example: SELECT [System.Id], [System.Title], [System.State] FROM WorkItems WHERE [System.WorkItemType] = 'Bug' AND [System.State] <> 'Closed'. Returns ID, title, state, type, and assignee for each match. Use ado_workitems_get for full details on a specific item. |
| ado_workitems_getA | Get full details of a single work item by its ID, including all fields, description, tags, and relations. Use ado_workitems_query or ado_workitems_list_recent to find work item IDs first. If project is supplied and the item belongs to a different project, the call will error with the actual project name. |
| ado_workitems_createA | Create a new work item in Azure DevOps. Specify the project, type (Bug, Task, User Story, Epic, Feature, etc.), and fields. Returns the created work item with its ID. Requires vso.work_write PAT scope. |
| ado_workitems_updateA | Update fields on an existing work item. Pass the work item ID and a map of field names to new values. Common fields: System.State, System.AssignedTo, System.Title, System.Tags, Microsoft.VSTS.Common.Priority. Requires vso.work_write PAT scope. |
| ado_workitems_linkA | Link two work items. Typical use: set a Feature as the parent of a Task so it shows nested on the board (linkType='parent', fromId=Task, toId=Feature). Can also create child, related, predecessor, successor, duplicate, and duplicate-of links. Requires vso.work_write PAT scope. |
| ado_workitems_unlinkA | Remove an existing link between two work items. Pass the same fromId/toId/linkType used when the link was created. Errors if the link is not present. Requires vso.work_write PAT scope. |
| ado_workitems_list_recentA | List recently updated work items in a project, with optional filters for type, state, and assignee. Results are ordered by last changed date (newest first). Use this for quick overviews; use ado_workitems_query for complex filtering. |
| ado_git_list_reposA | List Git repositories in an Azure DevOps project. Returns repository ID, name, default branch, and size. Use the repository ID in other git tools (PRs, search). |
| ado_git_list_prsA | List pull requests in a project or specific repository. Filter by status (active, completed, abandoned) and creator. Returns PR ID, title, status, branches, creator, and reviewers. Use ado_git_get_pr for full details on a specific PR. |
| ado_git_get_prA | Get full details of a specific pull request, including title, description, reviewers, source/target branches, and status. Use ado_git_get_pr_threads for comments/discussions. |
| ado_git_get_pr_threadsA | Get all comment threads on a pull request, including inline code comments with file paths and line numbers. Use ado_git_create_pr_comment to reply to a thread or add a new comment. |
| ado_git_create_pr_commentA | Add a comment to a pull request. To reply to an existing thread, provide threadId (do not provide filePath). To create a new general thread, provide only content. To create an inline code comment, provide filePath; optionally add lineNumber (start) and endLineNumber (end) for a multi-line range, and side ('right' for new file, 'left' for old). Requires vso.code_write PAT scope. |
| ado_git_search_codeA | Search for code across Azure DevOps repositories. Returns matching files with paths, repository names, and character-offset positions of each match within the file. To read the matched text, fetch the file via the repository API. Optionally scope to a project or specific repository. Does NOT search work items or wiki — use ado_workitems_query for work item search. |
| ado_wiki_listA | List wikis in an Azure DevOps project, or all wikis across the organisation when project is omitted. Returns id, name, type (projectWiki or codeWiki), projectId, remoteUrl, and versions for each wiki. Call this first to discover wikiId values before using ado_wiki_get_page or ado_wiki_list_pages. An empty result means the project exists but has no wiki provisioned. Requires vso.wiki PAT scope. |
| ado_wiki_get_pageA | Fetch the content and metadata of a single Azure DevOps wiki page by its path. Returns the page content (Markdown), URL, last updated date, and version. Requires vso.wiki PAT scope. |
| ado_wiki_list_pagesA | List pages in an Azure DevOps wiki with optional pagination. Returns a list of pages with their paths, URLs, and metadata. When wikiId is omitted the project's default projectWiki is resolved automatically — use ado_wiki_list to discover available wikis if auto-resolve fails. Use top to limit results; pass the returned continuationToken for subsequent pages. Requires vso.wiki PAT scope. |
| ado_wiki_update_pageA | Create or update an Azure DevOps wiki page at the specified path. If the page does not exist it will be created; if it exists it will be updated. To prevent overwriting concurrent edits, pass the |
| ado_pipelines_listA | List pipeline definitions for an Azure DevOps project. Returns id, name, folder, revision, and URLs for each pipeline. Requires vso.build PAT scope. |
| ado_pipelines_get_runA | Get details of a single Azure DevOps pipeline run by pipeline ID and run ID. Returns state, result, timestamps, and URL. Requires vso.build PAT scope. |
| ado_pipelines_list_runsA | List recent pipeline runs for an Azure DevOps project with optional filtering. Filter by pipeline definition, status, or paginate with top and continuationToken. Requires vso.build PAT scope. |
| ado_pipelines_triggerA | Queue a new pipeline run in Azure DevOps. This is a WRITE operation — it will immediately queue a run and consume build minutes. Optionally override the branch, set pipeline variables, or skip stages. Requires vso.build_execute PAT scope. |
| ado_pipelines_get_logsA | Get build log references for an Azure DevOps pipeline run. Returns a list of log entries (id, type, url, lineCount) truncated to 10 KB to prevent context overflow. Follow the url of each log entry to fetch full log content. Requires vso.build PAT scope. |
| ado_testplans_listA | List test plans in an Azure DevOps project. Returns each plan's ID, name, area path, iteration, state, and the root suite ID. The root suite ID is needed when creating child suites with ado_testsuites_create. |
| ado_testplans_getA | Get details of a single test plan by ID. Returns name, area path, iteration, state, start/end dates, and the root suite ID. Use ado_testplans_list to discover plan IDs. |
| ado_testplans_createA | Create a new test plan in Azure DevOps. ADO automatically creates a root suite alongside the plan — the response includes rootSuiteId. Pass rootSuiteId as parentSuiteId when calling ado_testsuites_create to add child suites. Requires vso.test_write PAT scope. |
| ado_testsuites_listA | List all suites in a test plan. Returns each suite's ID, name, type, state, test case count, and parent suite ID. Use ado_testplans_list to find plan IDs. |
| ado_testsuites_createA | Create a new suite inside a test plan. suiteType must be staticTestSuite (test cases added manually), requirementTestSuite (linked to one backlog item — requirementId required), or dynamicTestSuite (auto-populated from WIQL — queryString required, membership is read-only). Set parentSuiteId to the plan's rootSuiteId (from ado_testplans_create/get) to attach directly under root. Requires vso.test_write PAT scope. |
| ado_testcases_add_to_suiteA | Add existing Test Case work items to a suite. Pass an array of work item IDs that have type 'Test Case'. Use ado_workitems_create with type='Test Case' to create new test cases first. Only works for staticTestSuite — dynamicTestSuite membership is query-driven. Requires vso.test_write PAT scope. |
| ado_testcases_listA | List test cases assigned to a suite. Returns each test case's work item ID and title. Use ado_workitems_get for full test case details including steps. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Laonnda/azure-devops-local-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server