1MCP - One MCP Server for All

A unified Model Context Protocol server implementation that aggregates multiple MCP servers into one.

Overview

1MCP (One MCP) is designed to simplify the way you work with AI assistants. Instead of configuring multiple MCP servers for different clients (Claude Desktop, Cherry Studio, Cursor, Roo Code, Claude, etc.), 1MCP provides a single, unified server.

Related MCP server: MCP Starter

Features

• 🔄 Unified Interface: Aggregates multiple MCP servers into one

• 🔒 OAuth 2.1 Authentication: Production-ready security with scope-based authorization

• ⚡ High Performance: Efficient request forwarding with proper error handling

• 🛡️ Security First: Stdio transport isolation, input sanitization, and comprehensive audit logging

• 🔧 Easy Configuration: Single JSON configuration file with hot-reload support

• 📈 Health Monitoring: Built-in health check endpoints for monitoring and observability

Quick Start

1. Install 1MCP

Binary (Recommended - No Node.js Required):

NPM:

2. Add MCP Servers

3. Start the Server

4. Connect Your AI Assistant

For Cursor, add to ~/.cursor/mcp.json:

For VSCode, add to settings.json:

Install MCP Server to VSCode

For Claude Code:

That's it! All your MCP servers are now available through one unified endpoint. 🎉

Commands

Core Commands

• 1mcp [serve] - Start the 1MCP server (default command)

• 1mcp mcp add <name> - Add a new MCP server to configuration

• 1mcp mcp list - List all configured MCP servers

• 1mcp mcp status [name] - Show server status and details

For detailed command usage, run: 1mcp <command> --help

Documentation

📚 Complete Documentation - Comprehensive guides, API reference, and examples

Key Topics

• Installation Guide - Binary, NPM, and Docker installation

• Quick Start - Get running in 5 minutes

• Configuration - CLI flags and environment variables

• Authentication - OAuth 2.1 security setup

• Architecture - How 1MCP works internally

• Development - Contributing and building from source

How It Works

1MCP acts as a proxy, managing and aggregating multiple MCP servers. It starts and stops these servers as subprocesses and forwards requests from AI assistants to the appropriate server. This architecture allows for a single point of entry for all MCP traffic, simplifying management and reducing overhead.

Contributing

Contributions are welcome! Please read our CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.

License

This project is licensed under the Apache License 2.0. See the LICENSE file for details.