Does vibe open and close stdio MCP servers?
Hi,
I am usually working with claude code and have built an stdio MCP server that usually stays alive. Claude Code starts this MCP server once and keeps it alive for the entire time sending commands to it.
Now I am testing mistral vibe with a local LLM with tool calling capabilities and I have noticed that MCP server is used differently in vibe. I observed that the MCP process is spawned for a short time and then instantly closed.
Is this as intended? I have designed my MCP to be stateful, so it actually needs to be running to be of use.
Does somebody else have similar experiences? Have I designed my MCP wrong, or can I configure vibe to keep the connection alive?
Edit: I was using devstral-small-2-24b-instruct-2512 and from how I understand MCP design it is stateful, so pulling MCPs up and down is not really the intended use case? What am I missing?