Log inSubmit server
Universal MCP Toolkit logo

Universal MCP Toolkit

by Markgatcha

Aggregates MCP servers behind one CLI for discovery, configuration, workflows, composition, local execution, and diagnostics.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Universal MCP Toolkit

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "markgatcha-universal-mcp-toolkit": {
      "command": "npx",
      "args": [
        "-y",
        "universal-mcp-toolkit"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y universal-mcp-toolkit

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

Markgatcha/universal-mcp-toolkit MCP server provides a unified CLI and runtime for discovering, configuring, running, and composing multiple MCP servers. It supports stdio and HTTP+SSE transports, generated client configuration, cross-server workflows, tool discovery, diagnostics, caching, and session orchestration. Reach for Markgatcha/universal-mcp-toolkit MCP server when an agent setup spans several MCP integrations and you want shared configuration and routing instead of managing each server separately.

Use cases

  • Configure several MCP servers for Claude Desktop
  • Discover tools across a multi-server installation
  • Validate a cross-server JSON workflow
  • Run and diagnose a selected MCP server locally

Key features

  • Unified MCP server registry and CLI
  • Stdio and HTTP+SSE transport support
  • Cross-server workflow validation and execution
  • Tool discovery and server composition
  • TTL/LRU result caching
  • Lazy loading and transport health handling

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

6/6 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · universal-mcp-toolkit (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars15Stargazers on the source repository.
npm downloads80Package downloads in the last 30 days.
Last commit23d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity7 viewsConfig copies, upvotes, and views on AllMCPs.

How Universal MCP Toolkit works

What Markgatcha/universal-mcp-toolkit MCP server does

Markgatcha/universal-mcp-toolkit MCP server is an open-source TypeScript monorepo and command-line toolkit for working with multiple MCP servers from one setup. It includes a shared runtime, a server registry, configuration generation, execution commands, discovery features, and composition utilities. The repository lists integrations spanning collaboration, productivity, data, platform, research, local-file, and memory use cases, including GitHub, Slack, Notion, databases, cloud platforms, and FileSystem.

The toolkit is intended for developers who need a consistent way to select MCP servers, produce host configuration, run servers locally, and connect tools across server boundaries. It is also presented as a reference implementation with shared validation, logging, error handling, and packaging conventions.

How it works

The universal-mcp-toolkit CLI provides commands for listing available servers, interactively installing a selection, generating configuration for Claude Desktop, running a selected server, checking its environment, and validating workflows. Tool discovery can search across the available servers by name or category. Registry-compatible and local discovery modes are also supported.

Cross-server workflows are represented as versioned JSON files with validated inputs and step references. The toolkit also retains a simpler composition mode for piping output between two steps. Its session abstraction can coordinate calls to several MCP servers in parallel, while typed tool chains support compile-time-checked pipelines.

At the runtime level, the toolkit supports stdio and HTTP+SSE transport handling. It includes lazy loading for server packages and tool registration, TTL/LRU result caching, reconnect and circuit-breaker behavior for transport failures, and structured bridge errors containing tool and argument context. Streaming calls expose completed result chunks through an asynchronous iterator; the README distinguishes this from protocol-level streaming.

Setup and configuration

The quick-start examples use the npm package through npx, with commands such as npx universal-mcp-toolkit list, install, config, run, doctor, and workflow validate. A global npm installation is also documented, after which the executable is available as umt.

Interactive setup can select servers, choose a transport, and write configuration. The config command can generate a Claude Desktop configuration snippet for named servers. Individual integrations may require their own credentials; the README’s server table identifies examples such as GITHUB_TOKEN, NOTION_TOKEN, SLACK_BOT_TOKEN, and LINEAR_API_KEY, but the required variables depend on the selected server.

Tools and capabilities

  • Discover servers and tools through the CLI
  • Generate host configuration for selected MCP servers
  • Run servers over stdio or HTTP+SSE
  • Validate and run JSON-defined multi-server workflows
  • Compose short tool pipelines
  • Coordinate calls through multi-server sessions
  • Cache tool results with TTL and LRU behavior
  • Diagnose server environments and transport problems
  • Load server packages and expensive tools lazily

Limitations and notes

The toolkit is an aggregator and runtime layer, not a replacement for the credentials or external services used by its individual integrations. Configuration requirements therefore vary by server. Its documented chunk iterator does not represent MCP protocol-level streaming, and ordinary tool-validation errors are not treated as transport failures by the circuit breaker.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Universal MCP Toolkit

Yes. Its `config` command can generate a Claude Desktop configuration snippet for selected servers.

Yes. It provides a unified configuration, multi-server sessions, tool routing, server composition, and cross-server workflows.

The toolkit supports stdio and HTTP+SSE transport modes.

The toolkit itself does not specify one universal credential, but individual integrations can require environment variables such as `GITHUB_TOKEN`, `NOTION_TOKEN`, or `SLACK_BOT_TOKEN`.

Related MCP servers

All in Aggregators All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewUniversal MCP Toolkit AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/markgatcha-universal-mcp-toolkit?style=directory)](https://allmcps.com/mcp/markgatcha-universal-mcp-toolkit)
HTML Embed
<a href="https://allmcps.com/mcp/markgatcha-universal-mcp-toolkit"><img src="https://allmcps.com/api/badge/markgatcha-universal-mcp-toolkit?style=directory" alt="Universal MCP Toolkit on AllMCPs" /></a>