Monitor and restart MCP (Model Context Protocol) servers for Cursor, VS Code, Windsurf, Claude Desktop, Claude Code, and GitHub Copilot from one terminal. A lightweight TUI (terminal UI) and optional Web UI discover your MCP configs, show which servers are running or stopped, and let you kill or restart them—no install into any AI tool required.
Works on Windows, macOS, Linux, and WSL.
- Screenshots
- Quick start
- What is this?
- CLI reference
- Supported tools & config locations
- Terminal UI
- Web UI mode
- How it works
- Cross-platform behavior
- Logging
- Troubleshooting
- Requirements
- Contributing
- Links
Terminal UI — server list with status, PID, command, and config path.
Terminal UI — Server Details view (press d). Full command, paths, and masked sensitive values in environment where applicable.
Web UI (--ui) — browser dashboard with status summary, action toolbar, sortable server table, and activity log (auto-refresh in the browser).
Run with npx—no clone or global install needed:
# Terminal UI mode (default)
npx simple-mcp-manager
# Web UI — served at http://localhost:3000 by default
npx simple-mcp-manager --ui
# Web UI on a specific port
npx simple-mcp-manager --ui --port 8080Install globally:
npm install -g simple-mcp-manager
mcp-manager # Terminal UI (default)
mcp-mgr --ui # Web UI (short alias)
simple-mcp-manager --ui # Web UI (full name)Clone and run from source:
git clone https://github.com/tamb/simple-mcp-manager.git
cd simple-mcp-manager
npm install
npm start # Terminal UI
npm run start:ui # Web UIA standalone CLI you run in a separate terminal. It is not an MCP server and does not need to be registered inside Cursor, VS Code, or other tools as an MCP entry. It reads the same config files those tools use and matches running processes on your machine so you can see and control local stdio-based servers from one place.
It does:
- Scan MCP config locations for all supported agents
- Show each configured server with run/stop (and related) status
- Offer restart, kill, kill all running, and restart all stopped for managed stdio processes
- Optionally serve a browser UI with the same operations and live refresh
Limitations to be aware of:
- HTTP / HTTPS / SSE MCP endpoints are listed with health probes but are not local processes you can kill or restart from this tool
- Log capture for a server is tied to processes the manager starts or restarts; servers already running before you open the manager may show “logs not available” until you restart them from the UI (see screenshots)
- Process matching is heuristic (command line, package names); unusual spawn setups may not classify perfectly
| Mode | Command | Description |
|---|---|---|
| TUI (default) | simple-mcp-manager |
Full-screen terminal interface |
| Web UI | simple-mcp-manager --ui |
HTTP server on localhost |
| Web UI port | --ui --port <n> |
Preferred port (default 3000); must be 1–65535 |
| Validate configs | --validate |
Check all MCP JSON configs; exit 1 on errors |
| Workspace root | --cwd <path> |
Directory for workspace-relative config discovery |
| Extra scan dirs | --scan-dir <path> |
Additional roots to scan (repeatable) |
Rules:
- The Web UI flag must be
--ui(there is no-uishorthand). - If the preferred port is busy, the server tries the next ports up (same behavior as before), within a limited range.
- Bin names:
mcp-manager,mcp-mgr, andsimple-mcp-manager(seepackage.jsonbin).
| Tool | Config locations |
|---|---|
| Cursor | ~/.cursor/mcp.json, %APPDATA%\Cursor\User\mcp.json, per-project ~/.cursor/projects/*/mcp.json, workspace .cursor/mcp.json |
| VS Code | ~/.vscode/mcp.json, %APPDATA%\Code\User\mcp.json (Win), ~/Library/Application Support/Code/User/mcp.json (Mac), ~/.config/Code/User/mcp.json (Linux), workspace .vscode/mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json, %APPDATA%\Windsurf\User\mcp_config.json (Win), ~/Library/Application Support/Windsurf/User/mcp_config.json (Mac), ~/.config/Windsurf/User/mcp_config.json (Linux), workspace .windsurf/mcp.json |
| Claude Desktop | %APPDATA%\Claude\claude_desktop_config.json (Win), ~/Library/Application Support/Claude/claude_desktop_config.json (Mac), ~/.config/claude/claude_desktop_config.json (Linux) |
| Claude Code | ~/.claude/mcp.json, ~/.claude.json, workspace .claude/mcp.json |
| GitHub Copilot | ~/.mcp.json, workspace .mcp.json |
Most tools use { "mcpServers": { ... } }. GitHub Copilot and VS Code use { "servers": { ... } }. The manager detects both shapes.
The TUI shows a sortable-style table (agent, server name, status, PID, command, type, config path), a short Activity Log, and a footer with shortcuts.
| Key | Action |
|---|---|
r |
Restart the selected server |
k |
Kill the selected server |
K |
Kill all running servers |
a |
Restart all stopped servers |
F5 |
Manual refresh |
d |
Server details modal |
l |
Logs (when applicable; from details or global shortcut) |
/ |
Search/filter servers |
e |
Export captured logs to file |
| Up / Down | Move selection |
q |
Quit |
Statuses use color and symbols (running, stopped, shared, HTTP, starting/stopping—see UI labels). Sensitive environment keys can be masked in detail views.
Run with --ui. Open the URL printed in the terminal (by default http://localhost:3000, or the next free port if 3000 is taken).
Features mirror the TUI in the browser:
- Sortable server table with status colors and search box
- Auto-refresh (5s typical, 15s on WSL)
- Buttons: Refresh, Restart, Kill, Kill All, Restart All Stopped, Details, Logs, Export Logs
- HTTP/SSE endpoint health (ok/down/latency in status and details)
- Details and log modals; activity log pane
- Keyboard shortcuts aligned with the TUI (
r,k,K,a,d,l,F5, arrows, Esc)
The page is self-contained HTML/CSS/JS—no bundler or extra assets needed.
Prefer --port:
mcp-mgr --ui --port 8080Default port is 3000. If unavailable, higher ports are tried automatically (bounded search).
- Enumerate known config paths per platform and workspace-relative files
- Parse
mcpServersorserversentries - Correlate configured commands with OS processes (
ps, PowerShell on Windows/WSL paths, etc.) - Refresh on an interval (5 s, or 15 s on WSL to reduce expensive Windows process queries)
- Actions call into the same process start/kill helpers for stdio servers; HTTP entries are informational
| Feature | Windows | macOS | Linux | WSL |
|---|---|---|---|---|
| Process detection | PowerShell | ps aux |
ps aux |
PowerShell (Windows processes) |
| Kill process | taskkill /PID /F (per PID) |
kill SIGTERM/SIGKILL |
kill SIGTERM/SIGKILL |
taskkill.exe /PID /F |
| Spawn process | shell: true for .cmd |
detached | detached | cmd.exe /C on Windows side when needed |
On WSL, the tool can observe MCP servers launched by Windows-hosted editors when those show up as Windows processes.
Diagnostic output is appended to logs/<timestamp>-log.txt under the installed package directory (next to index.js). If the directory cannot be created, logging fails silently so the CLI still runs. Use these files when reporting bugs.
| Issue | What to try |
|---|---|
| No servers listed | Confirm configs exist and JSON is valid; check table paths above |
| Wrong or “unknown” status | Refresh (F5); ensure the MCP command matches how the agent starts the server |
| Cannot kill / restart | HTTP servers cannot be controlled locally; some shared/cluster PIDs need care—use Details to see linkage |
| Web UI won’t bind | Pick another --port; check firewall or conflicting apps |
| WSL feels slow | Shorter refresh is skipped on purpose (15s); run from native OS if you need faster polling |
| “Logs not available” | Restart that server once from this manager (r) so stderr/stdout hooks attach |
- Node.js >= 18
See CONTRIBUTING.md for local development, npm link, packing with npm pack, and Pull Request workflow.
- Repository: github.com/tamb/simple-mcp-manager
- npm: simple-mcp-manager
- Model Context Protocol (MCP): modelcontextprotocol.io