NeuralTrust has been recognized by Gartner → Read more

Connect Azure DevOps MCP to your AI agents, securely.

One secured endpoint for every Azure DevOps call your AI agents make, scoped per user, inspected, and logged.

Select the tools your AI agents can call

44 tools from the Azure DevOps MCP schema.

Showing 44 tools

  • core_list_projectsreadLists all projects in the organization.
  • core_list_project_teamsreadLists the teams within a project.
  • core_get_identity_idsreadRetrieves identity IDs by search filter.
  • wit_work_itemreadReads work items: get a single item, get a batch by IDs, list comments, or list items relevant to the authenticated user.
  • wit_work_item_writewriteCreates or updates work items, individually or in batch.
  • wit_work_item_comment_writewriteAdds a comment to a work item.
  • wit_work_item_link_writewriteLinks work items to each other, to pull requests or to other artifacts.
  • wit_backlogreadLists backlog levels and the work items in a specific backlog level.
  • workreadLists iterations in a project and the iterations assigned to a team.
  • wit_work_item_attachmentwriteUploads an attachment to a work item or downloads an existing one.
  • work_iteration_writewriteCreates iterations and assigns them to a team.
  • work_capacity_writewriteUpdates the capacity of a team member for an iteration.
  • wit_queryreadGets a work item query by ID or path, runs saved queries and executes ad-hoc WIQL queries.
  • wit_work_item_attachment_uploadwriteUploads a file as a new work item attachment without linking it.
  • wit_work_item_attachment_linkwriteLinks an uploaded attachment to a work item.
  • repo_repositoryreadLists repositories in a project and gets the details of one.
  • repo_branchreadLists branches in a repository, or the branches the current user has pushed to.
  • repo_filereadLists the files and folders in a repository directory.
  • repo_pull_requestreadLists pull requests in a repository or project, and finds those containing specific commits.
  • repo_pull_request_orgreadLists the authenticated user's active pull requests across the organization.
  • repo_pull_request_threadreadLists comment threads on a pull request and the comments in a thread.
  • repo_pull_request_writewriteCreates or updates a pull request.
  • repo_pull_request_thread_writewriteAdds or replies to a comment thread on a pull request.
  • repo_file_writewriteCreates or edits a text file on an existing branch and commits the change.
  • repo_search_commitsreadSearches commits, with filters for text, author and date range.
  • repo_create_branchwriteCreates a new branch in a repository.
  • pipelines_buildreadLists builds with optional filters and gets the commits and work items associated with a build.
  • pipelines_build_logreadLists the available logs for a build and retrieves their content.
  • pipelines_definitionreadLists pipeline definitions with optional filters and their revision history.
  • pipelines_runreadLists the runs for a pipeline.
  • pipelines_artifactreadLists the artifacts produced by a build.
  • pipelines_writewriteQueues pipeline runs, creates and renames YAML pipeline definitions, and cancels, retries or runs stages on in-flight builds.
  • wikireadLists wikis in an organization or project, gets wiki details, lists pages, and gets page metadata and content.
  • wiki_upsert_pagewriteCreates or updates a wiki page.
  • search_codereadSearches for code across repositories.
  • search_wikireadSearches wiki pages by keywords.
  • search_workitemreadSearches work items by text and filters.
  • advsec_get_alertsreadRetrieves Advanced Security alerts for a repository.
  • advsec_get_alert_detailsreadGets detailed information about a specific security alert.
  • testplanreadLists test plans, test suites and test cases in a project.
  • testplan_show_test_results_from_build_idreadGets the test results for a specific build.
  • testplan_test_plan_writewriteCreates a new test plan.
  • testplan_test_suite_writewriteCreates a test suite within a test plan and adds test cases to it.
  • testplan_test_case_writewriteCreates test case work items and updates the steps of existing test cases.

What Azure DevOps MCP exposes

Azure DevOps MCP groups its 44 tools into 8 categories, each with a suggested starting policy.

All 44 tools as JSON, ready to paste.

CategoryCoversAccessSuggested policy
Work ItemsWork item reads, batch reads, comments, backlogs, iterations and updatesRead / WriteAudit updates; keep batch writes disabled unless needed
ReposRepositories, branches, files, pull requests and comment threadsRead / WriteRequire approval for pull request actions
PipelinesBuilds, definitions, runs, logs and artifactsRead / WriteRestrict pipeline execution
WikiWiki listing, pages, page content and upsertsRead / WriteReview content before publishing
SearchCode, wiki and work item search across the organizationReadLimit to intended projects
CoreOrganizations, projects, teams, identities and group membersReadLimit organization access
Advanced SecuritySecurity alerts and alert details for a repositoryReadLimit access to security findings
Test PlansTest plans, test suites, test cases and build test resultsRead / WriteAllow reading; review creation of plans, suites and cases

Connect Azure DevOps MCP to your AI agent

Four steps, under ten minutes.

  1. 01

    Sign in to NeuralTrust

    Open the NeuralTrust platform, sign in and go to Getting started, then Connect your tools.

    Sign in to NeuralTrust
  2. 02

    Choose your agent

    When asked which agent you use, pick Claude Code, Codex, Cursor, Windsurf, Copilot or your own code.

    Choose your agent
  3. 03

    Connect Azure DevOps

    Find Azure DevOps in the tool list and connect it.

    Connect Azure DevOps
  4. 04

    Connect your agent

    Follow the steps on screen to add the config to your agent, then send the test prompt.

    Connect your agent

Permissions down to the single tool

You do not allow Azure DevOps MCP or block it. You allow the exact tools each agent can call, one by one.

Azure DevOps MCP44 TOOLS AVAILABLE
Code review agent4 tools, read only
Issue triage bot9 tools
Platform team assistantall 44 tools
  • Tool by toolConnecting the server is not the unit of access. Each tool is granted on its own.
  • Default denyA tool you have not enabled is never exposed to the agent.
  • Approval on writesTools that change or delete things can require a human to confirm.

Is Azure DevOps MCP secure?

One endpoint instead of raw credentials. Every call is checked against policy and logged.

AI agentsConnect through your MCP client configuration.NeuralTrustApply controls based on your configuration.Azure DevOps MCP44 documented tools.
Coding assistantsConnection & credentialsper userWork Items12 tools
Internal copilotsTool access policiesdeny by defaultRepos11 tools
Workflow automationsRequest & response inspectioninlinePipelines6 tools
Compatible MCP clientsActivity monitoringalerts and logsAll other tools15 tools
FAQ

Common questions about running Azure DevOps MCP through TrustGate.

Connect Azure DevOps MCP instantly

Pick the tools, point your agent at TrustGate, and Azure DevOps MCP is live: scoped, inspected, logged.