MCPMate

by loocor

Not rated
GitHub

About

MCPMate is a comprehensive Model Context Protocol (MCP) management center designed to address configuration complexity, resource consumption, security risks, and other issues in the MCP ecosystem, providing users with a unified management platform.

Details

Author
loocor
Categories
Productivity, Automation, Infrastructure

Setup

Install MCPMate in your MCP client (Claude Desktop, Cursor, Windsurf, and others).

Repository: https://github.com/loocor/mcpmate

Follow the installation instructions in the repository README, then restart your MCP client.

Your progressive MCP management partner.

Import MCP once. Start simple, then add profiles, per-client tools, and setup modes as your workflow grows.

MCPMate is a local-first assistant that grows with you—not just another config file editor.

MCPMate sits between your AI apps and MCP servers so you manage connections once and send the right tools to each app. It works with Claude Desktop, Cursor, Codex, Zed, VS Code, CLI tools, and other clients that follow the standard MCP config format.

Easy to begin, built to scale:one import with low friction; the same setup still fits as MCP spreads across more clients, servers, and scenarios—no product swap, no restart ritual.

Live site:mcp.umate.ai· Docs:mcp.umate.ai/docs

- MCPMate

- 📑 Table of Contents
-
🤔 Why MCPMate?
-
🔄 How It Works
-
🚀 Key Features
-
🛠️ Core Components

- Proxy
-
Bridge
-
Runtime Manager
-
Desktop App
-
Logs

- Option A: Download the Desktop App (Recommended)
-
Option B: Build from Source
-
Option C: Online Demo

Managing MCP across multiple AI tools (Claude Desktop, Cursor, Zed, Codex, and custom clients) gets messy fast:

flowchart LR subgraph mgmt ["🖥️ Management"] APP["Tauri Desktop"] DASH["Web Dashboard"] end subgraph proxy ["⚙️ MCPMate Proxy"] direction TB UP["Upstream Mgmt<br/><small>Connection Pool · OAuth 2.0 + PKCE</small>"] PROF["Profile Engine<br/><small>Scene · App · Dynamic</small>"] SEC["Event Logs &amp; Security<br/><small>Secure Store · Structured Logs · SQLite Catalog</small>"] UP --> PROF --> SEC end subgraph cfg ["🔧 Client Config"] direction TB DET["Detection &amp; Adapter"] MODES["Modes<br/><small>Transparent · Hosted · Unify</small>"] DET --> MODES end subgraph clients ["📱 AI Clients"] C["Cursor · VS Code · Zed · ..."] end subgraph upstream ["☁️ Upstream MCP Servers"] S["uvx · bunx · npx<br/>SSE · Streamable HTTP"] end subgraph market ["🛒 MCP Marketplace"] M["Official Registry"] end APP -->|"API"| proxy DASH -->|"API"| proxy market -.->|"Install"| proxy upstream -->|"stdio / HTTP"| proxy proxy -->|"Bridge / HTTP"| cfg MODES --> clients classDef mgmt fill:#e3f2fd,stroke:#1565c0,color:#000 classDef proxy fill:#fff3e0,stroke:#e65100,color:#000 classDef cfg fill:#e8f5e9,stroke:#2e7d32,color:#000 classDef clients fill:#fce4ec,stroke:#c62828,color:#000 classDef upstream fill:#f3e5f5,stroke:#6a1b9a,color:#000 classDef market fill:#fff9c4,stroke:#f9a825,color:#000 class APP,DASH mgmt class UP,PROF,SEC proxy class DET,MODES cfg class C clients class S upstream class M market

MCPMate sits between your AI clients and MCP servers. To each app it looks like a normal MCP endpoint—no workflow disruption—while profiles, policy, and routing stay in the middle layer. TheBridgeadapts stdio-only clients (such as Claude Desktop) to the HTTP proxy. TheProfile Enginedecides which tools each client sees—scene profiles for workflow context, app profiles for per-client tuning, and dynamic profiles that adjust at runtime.Transparent,Hosted, andUnifysetup modes let you choose how much MCPMate sits in the path versus writing native client configs.

A high-performance MCP proxy server that connects to multiple MCP servers and aggregates their tools. Implements stdio and Streamable HTTP transport protocols aligned with the current MCP specification. Accepts legacy SSE-configured servers and automatically normalizes them to Streamable HTTP for backward compatibility.

A lightweight bridging component that converts stdio protocol to HTTP transport without modifying the client. Automatically inherits all functions and tools from the HTTP service. Minimal configuration — only requires service address.

Installs and manages runtimes used by local MCP servers. Supports Node.js, uv (Python), and Bun with download progress tracking and automatic environment variable configuration.

runtime install node # Install Node.js for JavaScript MCP servers runtime install uv # Install uv for Python MCP servers runtime install bun # Install Bun runtime list # List installed runtimes

Cross-platform desktop application built with Tauri 2. Complete graphical interface for managing MCP servers, profiles, and tools with real-time monitoring, intelligent client detection, and system tray integration. macOS, Windows, and Linux desktop builds are currently available as Beta releases.

Structured operational log for MCP proxy activity. Collects MCP operations and management-side changes into a structured timeline with cursor-based pagination, REST APIs, and a dedicated Logs page in the dashboard UI.

Option A: Download the Desktop App (Recommended)

Download the latest release for your platform fromGitHub Releases.

Note: macOS builds are signed and notarized to reduce system security prompts and improve package trust.

macOS and Linux users can also install the Homebrew Beta cask withbrew install --cask loocor/tap/mcpmate@beta. See theInstallation guidefor updates and uninstall steps.

Prerequisites:Rust1.85+,Node.js18+ orBun, SQLite 3

git clone https://github.com/loocor/MCPMate.git cd MCPMate/backend cargo build --release

- REST APIonhttp://localhost:8080
- MCP endpointonhttp://localhost:8000

Dashboard available athttp://localhost:5173.

Coming soon. An online environment will let you explore the dashboard, profiles, and client configuration without a local setup.

- Integrated mode (desktop)— Tauri bundles backend + dashboard for local all-in-one operation
- Separated mode (core server + UI)— Run backend independently and connect either the web dashboard or desktop shell to that core service
- Client mode flexibility— Managed clients can continue using hosted/transparent workflows while the control plane runs remotely

# Run all checks ./scripts/check # Start backend + board together ./scripts/dev-all

SeeAGENTS.mdfor development guidelines, coding standards, and contribution workflow.
- Discovery-to-install polish— tighter browser extension, Market, README, and source-metadata flows
- Account-based configuration backup & restore
- Skills-mode packaged profiles
- Standalone Inspector— a focused path for MCP server connection, capability discovery, and call verification
- Read
AGENTS.mdfor development guidelines
- Open an issue to discuss significant changes
- Submit pull requests against themainbranch

GNU Affero General Public License v3.0(AGPL-3.0)

A manager server for MCP servers that handles process management and tool routing.

A self-hostable middleware to manage all your MCPs through a GUI and a local proxy, supporting multiple clients and workspaces.

Connect AI clients to Cal.com scheduling through the Model Context Protocol using the hosted server at mcp.cal.com or a local instance.

Sync Calendars, Scheduling Links, AI Executive Scheduling Assistant, Unified Calendar

Automated document processing and extraction

Create notes, search, & think with your Fabric AI workspace

Perform queries and entity operations in your Fibery workspace.

Magica is your all-in-one AI platform, offering 2500+ cutting-edge tools under a single subscription.

Turn your Make scenarios into callable tools for AI assistants.

No-code Slack MCP Client (Powered by Runbear)

Unlock MCP for your whole team in Slack with a single install.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.