mcp-client-helper

Created By
Yangbin-va year ago
mcp client helper(管理,执行 mcp server)
Overview

what is mcp-client-helper?

The mcp-client-helper is a management tool library designed for managing and controlling multiple MCP server instances through configuration files.

how to use mcp-client-helper?

To use mcp-client-helper, install it via npm and create a configuration file that defines the MCP servers you want to manage. Then, use the provided API to start, stop, and monitor the servers.

key features of mcp-client-helper?

  • Manage multiple MCP servers through configuration.
  • Support for starting, stopping, and restarting servers.
  • Real-time monitoring of all server statuses.
  • Event-driven logging and error handling.
  • Custom environment variable configuration support.

use cases of mcp-client-helper?

  1. Managing multiple instances of MCP servers for different projects.
  2. Automating server management tasks in a development environment.
  3. Monitoring server performance and logs in real-time.

FAQ from mcp-client-helper?

  • Can mcp-client-helper manage any type of server?

No, it is specifically designed for managing MCP servers.

  • Is mcp-client-helper free to use?

Yes, it is open-source and available under the MIT license.

  • What are the system requirements for mcp-client-helper?

It requires Node.js version 14.0.0 or higher and TypeScript version 4.0.0 or higher.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Yangbin-v
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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)

a day ago