Feature hasn't been suggested before.
Describe the enhancement you want to request
When one opencode serve instance has multiple clients connected with opencode attach, the MCP enabled/disabled state is currently shared by clients using the same directory.
Each attached session should be able to independently choose which configured MCP servers are available to it. Disabling an MCP in one session must not change its availability in any other session. The server should continue sharing the underlying MCP processes and connections rather than starting a separate process for every session.
This is distinct from persisting MCP state across restarts and from supplying a different MCP configuration when creating a session.
Feature hasn't been suggested before.
Describe the enhancement you want to request
When one
opencode serveinstance has multiple clients connected withopencode attach, the MCP enabled/disabled state is currently shared by clients using the same directory.Each attached session should be able to independently choose which configured MCP servers are available to it. Disabling an MCP in one session must not change its availability in any other session. The server should continue sharing the underlying MCP processes and connections rather than starting a separate process for every session.
This is distinct from persisting MCP state across restarts and from supplying a different MCP configuration when creating a session.