mcp-hub and agent
These are complements: one provides centralized management and monitoring of multiple MCP servers, while the other aggregates them into a unified interface, with the aggregator typically consuming servers managed by the hub.
About mcp-hub
ravitemer/mcp-hub
A centralized manager for Model Context Protocol (MCP) servers with dynamic server management and monitoring
Provides a unified HTTP endpoint that aggregates multiple MCP servers with automatic capability namespacing, allowing any MCP client to access all managed servers without individual configuration. Supports local STDIO servers and remote endpoints via streamable-http/SSE transports with OAuth 2.0 and automatic reconnection. Built-in REST API, real-time SSE events, and VS Code configuration compatibility enable dynamic server management, hot reload, and environment variable interpolation.
About agent
1mcp-app/agent
A unified Model Context Protocol server implementation that aggregates multiple MCP servers into one.
Implements stdio transport isolation with subprocess management for child MCP servers, featuring OAuth 2.1 authentication, hot-reload configuration, and health check monitoring. Designed as a proxy layer that aggregates tools across multiple AI assistants (Claude Desktop, Cursor, VSCode) through a single HTTP endpoint, eliminating per-client configuration overhead.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work