feat(remote): add remote server capabilities

[Fluf22]

What

• extract common code between stdio and HTTP servers
• add --transport flag to CLI
• add Streamable HTTP support
• add SSE backward compatibility
• add config example with gateway to README

Todo

• We could use some more modern server like HonoJS
• OAuth should be done at the server level, not at the MCP app level, to link auth to the user session
• User sessions should be handled by a Redis or similar
• The HTTP server uses the example InMemoryEventStore for events, but it should use something more robust for production

[seafoox]

OAuth should be done at the server level, not at the MCP app level, to link auth to the user session

Agree would be great if we could obtain the accessToken connecting to the website, and then setting that one via an ENV variable. In a context like n8n, that would allow to deploy the MCP server one, and declare multiple instance via n8n nodes. Each instance potentially pointing to its own Algolia account.

[Fluf22]

@seafoox any particular reason why you erased all my code from today? 😄

[seafoox]

@seafoox any particular reason why you erased all my code from today? 😄

Sounds like I don’t know how to use GitHub desktop UI 🤦‍♂️ - I did not even realized I made a commit and push. I should stick with the CLI next time. Really sorry about that. I’ll revert my commit tomorrow. Or feel free to do it by the if you’re quicker.

[Fluf22]

@seafoox Could you work on your own branch, based on mine, please?

[bytrangle]

How do you "initialize with POST to /mcp"? What should be in the request body? Overall it's a very cool implementation and I'm looking forward to it.

[Fluf22]

@bytrangle hey! Most MCP clients implement this part themselves
If you are looking how to implement a client yourself, the initialize request must be a POST request with a payload matching this

For documentation, I'd recommend that or checking the inspector code

Good luck!