-
Notifications
You must be signed in to change notification settings - Fork 65
Deployment: Smithery config #31
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
💚 CLA has been signed |
Hey @calclavia, thanks for your contribution! In order for us to be able to merge your changes, please sign the contributor agreement. |
buildkite test this |
Just signed |
Thank you, one more thing (as mentioned in #37 (comment)). We prefer to build the image on top of Chainguard’s hardened Wolfi base image. Switching to the publicly available Once we have the repos |
Yep! Dockerfile is required. Since I'm not familiar with the specific image needs, you can feel free to make this change to the Dockerfile: You should have permission on the branch to make PR. Thanks! |
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! I've not used Smithery before, but I'll set up an official page for it on their registry after merging.
It looks like that build failed. Dockerfile seems to have failed their tests. Docs say:
I may need to add |
This PR adds files for deploying your MCP server on Smithery. After deployment, users can use your server over WebSockets (hosted on Smithery) without needing to install any dependencies.
Changes
Server Details
@elastic/mcp-server-elasticsearch
Action Items