UMT overview

Universal MCP Toolkit: install, connect, and run 28 curated MCP servers across every major coding harness.

Universal MCP Toolkit (UMT) is one CLI and runtime for 28 curated MCP servers. It writes the config each harness expects, starts servers over stdio or HTTP, and checks the environment before you waste time debugging a missing token.

Why it exists

MCP is a good protocol with a bad onboarding story. Every server has its own package, its own environment variables, and its own config shape. Every host expects a different file. UMT collapses that into one workflow:

1. umt list shows what is available.
2. umt connect picks servers and a harness.
3. UMT writes the real config file, with a backup.
4. umt run starts a server locally.
5. umt doctor explains what is broken.

60-second quickstart

# See every server, grouped by category
npx -y universal-mcp-toolkit list

# Preview a Claude Code config for two servers
npx -y universal-mcp-toolkit config -s github hackernews -t claude-code

# Guided flow: pick servers, pick a harness, write the config
npx -y universal-mcp-toolkit connect

# Run one server locally
npx -y universal-mcp-toolkit run github --transport stdio

# Check build output, config, and env vars
npx -y universal-mcp-toolkit doctor

What is in the box

The shared core is why every server behaves the same way: one bootstrap path, one logging format, one env loader, one registration pattern.

What makes it different

Next