Skip to content

Conversation

peteski22
Copy link
Contributor

@peteski22 peteski22 commented Aug 22, 2025

What's changed

This PR implements hot reload functionality for mcpd, allowing dynamic reconfiguration of MCP servers without daemon restart via SIGHUP signal.

TL;DR

  • SIGHUP Signal Handling: Send kill -HUP <PID> to trigger configuration reload
  • Smart Change Detection: Intelligently categorizes configuration changes to minimize disruption
  • Tools-Only Updates: Updates allowed tools without restarting server processes when only tools change
  • Documentation added to docs/configuration.md (/mcpd/configuration/#hot-reload)

Closes: #150


SIGHUP no changes:

image

SIGHUP removed tools from jira leaving only search_jira_issues:

image

SIGHUP removed jira server:

image

SIGHUP added duckduckgo-mcp:

image

* Added documentation
* Implement equality checks for Server (ServerEntry and ServerExecutionContext)
* Added 'UpdateTools' to MCPClientAccessor (ClientManager)
* Update 'reload' logic for MCP servers to handle tool only changes etc.
*
@peteski22 peteski22 force-pushed the peteski22/150/reload-config branch from a6faa80 to 4353db9 Compare August 22, 2025 10:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Reload config changes on SIGHUP
1 participant