MQ: Enable Azure MCP Server to Query Recent Service Updates (e.g., Key Vault changes in last X days)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.7k
- Forks
- 624
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 220
Description
I’m a Content Developer in the Microsoft Learn organization, and we would find this feature useful for keeping documentation up-to-date.
Our team regularly needs to identify recent changes to Azure services and products so we can update Learn content accordingly. Today, this requires manual monitoring of update feeds and release notes. If Azure MCP Server could expose a tool for querying recent service updates (e.g., “What features/changes occurred for Key Vault over the last 14 days?”), it would enable two key workflows:
- Writers calling the tool directly to check for changes before updating docs.
- AI agents programmatically invoking the tool to detect changes and automatically create pull requests for documentation updates.
I propose an MCP tool (or an extension to an existing one) that can:
- Query official Azure Updates feeds and/or service release notes
- Filter by service name and time window (e.g., last 14 days)
- Return structured results (title, date, summary, link, category)
Customers would also benefit from this capability because it mirrors the value they already find in changelogs and “What’s New” articles.
Thanks for the consideration!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Azure MCP Server entry point and any existing tools, then review the official Azure Updates feeds and service release notes named in the issue. Done means a tool can filter updates by service and time window and return each result’s title, date, summary, link, and category.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100