microsoft / microsoft/upgrade-agent-plugins
Enterprise "Registry only" MCP policy blocks local MCP servers in sub-agent processes
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 37
- Forks
- 8
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 6
Description
When using the Microsoft Upgrade Agent plugin with GitHub Copilot CLI, the local built-in MCP servers are accessible in the main CLI session (via manual mcp.json configuration) but are not invokable from sub-agent processes when the enterprise policy is set to "Registry only". Admin has allowed this MCP, but it still don't work via the upgrade agent.
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the issue with the Microsoft Upgrade Agent plugin and GitHub Copilot CLI using a manual mcp.json configuration and the enterprise "Registry only" policy. Compare local built-in MCP invocation in the main CLI session with invocation from a sub-agent; the work is done when an admin-allowed MCP works in both contexts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, powershell
- Domain
- authorization, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100