Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

We would love to know:

  1. How are you using the Azure DevOps MCP Server?
  2. What scenarios are you trying to solve?
  3. How is going?
You must be logged in to vote

Replies: 2 comments · 2 replies

Comment options

  1. Our devs are using the ADO MCP heavily in the GitHub Copilot experience. We had a custom training knowledge base for our copilot agent that understands our expectations for requirements gathering, quality checks, what-if thinking, etc. By having the MCP able to crawl the work items and related items, we're able to very cleanly build implementation plans for feature/requirement work items directly from ADO, while act naturally through the MCP to post comments explaining what additional information is required. Then, we're also utilizing it extensively in: query calls to queue work, query build and logs to troubleshoot YML pipelines, and more
  2. We're trying to solve scenarios like incomplete requirements or missed best practice considerations being communicated to stakeholders, planning work items, updating work items with field settings or comments, managing pipelines and PRs
  3. Fantastic. There are still a couple of gaps here and there where we have to 'fallback' to REST or az cli like getting information at the project or process level, which can be valuable if you're using custom fields, area paths creatively, or other adjustments from 'standard'
You must be logged in to vote
2 replies
@danhellem
Comment options

danhellem Aug 15, 2025
Maintainer Author

@JeremyVyska can you send me specifics on what is missing for item 3?

@JeremyVyska
Comment options

Sure. I think the main things are what I mentioned:

  • Project configuration information. For example, getting Area Path information. We also use Area Paths Security settings, which is not available via any REST, cli, or MCP that I've found.
  • Organization settings, specifically information about Work Item configurations in the Process area. We use Custom Fields, and Rules, and States.

Would be nice to dig into those, even if just for reading. But those have been minor blips compared to the powerhouse options we already have.

Comment options

  1. I have created this prompt file (attached) to review pull requests that my team raises. I am not a prompt expert but I do get valuable insights out of it. I have managed to catch some bugs due to this. There is PRAssistant for the same purposes and we have recently onboarded to it. I will compare the results of both to see if my way is more efficient.
    PullRequestReview.prompt.md
  2. Trying to solve pull request review on local with help of AI that I can chat 1:1 with about the code changes in PR.
    Additionally there is a another scenario I want to solve. I basically need ADO MCP Server support in M365 copilot agent or ADO SWE Agent so that it is able to read from code from 2 repositories and run my prompt and finally generate a pull request as a result. As of now I have to do this in vs code github copilot.
  3. Good. Sometimes unreliable output for same prompt but I hope it improves.
You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.