Skip to content

Deployment: Dockerfile and Smithery config #1

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

calclavia
Copy link

This pull request introduces the following updates:

  • Dockerfile: Introduces a Dockerfile to package the MCP for deployment across various environments.
  • Smithery Configuration: Adds a Smithery YAML file, which specifies how to start the MCP and the configuration options it supports. It allows you to deploy your MCP to Smithery, serving it over WebSockets so end-users do not need to install additional dependencies. To deploy, merge this PR, then visit your server page and click "Deploy" under the deployments page.
  • README: Updates the README to include installation instructions via Smithery and a popularity badge. Note that the installation only works after the server is deployed on Smithery.

Please review these updates to verify their accuracy for your server and feel free to customize it to your needs. Let me know if you have any questions. 🙂

Copy link
Owner

@lamemind lamemind left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello, thanks for your PR
there's an issue in the dockerfile

RUN npm ci --only=production

# Run the application
ENTRYPOINT ["node", "dist/index.js"]
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming I'm getting this right, the server doesn't start without a config file.
a valid json config file is required to let the server start.
e.g. ENTRYPOINT ["node", "dist/index.js", "my-multiverse.json"]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants