Skip to content

Missing handler for request type: notifications/initialized #777

@woweow

Description

@woweow

Please do a quick search on GitHub issues first, there might be already a duplicate issue for the one you are about to create.
If the bug is trivial, just go ahead and create the issue. Otherwise, please take a few moments and fill in the following sections:

Bug description
I am getting the following errors from my MCP:

ERROR io.modelcontextprotocol.server.transport.HttpServletStatelessServerTransport - Failed to handle request: Missing handler for request type: notifications/initialized

Environment
version 17.1 of the MCP SDK. Running kotlin

Steps to reproduce
Unable to reproduce - seems like a client is more up to date on the spec than we are but I haven't been able to determine which

Expected behavior
I wouldn't expect anything a client says to my server to fail the protocol. I think we need an additional handler? Maybe I am dumb but in the past when I had this issue for tools et all, I just needed to explicitly say that I don't support them:

    private val SERVER_CAPABILITIES: McpSchema.ServerCapabilities = McpSchema.ServerCapabilities.builder()
        .prompts(true)
        .tools(false)
        .resources(false, false)
        .completions()
        .build()

however there is not a "notifications" capability

Minimal Complete Reproducible example
Unable to reproduce right now. I am guessing some update was made to MCP which we don't have yet in 17.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions