MCP Host Server
@motionmavericks
Multi-tenant remote MCP server hosting platform for DigitalOcean
Overview
What is MCP Host Server?
A multi-tenant remote MCP (Model Context Protocol) server hosting platform built for DigitalOcean deployment. It allows multiple applications to connect to and use various MCP servers remotely over WebSocket connections, with JWT‑based authentication and role‑based access.
How to use MCP Host Server?
Clone the repository, copy .env.example to .env, configure JWT_SECRET, ALLOWED_ORIGINS, and ADMIN_PASSWORD, run npm install, then start with npm run dev (development) or npm start (production). Use the REST API to authenticate and create MCP servers, then connect via the provided WebSocket connection URL.
Key features of MCP Host Server
- Multi-tenant architecture with isolated MCP servers per tenant
- JWT‑based authentication with role‑based access control
- Remote WebSocket connections for MCP client usage
- RESTful management API for server lifecycle
- Rate limiting, input validation, CORS, and Helmet security headers
- Designed for scalable cloud deployment on DigitalOcean App Platform
Use cases of MCP Host Server
- Hosting remote file‑manager, database, and API MCP servers for Claude Desktop
- Providing isolated MCP environments for multiple tenants (e.g., separate teams or projects)
- Enabling custom MCP clients to connect to tools via a secure WebSocket gateway
- Managing and monitoring MCP server instances through a unified management API
FAQ from MCP Host Server
What is MCP Host Server?
It is a multi‑tenant platform that hosts MCP servers remotely, allowing multiple applications (like Claude Desktop) to connect to them via WebSocket.
How do I connect an MCP client to a server?
After authenticating and creating a server via the REST API, use the returned WebSocket URL (with tenant, server ID, and connection token) in your client configuration.
What MCP server types are available?
The platform supports file manager (read/write/list files), database (SQL queries), API client (HTTP requests), and custom tool definitions.
How is security handled?
Security features include JWT authentication, rate limiting, input validation, CORS protection, Helmet.js headers, and request logging.
What are the deployment requirements?
The server is designed for DigitalOcean App Platform; it runs on Node.js, requires environment variables (JWT_SECRET, ALLOWED_ORIGINS, etc.), and supports instance scaling via an App Spec.