mcphub

Centralized hub for curated MCP (Model Context Protocol) servers. Browse, search, and install MCP servers across multiple AI clients from a single CLI.

Why mcphub?

Setting up MCP servers means finding the right packages, figuring out config formats for each AI client, and managing environment variables. mcphub solves this:

• 40+ curated servers — Verified configs ready to install in one command
• 5 bundles — Pre-built collections by use case (web-dev, data-science, devops, full-stack, productivity)
• 5 AI clients — Claude Desktop, VS Code, Cursor, Windsurf, Claude Code
• Auto-discovery — Finds 400+ servers from npm automatically
• Zero config — Works instantly with npx, no global install needed

Quick Start

# Install a single server
npx mcphub install filesystem

# Install a bundle (multiple servers at once)
npx mcphub bundle install web-developer

# Search servers
npx mcphub search database

# List all available servers
npx mcphub list

# Show server details
npx mcphub info postgres

# Show bundle contents before installing
npx mcphub bundle show devops

Available Bundles

How It Works

View interactive architecture diagram on Excalidraw

flowchart TD
    A["npx mcphub install filesystem"] --> B["Load from registry index.json"]
    B --> C["Resolve server config"]
    C --> D{"mcpman installed?"}
    D -->|YES| E["Delegate to mcpman\n(lockfile, rollback)"]
    D -->|NO| F["Detect AI clients"]
    F --> G["Write config to each\nclient's JSON file"]
    E --> H["Done! Restart AI client"]
    G --> H

mcphub reads server configs from its curated registry and writes them to the correct config file for each detected AI client:

With mcpman

mcpman is a full-featured MCP package manager. mcphub integrates with it seamlessly:

flowchart LR
    subgraph mcphub["mcphub (WHAT)"]
        R[Curated Registry]
        B[Bundles]
        D[Auto-Discovery]
        S[Quality Scoring]
    end
    subgraph mcpman["mcpman (HOW)"]
        I[Smart Installer]
        L[Lockfile]
        RB[Rollback]
        V[Vault]
    end
    DEV["Developer"] --> mcphub
    DEV --> mcpman
    mcphub -->|delegates| mcpman
    mcpman -->|resolves from| mcphub
    mcpman --> AI["AI Clients"]
    mcphub -->|fallback| AI

mcphub = what to install (curated catalog, bundles, scoring)
mcpman = how to install (lockfile, rollback, version management, 10+ clients)

Option 1: Automatic (Recommended)

If mcpman is installed globally, mcphub automatically delegates to it:

npm install -g mcpman
npx mcphub install filesystem    # → automatically uses mcpman under the hood

Option 2: mcpman Registry

Add mcphub as a registry source in mcpman:

mcpman registry add mcphub https://raw.githubusercontent.com/user/mcphub/main/registry/index.json
mcpman install mcphub:filesystem
mcpman install mcphub:postgres

Option 3: mcpman Plugin

For richer integration (search, bundles via mcpman):

# Copy plugin to ~/.mcpman/plugins/mcphub/
mcpman install mcphub:filesystem    # Resolves from mcphub registry

Standalone (No mcpman)

mcphub works perfectly without mcpman. It writes configs directly to your AI client files. mcpman just adds lifecycle features (lockfile, rollback, updates).

Server Categories

Contributing

Want to add an MCP server? See CONTRIBUTING.md.

TL;DR: Create a YAML file, submit a PR, CI validates automatically.

Project Structure

mcphub/
├── registry/
│   ├── servers/        # 40 curated server YAML configs
│   ├── bundles/        # 5 curated bundles
│   └── discovered/     # 400+ auto-discovered servers
├── cli/                # Standalone CLI (npx mcphub)
├── website/            # GitHub Pages static site
├── schema/             # JSON Schema for validation
├── scripts/            # Validate, build, discover, health-check
└── .github/workflows/  # CI: validate PRs, build, release, discover, health

License

MIT