-
Notifications
You must be signed in to change notification settings - Fork 65.6k
Updated the MCP Registry validation steps by including name, description and version, as done in VS Code. #42331
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Updated instructions for including local MCP servers in the registry to specify correct name, description, and version. This is as per the validation done in VS Code.
Updated the limitations section to include description and version matching for MCP allowlist enforcement. This is as per the current validation in the VS Code.
Changed to server name/ID to reflect better field.
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
Why:
The MCP Registry validation steps mentioned in the documentation is not correct. I can see from the VS Code source code that they do more elaborate validation including name, description and version.
What's being changed (if available, include any code snippets, screenshots, or gifs):
This is the part of source code in VS code where the above is validated. I spend a lot of time wandering why the server is not showing up, then figured out other parameters.
imageThis PR corrects the documentation in 2 relevant pages.
Check off the following: