Add production deployment guide and automation for MCP servers #120
+681
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds comprehensive documentation and tooling for deploying MCP servers to production environments using systemd, nginx, and Let's Encrypt SSL. ## Overview Production deployment runs MCP servers directly on VMs with systemd service management, nginx reverse proxy, and automated deployment workflows. ## Changes **Documentation:** - `docs/DEPLOYMENT.md` - Generic production deployment guide - Covers systemd setup, nginx configuration, SSL certificates - Includes concrete pizzaz example as implementation reference **Deployment Automation:** - `docs/scripts/deploy-example.sh` - Automated deployment script template - Handles building, syncing, dependency installation, service restart - Health checks and verification **Setup Files:** - `docs/setup/example-mcp.service` - Systemd service template for MCP server - `docs/setup/example-assets.service` - Systemd service for assets (optional) - `docs/setup/example-nginx-production.conf` - Production nginx with SSE ## Key Features - **Generic approach**: Works with any MCP server (Node.js, Python, etc.) - **Systemd integration**: Auto-restart on failure, logging to journalctl - **nginx optimization**: SSE-specific settings for MCP protocol - **Automated deployment**: One-command deployment with verification - **Security**: HTTPS with Let's Encrypt, firewall guidelines - **Monitoring**: Service status checks, log viewing commands - **Pizzaz example**: Concrete two-server architecture implementation ## Production Features - Service management with systemd - Automatic restarts on failure - Centralized logging with journalctl - SSL termination with nginx - Health verification after deployment - Rollback instructions - Multi-app support on single VM This enables developers to quickly deploy any MCP server from this repository to production with proper service management, monitoring, and security.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Changes
Key Features
Differences from Development Setup
Prerequisites
This PR builds upon the development setup documentation added in PR #119.
Target Audience
Developers ready to deploy their tested MCP servers to production environments.
Test Plan