Add support for running MCP server initialization code #28
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.
Clients will typically invoke ListTools right after client initialization is complete. We don't attempt to run this code as a notification handler because those don't have access to the server instance and therefore are not very useful.
Running just before tools list is a good spot for post-initialized and before things can actually start running.
Note that doing elicitation in this context won't work, but other notifications/logging to the client should be perfectly functional at this stage.