mcp-toolkit-hub
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
mcp-toolkit-hub
MCP hub server that aggregates tools from multiple domain packages into a single globally-available interface.
Status
Stage: POC (Proof of Concept)
Related MCP server: MCP Proxy Server
Why a Hub?
Without a hub, each MCP package needs separate configuration, and tools only work in specific project directories. The hub pattern gives you:
One config — Single
config.yamllists all your domain packagesGlobal availability — Tools work regardless of which directory Claude Code starts from
Namespace clarity — Tools prefixed by domain:
briefing_run_weekly_digest,travel_search_flights
Architecture
User Config (~/.config/mcp-toolkit-hub/config.yaml)
↓
mcp-toolkit-hub (this package)
↓
Domain Packages (mcp-content-feed, mcp-travel, etc.)Prerequisites
Node.js 18+
One or more domain MCP packages installed locally
Domain packages built (
npm run buildin each)
Quick Start
# 1. Clone and install
git clone https://github.com/lokkaflokka/mcp-toolkit-hub.git
cd mcp-toolkit-hub
npm install
# 2. Create your config
mkdir -p ~/.config/mcp-toolkit-hub
cp examples/config.example.yaml ~/.config/mcp-toolkit-hub/config.yaml
# Edit config.yaml with paths to your domain packages
# 3. Build
npm run build
# 4. Add to Claude Code (user-level for global availability)
claude mcp add -s user personal node /path/to/mcp-toolkit-hub/dist/server/index.jsConfiguration
Edit ~/.config/mcp-toolkit-hub/config.yaml:
schema_version: "1.0"
packages:
briefing:
path: ~/path/to/mcp-content-feed
enabled: true
travel:
path: ~/path/to/mcp-travel
enabled: false # Disabled packages don't expose toolsAvailable Tools
The hub exposes tools from enabled domain packages, plus:
Tool | Description |
| Shows which packages are loaded and available |
Domain package tools are namespaced:
briefing_run_weekly_digestbriefing_run_rss_digestbriefing_content_feed_statustravel_search_flights(when enabled)
Development
npm install
npm run build
npm run dev # Run with tsx for development
npm test # Run testsKey Constraints
Distributable — This package contains generic orchestration logic; personal config stays in
~/.config/Delegates, doesn't duplicate — Business logic lives in domain packages. This package only routes.
Namespaced tools — Tools prefixed with package name using underscores (MCP spec disallows colons)
Related Packages
mcp-content-feed — Content scoring and briefing (Gmail + RSS + saved URLs)
mcp-travel — Flight search and price tracking
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for progressive tool usage at any scale (see https://klavis.ai)
One MCP server exposing every tool in the Gumball portfolio.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA central hub that aggregates multiple MCP resource servers into a single unified interface, enabling users to access tools and capabilities from multiple backend servers through one connection point.120 npm202MIT
- AlicenseNot gradedqualityDmaintenanceAggregates multiple backend MCP servers into a single unified interface with optional web management UI for tool control and configuration.120 npm195MIT
- FlicenseAqualityDmaintenanceUniversal MCP proxy server that discovers, searches, and executes tools across all configured MCP servers from a single entry point.7-
- AlicenseNot gradedqualityCmaintenanceProvides a reusable MCP server foundation with explicit tool registration, operation-mode separation, scope-based permissions, structured results, and built-in health/status tools.MIT