Prevent servers without tools from being added/running #173
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses issue #108 by ensuring MCP servers always have at least one tool configured, preventing useless server configurations that cannot function.
Previously, servers could be added or modified to have zero/no tools, resulting in non-functional configurations that would run but provide no capabilities.
This could happen through:
.mcpd.tomlto remove all toolsmcpd config tools removeto remove all tools from a serverValidation:
mcpd add) - Prevents adding servers without toolsmcpd daemon) - Validates on startup and reload, exits if any servers lack toolsmcpd config tools remove) - Prevents removing the last tool, guides users to usemcpd removeinsteadUpdated docs on hot reload to mention the edge case.
Closes: #108