MCP Manager

Created By
kaichena year ago
A simple GUI for managing MCP servers, for easy toggle mcp servers.
Overview

what is MCP Manager?

MCP Manager is a simple graphical user interface (GUI) designed for managing Model Context Protocol (MCP) servers, allowing users to easily toggle between different MCP server settings.

how to use MCP Manager?

To use MCP Manager, download the application from its GitHub repository, install it on a compatible operating system (currently tested on MacOS), and launch the GUI to manage and configure your MCP servers.

key features of MCP Manager?

  • User-friendly GUI for managing MCP servers
  • Easy toggling of server settings
  • Powered by Tauri for a lightweight application experience

use cases of MCP Manager?

  1. Enabling and disabling specific MCP servers based on user requirements
  2. Managing server configurations for different projects utilizing MCP
  3. Testing MCP server functionality in various environments such as MacOS and Windows (ongoing testing)

FAQ from MCP Manager?

  • Which operating systems does MCP Manager support?

Currently, MCP Manager is tested on MacOS, with plans for Windows support in the future.

  • Is MCP Manager open source?

Yes! MCP Manager is open source and licensed under the Apache License 2.0.

  • How can I contribute to the MCP Manager?

You can contribute by checking out the GitHub repository and following the contribution guidelines provided there.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kaichen
Star
-
Language
-
License
-

Recommend Servers

View All
Alloy

2 days ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

12 hours ago
Crevio

a day ago