Girish Konda

MCP Pacemaker

Keep your MCP servers outside the editor.

Editors and one-shot CLIs often own the stdio MCP servers they start. When the host exits, those subprocesses stop too. MCP Pacemaker moves process supervision into a local bridge.

I built it to keep server setup and diagnostics in one place, rather than repeat them for every editor and agent CLI.

Source on GitHub Package on npm

  • Manage MCP server processes and OS auto-start from one place on Windows, macOS, and Linux.
  • Isolate sessions by default, with opt-in pre-warming and compatible process sharing.
  • Inspect connected clients, server health, and durable logs through local web and terminal dashboards, without opening an editor.
Demo
Clock-tool recording: two isolated launches, one shared launch, none added on reconnect.
Recorded with 2.1.0 on Windows: two isolated launches, one shared, none added on reconnect. The clock-tool clients use identical initialization and empty capabilities; this is not a speed or cross-editor compatibility test.

Try it

npm install -g mcp-pacemaker
mcp-pacemaker init

Node 22 or 24, run as a normal user. init asks before it rewires any host and backs up the config files it edits; mcp-pacemaker uninstall undoes it. Full setup guide

Available releases

Deep dive