Feature Summary

MCP panel only reads ~/.claude.json and ~/.config/opencode/opencode.json. Project-scoped configs and Claude Code plugin MCPs don't show up, even though Claude Code loads them at runtime when emdash launches it.

Problem or Use Case

Open a project in emdash, panel shows e.g. 5 MCPs. Run Claude Code in the same project and there's potentially way more available - like those from the project's opencode.json, plus stuff from Claude Code plugins, etc. They all work fine because emdash just launches Claude Code and Claude picks them up. The panel just doesn't reflect any of it.

Proposed Solution

Surface them in the panel somehow, read-only is fine. The project-scoped configs are at known paths (.mcp.json, project opencode.json, etc.) and Claude Code plugin MCPs live under ~/.claude/plugins/. Just so the panel matches what Claude Code actually loads.

Alternatives Considered

Copy every project/plugin MCP into the global config so emdash sees it. Annoying, goes stale.

Additional Context

• [proposal]: mcp server management #1009 (closed proposal — table covered project paths but impl only did global)
• [feat]: Plugins Marketplace Support #1729 (plugin marketplace — different scope, install plugins from emdash vs show plugins already installed)