- Notifications
You must be signed in to change notification settings - Fork3.1k
Update docs regarding MCP Server behaviour when bad toolsets are provided#1398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Pull Request Overview
This PR updates the documentation to reflect the new MCP Server behavior introduced in PR#1202, where invalid or unknown toolsets are now silently ignored instead of causing the server to fail with a 400 error.
Key Changes:
- Updated error handling behavior documentation for the
X-MCP-Toolsetsheader to indicate that invalid toolsets are now silently ignored rather than causing server startup failures
💡Add Copilot custom instructions for smarter, more guided reviews.Learn how to get started.
Uh oh!
There was an error while loading.Please reload this page.
41090e5 intomainUh oh!
There was an error while loading.Please reload this page.
Now that we ignore "bad" toolsets in the MCP Server (PR:#1202) I have updated the docs to describe this new behaviour