MCP Host Server

Created By
motionmavericksa year ago
Multi-tenant remote MCP server hosting platform for DigitalOcean
Overview

what is MCP Host Server?

MCP Host Server is a multi-tenant remote hosting platform designed for deploying Model Context Protocol (MCP) servers on DigitalOcean, allowing multiple applications to connect and utilize various MCP servers remotely via WebSocket connections.

how to use MCP Host Server?

To use MCP Host Server, clone the repository from GitHub, install the dependencies, configure the environment settings, and start the server in development or production mode. You can then interact with the server using the provided RESTful API for management and WebSocket connections for client applications.

key features of MCP Host Server?

  • Multi-tenant architecture for isolated server instances
  • Secure JWT-based authentication with role-based access
  • Remote access via WebSocket connections
  • RESTful API for server management
  • Security features including rate limiting and input validation
  • Scalable deployment on DigitalOcean

use cases of MCP Host Server?

  1. Hosting multiple isolated MCP servers for different applications.
  2. Enabling secure remote access for various client applications.
  3. Managing server instances through a RESTful API.

FAQ from MCP Host Server?

  • Can I host multiple applications on MCP Host Server?

Yes! MCP Host Server supports multi-tenancy, allowing multiple applications to run on isolated servers.

  • How do I secure my MCP server?

MCP Host Server uses JWT authentication, rate limiting, and input validation to ensure security.

  • Is there documentation available for setup and usage?

Yes! Comprehensive documentation is available on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
motionmavericks
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago