Implement remote MCP server deployment capabilities

- Add HTTP/JSON-RPC server for remote MCP access
- Configure domain and authentication via environment variables
- Create comprehensive remote deployment documentation
- Support both local (stdio) and remote (HTTP) deployment modes
- Add PM2 and Nginx configuration examples
- Update README with remote server instructions

The server can now be deployed on a VM (e.g., Hetzner) and accessed
from Claude Desktop over HTTPS using the configured domain.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
czlonkowski
2025-06-08 07:31:12 +00:00
parent d32af279c0
commit ee8aa729c1
9 changed files with 1867 additions and 17 deletions

View File

@@ -1,22 +1,32 @@
# n8n Configuration
N8N_BASIC_AUTH_USER=admin
N8N_BASIC_AUTH_PASSWORD=your-secure-password-here
N8N_HOST=localhost
N8N_API_KEY=your-api-key-here
# n8n Documentation MCP Remote Server Configuration
# MCP Configuration
MCP_LOG_LEVEL=info
NODE_ENV=production
# Remote Server Configuration
MCP_PORT=3000
MCP_HOST=0.0.0.0
MCP_DOMAIN=n8ndocumentation.aiservices.pl
# Authentication (REQUIRED for production)
# Generate a secure token: openssl rand -hex 32
MCP_AUTH_TOKEN=your-secure-auth-token-here
# CORS - Enable for browser-based access
MCP_CORS=true
# TLS Configuration (optional but recommended for production)
# MCP_TLS_CERT=/path/to/cert.pem
# MCP_TLS_KEY=/path/to/key.pem
# Database Configuration
NODE_DB_PATH=/app/data/nodes.db
NODE_DB_PATH=/app/data/nodes-v2.db
# Optional: External n8n instance
# N8N_API_URL=http://your-n8n-instance:5678
# Node.js Environment
NODE_ENV=production
# MCP Server Configuration (if using HTTP transport)
# MCP_SERVER_PORT=3000
# MCP_SERVER_HOST=localhost
# Logging
MCP_LOG_LEVEL=info
# Authentication
# MCP_AUTH_TOKEN=your-secure-token
# Legacy n8n Configuration (not used in v2)
# N8N_BASIC_AUTH_USER=admin
# N8N_BASIC_AUTH_PASSWORD=your-secure-password-here
# N8N_HOST=localhost
# N8N_API_KEY=your-api-key-here