Granular MCP server auto-approval settings #182284
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Copilot Feature Area
Copilot Agent Mode
Body
Description:
As a user working with multiple MCP servers (e.g., GitLab, filesystem, etc.),
I would like to configure auto-approval settings per MCP server rather than globally.
We could even think about having a more precise settings, with auto-approval for "read" actions only or auto-approval for all actions.
Use case:
Proposed solution:
Add per-server configuration in mcp.json or VS Code settings:
{
"servers": {
"GitLab": {
"autoApprove": false,
"autoApproveReadOnly": true,
...
}
}
Beta Was this translation helpful? Give feedback.
All reactions