Skip to content

Deployment: Dockerfile and Smithery config#45

Merged
cameroncooke merged 4 commits intogetsentry:mainfrom
smithery-ai:smithery/config-ma3b
Jun 7, 2025
Merged

Deployment: Dockerfile and Smithery config#45
cameroncooke merged 4 commits intogetsentry:mainfrom
smithery-ai:smithery/config-ma3b

Conversation

@calclavia
Copy link
Contributor

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

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.

@cameroncooke cameroncooke requested a review from Copilot May 15, 2025 19:08

This comment was marked as outdated.

@cameroncooke
Copy link
Collaborator

cameroncooke commented May 16, 2025

@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
Copy link
Contributor Author

@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.

@cameroncooke
Copy link
Collaborator

@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
Copy link
Contributor Author

@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?

@cameroncooke
Copy link
Collaborator

cameroncooke commented May 17, 2025

@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
Copy link
Contributor Author

@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

@cameroncooke cameroncooke requested a review from Copilot June 7, 2025 20:18
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This pull request adds deployment support for the MCP server on Smithery by introducing a new Dockerfile for packaging and a Smithery configuration file. Additionally, the README has been updated with installation instructions and a badge.

  • Added a Dockerfile to configure a multi-stage build for runtime.
  • Created a Smithery configuration file with a commandFunction for server startup.
  • Updated README with installation instructions for Smithery.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
smithery.yaml New configuration file for defining the server startup command
README.md Added instructions for installing the server via Smithery
Dockerfile Introduces a multi-stage Docker build for packaging the server
Comments suppressed due to low confidence (1)

smithery.yaml:12

  • [nitpick] Consider adding inline documentation or a comment explaining the commandFunction to help maintainability in case additional configuration options are later introduced.
(config) => ({ command: 'xcodebuildmcp', args: [], env: {} })

@@ -0,0 +1,38 @@
# Generated by https://smithery.ai. See: https://smithery.ai/docs/build/project-config
# Use a small base image with Node.js LTS
FROM node:lts-alpine AS build
Copy link

Copilot AI Jun 7, 2025

Choose a reason for hiding this comment

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

Consider pinning the Node.js LTS image version (e.g., node:18.17.0-alpine) to improve build reproducibility.

Suggested change
FROM node:lts-alpine AS build
FROM node:18.17.0-alpine AS build

Copilot uses AI. Check for mistakes.
@cameroncooke cameroncooke merged commit 52e43a2 into getsentry:main Jun 7, 2025
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.

3 participants