Description

Implement the HTTP transport using SSE. The CLI tool automatically determines whether the connection is an http or stdio by checking the command's arguments. If it is only 1 argument and starts with http:// or https://, it uses HTTP instead of stdio.

Hi Fatih, this project looks pretty cool, MCP is relatively new and I wanted to contribute. It's been a while since I have written Go so let me know if anything looks odd.

Also, I have implemented the solution based on "Final" edition. The "Latest" version actually changed quite a bit of things, it is much more complicated and I couldn't find any example project that used the new protocol (TBH I did not search hard enough).

https://spec.modelcontextprotocol.io/specification/2025-03-26/basic/transports/

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

I have run the "everything" MCP server using a docker image,

docker run -p 3001:3001 --rm -it tzolov/mcp-everything-server:v1

Later, I have conducted the test manually by calling the existing functionality,

Note that for some reason server exits when the connection is broken.

I belive there might be some kind of bug with tool calls in shell mode, I couldn't make it work.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules