fix: local MCP servers spawn twice, once for home dir

[dragon-Elec]

Description

Each local MCP server spawns twice at startup under the same opencode serve --service parent. The log shows one mcp connected per server with directory=<project>, and a second with directory=/home/ray. Both stay alive for the whole session.

Only one session is open (session_v2 has a single row updated in the last hour, in the project dir). Killing the service and relaunching from the project dir does not fix it — the home pair comes back at launch ("starting bg server" on every start).

Plugins

opencode-magic-context, aft-opencode, oh-my-opencode-slim, local V2 adapter (file shim in ~/.config/opencode/plugins/)

OpenCode version

2.0.18

Steps to reproduce

1. Configure a local MCP server (I have daisyui + skeleton-ui).
2. cd <project> && opencode
3. Check processes: ps -o pid,ppid,lstart,rss,args | grep mcp_server — two processes per server, started the same second.
4. Check the log: two mcp connected lines per server, one with directory=<project>, one with directory=/home/ray.

Operating System

Ubuntu (Linux x64)

Terminal

opencode TUI

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• #43845: the V2 service spawns local MCP servers for cataloged project directories at startup.
• #49209: the background service boots the home directory as an unrequested location, starting another set of MCP servers.
• #51003: global stdio MCP servers are spawned once per loaded directory.

[dragon-Elec]

Closing as duplicate of #49209 (home booted as unrequested location). Same symptom on 2.0.18/Linux: two MCP pairs with directory=/home/ray and directory=, single live session, survives full restart. Related: #43845 (general per-directory spawn), #50758 (reload trigger without reaping), #51003 (memory angle).