server: should make SSE endpoint the same as official MCP servers

[deadprogram]

Hello, there! Thanks for this very useful project.

While doing some testing recently, it was pointed out to me that the typical endpoint for SSE is messages (plural) not message (singular) as it is in this project.

See https://github.com/mark3labs/mcp-go/blob/main/server/sse.go#L126

For example, see how the official Python SDK does it here:
https://github.com/modelcontextprotocol/python-sdk/blob/main/src/mcp/server/sse.py#L14

If agreed, I am happy to submit a PR with this change.

[ezynda3]

Hi @deadprogram I'm happy to accept a PR for this. Also FYI there is a way to set a custom endpoint name if you like. Also I believe that the endpoint is something that is exchanged during initialization so technically shouldn't matter?

[deadprogram]

Also FYI there is a way to set a custom endpoint name if you like.

I am currently using that, thanks for mentioning.

Also I believe that the endpoint is something that is exchanged during initialization so technically shouldn't matter?

That is true, however not all MCP clients are well behaved, apparently.

[a67793581]

Also FYI there is a way to set a custom endpoint name if you like.

I am currently using that, thanks for mentioning.

Also I believe that the endpoint is something that is exchanged during initialization so technically shouldn't matter?

That is true, however not all MCP clients are well behaved, apparently.

I'm glad you found this. I think you should submit this PR. I hope you can submit it as soon as possible.