MCP Manager Local

Created By
silastorres14a year ago
Server para gerir os servidores de MCP
Overview

what is MCP Manager Local?

MCP Manager Local is a simple web-based manager for starting, stopping, configuring, and viewing logs of MCP (Multi-Capability Protocol) servers, with features for cloning new servers from Git repositories and adding configurations via JSON.

how to use MCP Manager Local?

To use MCP Manager Local, clone the repository from GitHub, install the dependencies, and run the server. Access the web interface at http://localhost:3000 to manage your MCP servers.

key features of MCP Manager Local?

  • Web interface for managing MCP servers
  • Start and stop individual server processes
  • Add configurations manually or via JSON
  • View real-time logs of server output
  • Clone Git repositories containing MCP servers
  • Save server configurations locally in servers.json

use cases of MCP Manager Local?

  1. Managing multiple MCP servers from a single interface.
  2. Cloning and configuring new servers quickly from Git repositories.
  3. Monitoring server logs in real-time for troubleshooting.

FAQ from MCP Manager Local?

  • What are the prerequisites for using MCP Manager Local?

You need Node.js (version 18 or higher) and Git installed on your machine.

  • How do I add a new server configuration?

You can add a new server configuration manually through the web interface or by pasting a JSON object in the designated section.

  • Is there a way to create an executable version of MCP Manager Local?

Yes, you can build an executable using the pkg tool after setting up the project.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
silastorres14
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
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)

a day ago