Want to set up as standalone server

[Mattheinrichs]

Believe this is more of a feature request than a defect, but thought I would drop this here.
I want to deploy this image to my docker server and keep it separate. Unfortunately, the entrypoint appears to only support taking a command, starting up, and then shutting down again. Am I mistaken?
If so - is there a way to keep the MCP server running to accept commands continuously from my editor (in this case, I'm running Cline within Studio Code Server on my (tiny) HA server).

[voska]

we don't currently support http-streaming as a transport right now, but i'll leave this issue open to track it.

[Mattheinrichs]

Hmm... I was just thinking about more of a wrapper that's persistent and activates the python app the same way it's being called today.
Alternatively, is it possible to think about this as an add-on, where HA is managing the docker image directly? I'm sure there's more scaffolding needed to get it in as an add-on though.

[voska]

it just needs a way to handle requests beyond STDIO, which is the current method (and why you need one docker instance per mcp client)

the canonical solution would be an http transport: https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#streamable-http

[Mattheinrichs]

Thank you - that context helps. Given that, I'm going to play around with mcp-proxy as a way to solve this for myself for now.

[ForceConstant]

it just needs a way to handle requests beyond STDIO, which is the current method (and why you need one docker instance per mcp client)

the canonical solution would be an http transport: https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#streamable-http

Since you are using mcp/FastMCP, isn't just a matter of telling it to use StreamableHTTP? https://github.com/modelcontextprotocol/python-sdk?tab=readme-ov-file#streamable-http-transport in the run() command?

[M4Al]

I made a PR to change this whole project to streamable http.

#24

[jsapede]

would be a général hood idea to provide streaming instead of stdio as mcp server can ben anchored on other llm tools than Claude, like librechat or openwebui that themselves run in docker.m, meaning cailing docker from inside another docker meanwhile they just coule run alongside with intra docker streams

[voska]

agreed! I'll try to get it done this weekend

[jsapede]

been looking quickly it seems mounting .sock inside thé master container would be sufficient to run thé mcp container and interact via stdio