-
Notifications
You must be signed in to change notification settings - Fork 29
support for MCP registry #42
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
752f6c7 to
e33fd2a
Compare
4faf7c7 to
afb8d23
Compare
1f9e913 to
3097e1d
Compare
zmofei
left a comment
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.
Looks good to me, do not forget to updat the version in package-lock.json
package-lock.json
Outdated
| { | ||
| "name": "@mapbox/mcp-server", | ||
| "version": "0.5.4", | ||
| "version": "0.5.5-dev", |
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.
Please remove-dev before merge. .e.g run npm install and push the package-lock.json changes
though not documented as such until version 9/29?
61d9fa0 to
c7125c8
Compare
Description
Add support for the MCP registry (and eventually the Github MCP registry) as described here
Note that the spec for adding remotes is in flux / broken as documented / sounds like it may change, so I did not add the remote server for now. Adding it per current spec does not work when using the name: io.github... See issue
Testing
Checklist
[ ] Documentation has been updated if neededAdditional Notes