cameroncooke
Deployment: Dockerfile and Smithery config
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.
- Updated README to include installation command via Smithery and a popularity badge. Note that the command only works after the server is deployed on Smithery.
Server Details
- Smithery ID:
@cameroncooke/XcodeBuildMCP - Server Homepage: https://smithery.ai/server/@cameroncooke/XcodeBuildMCP
Action Items
- [X] 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.
@calclavia Thanks for this and for adding my MCP to your registry. Given the nature of my MCP server and the fact that it needs access to the user's local file system and require Xcode and its command-line tools and therefore a macOS host to run how will this work as a remote server on your platform?
@calclavia Thanks for this and for adding my MCP to your registry. Given the nature of my MCP server and the fact that it needs access to the user's local file system and require Xcode and its command-line tools and therefore a macOS host to run how will this work as a remote server on your platform?
In that case I'd recommend claiming it and marking it as local (on the settings page). If it's local we don't run it in a hosted fashion and it'll be just a listing.
@calclavia Thanks for this and for adding my MCP to your registry. Given the nature of my MCP server and the fact that it needs access to the user's local file system and require Xcode and its command-line tools and therefore a macOS host to run how will this work as a remote server on your platform?
In that case I'd recommend claiming it and marking it as local (on the settings page). If it's local we don't run it in a hosted fashion and it'll be just a listing.
@calclavia I'm not seeing an option to claim?
@calclavia Thanks for this and for adding my MCP to your registry. Given the nature of my MCP server and the fact that it needs access to the user's local file system and require Xcode and its command-line tools and therefore a macOS host to run how will this work as a remote server on your platform?
In that case I'd recommend claiming it and marking it as local (on the settings page). If it's local we don't run it in a hosted fashion and it'll be just a listing.
@calclavia I'm not seeing an option to claim?
Ah, there was a bug on our end. Just fixed it.
Can you try: https://smithery.ai/server/@cameroncooke/XcodeBuildMCP again?
@calclavia I've claimed and marked the server as local only, do you want to revise this PR, assuming we don't need a docker file now?
@calclavia I've claimed and marked the server as local only, do you want to revise this PR, assuming we don't need a docker file now?
It's fine to keep a Dockerfile! In the future, when we support local, we'll likely be using the Dockerfile