Skip to content

Conversation

@galachad
Copy link
Contributor

@galachad galachad commented Oct 16, 2025

This MR is necessary for standard operations.

Currently, the tools list request ends with an error.

{"jsonrpc":"2.0","id":2,"error":{"code":-32602,"message":"Invalid request parameters","data":""}}

After successful initialization, the client MUST send an initialized notification to indicate it is ready to begin normal operations.

The client SHOULD NOT send requests other than pings before the server has responded to the initialize request.

Reference: https://modelcontextprotocol.io/specification/2025-06-18/basic/lifecycle#lifecycle-phases

Copy link
Collaborator

@simonpcouch simonpcouch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, thank you!

Somehow I remember both the client (and server reply) initialized notification as a MAY, but this doesn't seem to be the case in any of the versions on the linked webpage. Strange.

Will go ahead and approve GHA—I believe roundtrip may be broken with this PR and we'll need to implement a reply in the server.

@simonpcouch simonpcouch merged commit 2105c5c into posit-dev:main Oct 19, 2025
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.

2 participants