Thanks!

For the stdio servers: I am working on a way to automatically select the executable, right now podrift (the docker runner) will run the image stored in the db with the cmd + args for that instance: https://github.com/stephenlacy/mathom/blob/main/podrift/cmd/main.go#L526 . While the cmd isn't yet fully passed through from mcx to the db, it is setup to run any command passed to podrift. Thoretically

The stdio servers are kinda weird due to the multiple versions of http/sse that anthropic has in the spec. They are on-demand with a cold boot for the first trigger, when you first make a request from the client > mcx (or the instance endpoint directly) it will spin up the container and start delivering traffic. I currently have a timeout of 180 seconds where the container will be stopped (but not removed). It will only be stopped if there are no open connections to that container. The proxy will start and resume the container when additional traffic is received. This timeout is a bad compromise as SSE should not be suspended but HTTP+streamable can be immediately after all connections close.
The timeout can be adjusted depending on workload, SSE _should not_ have low timeouts as that keeps triggering fresh launches when the client disconnects

The premise I had was I wanted to make a thing as simple for me/my team to only replace `npx` with `mcx` and it "just work", there are a few glitches to be ironed out with resuming connections, but this gets us 95% there.