MCP Hub

Created By
Sobroinca year ago
MCP Hub - Central coordinator for MCP servers with REST API and real-time events
Overview

what is MCP Hub?

MCP Hub is a central coordinator for managing multiple MCP servers, providing a unified REST API and real-time event handling for seamless interaction between clients and servers.

how to use MCP Hub?

To use MCP Hub, install it via npm with npm install -g mcp-hub, then start the hub server using the command mcp-hub --port 3000 --config path/to/config.json.

key features of MCP Hub?

  • Dynamic Server Management: Start, stop, and configure servers on demand with real-time updates.
  • Unified REST API: Access tools and resources from any connected server with full CRUD operations.
  • Real-time Events: Receive live updates on server status and capabilities through Server-Sent Events (SSE).
  • Client Connection Management: Monitor and manage client connections efficiently.

use cases of MCP Hub?

  1. Coordinating multiple server instances for distributed applications.
  2. Managing real-time data processing across various services.
  3. Simplifying API interactions for developers working with multiple backend services.

FAQ from MCP Hub?

  • Can MCP Hub manage any type of server?

Yes! MCP Hub can manage both local and remote servers using various transport protocols.

  • Is MCP Hub open-source?

Yes! MCP Hub is licensed under the MIT License and is available on GitHub.

  • How can I contribute to MCP Hub?

Contributions are welcome! Please check the contributing guidelines in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Sobroinc
Star
0
Language
JavaScript
License
MIT 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