Skip to content

MCP server initialization fails in v0.2.5: expect initialized response, but received LoggingMessageNotification #188

@echozyr2001

Description

@echozyr2001

Problem Description

The MCP server fails to initialize properly in version 0.2.5, causing client connection errors (antinomyhq/forge#1149) :

ERROR: Failed to initiate MCP server: desktop-commander

Caused by:
    expect initialized response, but received: Some(Notification(JsonRpcNotification { jsonrpc: JsonRpcVersion2_0, notification: LoggingMessageNotification(Notification { method: LoggingMessageNotificationMethod, params: LoggingMessageNotificationParam { level: Error, logger: Some("desktop-commander"), data: String("Loading configuration...") }, extensions: Extensions }) }))

Environment

Expected Behavior

MCP server should respond with proper initialization response before sending any notifications.

Actual Behavior

Server sends JSON-RPC notifications during initialization phase, violating MCP protocol specification.

Impact

  • MCP clients cannot connect to Desktop Commander
  • Complete service unavailability in affected version

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions