Skip to content

Deployment: Dockerfile and Smithery config #112

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: main
Choose a base branch
from

Conversation

calclavia
Copy link

@calclavia calclavia commented Apr 25, 2025

This PR adds files for deploying your MCP server on Smithery. After deployment, users can use your server over streamable HTTP (hosted on Smithery) without needing to install any dependencies.

Changes

  • Added Dockerfile to package your server for deployment.
  • Added Smithery Configuration file to specify how to start your server. See documentation.

Server Details

Action Items

  • Build Passing: We verified that the Docker builds and your server starts up using an automated test.
  • Code Review: Please review the changes to ensure the configuration is accurate for your server.
  • Claim Server: Head to your server page to claim your server. This will let you edit your server listing on Smithery and deploy new versions of your server.

@damms005
Copy link
Owner

@calclavia Thanks for adding this, really appreciate it.

However, I noticed Smithery mostly leverages docker, even as reflected in this PR. However, I foresee a future where I add a setting in my code that allows users to specify their own custom port rather than the currently hardcoded 50001. How do you suggest such dynamic port settings be made to work with your platform with respect to when a user sets it in DevDb settings in their IDE?

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