restart

Restarts the CALM local MCP server process to apply plugin code updates.

3|1|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/isizono/calm --skill restart-isizono
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: restart
Source: https://github.com/isizono/calm/tree/main/skills/restart
Command: npx skills add https://github.com/isizono/calm --skill restart-isizono

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After updating the CALM plugin, the running MCP server keeps using old code because the launcher only starts a new process when none is alive. This Skill forcefully terminates the existing MCP server process and starts a fresh one so code changes take effect. ## Core Features & Use Cases - Forced MCP Server Restart: Kills the existing server on port 52837 and launches a new process via a dedicated restart script. - Optional Embedding Server Restart: The embedding server on port 52836 is excluded by default and only restarted when --restart-embedding is explicitly passed. - Structured JSON Reporting: The script returns JSON results covering dependency sync, old/new PIDs, and cache cleanup, which the Skill interprets and reports to the user. - Use Case: After pulling a new version of the CALM plugin, invoke this Skill so the updated server code is loaded without manually hunting down processes. ## Quick Start Ask the AI to restart the CALM MCP server, for example by saying "restart the CALM server" or invoking /restart.

Frequently Asked Questions about restart

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I restart the CALM MCP server after a plugin update?▼

Invoke the restart Skill, which runs restart_server.py via uv to kill the existing MCP server on port 52837 and start a new process. The script returns JSON with old and new PIDs confirming the restart.

Why doesn't my CALM plugin update take effect after upgrading?▼

The launcher only starts a server if none is running, so an existing process keeps old code loaded. Force a restart through this Skill to terminate the stale process and load the updated code.

Does restarting the MCP server also restart the embedding server?▼

No, the embedding server on port 52836 is excluded by default and respawns lazily when encoding is next needed. Pass the --restart-embedding flag only when embedding_server.py code changed.

What should I do if the MCP server restart fails or times out?▼

Check the detail field in the JSON output and verify the port manually with lsof -i tcp:52837 -sTCP:LISTEN. Timeouts can occur on the first run after an update due to venv rebuilds, so retry the command.

Do other Claude Code sessions need action after a server restart?▼

Yes, other running sessions may need to reconnect to the MCP server. Open /mcp in each session and reconnect if the connection was dropped by the restart.