The intention is to investigate whether including the TypeSpec authoring chatbot MCP in the Azure/azure-rest-api-specs repository can help GitHub Copilot better handle user issues and PR reviews.
One champion scenario I'd imagine would be:
Issue by user with description like below:
1. Add preview api-version 2025-09-01 to RP <resource-provider>
2. Add resource <resource> with path <route>, including standard CRUD operations on this resource
Assign to Copilot.
Copilot should successfully resolve the issue and create a PR to add that preview API version, along with the resources and routes. It should also follow best practice (e.g. remove the previous preview and only keep the latest; use standard Resource and Resource operation templates).
There are 2 major things to check:
- Copilot cannot do this well without our MCP
- Copilot can do this well if we add the MCP
and 1 minor thing
- There is no easier way to make Copilot work well, without providing the MCP (i.e. whether a bunch of markdown can already help Copilot do this?)