Is your feature request related to a problem? Please describe.

When mcpd receives a SIGHUP signal, it should reload it's config and apply changes.

This would allow MCP servers to be added/removed without requiring a restart to the mcpd instance, which may be preferable for local development or some production upgrade scenarios where only config changes (not the mcpd binary version).

Describe the solution you'd like

• Send SIGHUP to mcpd
• mcpd examines servers config:
  • Shutdowns and removes servers that have been removed from config
  • Adds and starts servers that have been added to config
  • Doesn't change running servers that aren't modified in config
• ❓could mcpd examine daemon config and reload the HTTP API etc?

Describe alternatives you've considered

• Could consider also adding an API endpoint, but it would have to be secured via admin style JWT to prevent abuse.

Additional Context

Consider how health endpoints would change, if a server was present and then is removed, do we change how it's tracked in the health endpoint (removed? or just goes away).

Self-Checklist

• I have read the Contributing Guidelines.
• I have searched the existing issues and found no duplicate.
• I have provided a clear and concise description of the problem.
• I have provided a clear and concise description of the proposed solution.