restart-server

Reload Willow MCP server modules with Postgres reconnection and fleet reimport.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/rudi193-cmd/Aionic-Claude-Skills --skill restart-server
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: restart-server
Source: https://github.com/rudi193-cmd/Aionic-Claude-Skills/tree/main/skills/restart-server
Command: npx skills add https://github.com/rudi193-cmd/Aionic-Claude-Skills --skill restart-server

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reload the Willow MCP server modules without restarting the process or the session, enabling zero-downtime updates.

Core Features & Use Cases

  • Flexible hot-reload of MCP modules
  • Automatic fleet reimport and Postgres reconnection verification
  • Post-reload status reporting to confirm readiness

Quick Start

Trigger the MCP hot-reload workflow by issuing mcp__willow__willow_reload with target 'all' and then verify fleet, Postgres, and store readiness.

Frequently Asked Questions about restart-server

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

FAQPage Schema
How do I hot-reload MCP server modules without downtime?

To hot-reload MCP server modules without downtime, trigger the mcp__willow__willow_reload workflow with target 'all'. This safely reconnects Postgres, reimports the fleet, and refreshes WillowStore while the process stays running.

What is zero-downtime hot-reload for Willow MCP servers?

Zero-downtime hot-reload is updating Willow MCP server modules without restarting the process or session. It automates deterministic sequencing and post-reload verification to ensure database connections and fleet configurations remain healthy.

When do I need to reimport the fleet and reconnect Postgres?

You need to reimport the fleet and reconnect Postgres whenever server modules or fleet configurations are updated, including changes to willow_store_mcp.py, pg_bridge.py, or fleet modules, to maintain session stability.

How do I verify readiness after an MCP server module reload?

To verify readiness after an MCP server module reload, check the post-reload status reporting. It confirms module reloads, fleet re-imports, and Postgres database connections are healthy and ready for operations.

Does hot-reloading MCP modules work with active Postgres connections?

Yes, hot-reloading MCP modules works with active Postgres connections. The workflow automatically reconnects the Postgres database and verifies the connection health as part of the deterministic reload sequence.