Bug: `notifications/initialized` should be sent from client, not server

[longseespace]

Overview

There seems to be a bug here I believe? According to the lifecycle (https://modelcontextprotocol.io/specification/2024-11-05/basic/lifecycle) this notification must be sent from the client, not server.

Currently, I don't see the client sending this notification at all. And because of this I wasn't able to perform any operations with some server (Fetch MCP Server for example).

Ref:

swift-sdk/Sources/MCP/Server/Server.swift

Line 502 in 29aa74d

try? await self.notify(InitializedNotification.message())

[stallent]

Ha, I actually have a fix for that in a PR i'm working on now resolving issues with the new streamable client.

FWIW you can send it yourself like this

let notificationData = try JSONEncoder().encode(InitializedNotification.message())
try await transport.send(notificationData)

[longseespace]

Thanks. I just fixed it in my fork.

[mattt]

Hi @longseespace. You're totally right. Sorry about that oversight. I just opened a PR with a fix here with #85