Skip to content

MCPs are loaded but not appearing as such in the MCP panel Window #30328

Closed

Description

@walidsi

Description

MCPs are loaded and working but not appearing as such in the MCP panel Window. This is happening in the latest Desktop app v1.15.13

Image Image

Plugins

No response

OpenCode version

v1.15.13

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

Windows 11

Terminal

OpenCode Desktop

Activity

  1. github-actions commented on Jun 2, 2026

    @github-actions
    Contributor

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

    Please review those issues and consider adding your information there if they match your situation.

  2. szsnzz commented on Jun 2, 2026

    @szsnzz

    Same here on Windows 11 (build 26200) + OpenCode Desktop v1.15.13 (sidecar core also reports version: '1.15.13'). Adding confirmation details since this issue had no repro steps yet.

    Key point: the MCP servers are fully working — only the panel is empty.

    I verified the backend is alive while the panel shows "No MCPs configured":

    • The MCP child processes are actually running (confirmed mcp-server-fetch, markitdown-mcp, mineru-converter-mcp-server, and the Node server-filesystem all spawned).
    • All four MCP tools are callable and return correct results (e.g. filesystem.list_allowed_directories, fetch, markitdown, mineru) — so this is purely a UI/state display regression, not a real load failure.

    This matches the analysis in #30130 pointing at PR #28937 (fix(app): start MCP servers only for open directories), whose own description notes "Core MCP startup behavior are unchanged" — consistent with backend-works-but-panel-empty.

    Extra observation: closing and re-opening the workspace tab does not bring the panel back, so the "only for open directories" gating isn't recovered by re-opening the directory.

    My MCPs are all defined in the global ~/.config/opencode/opencode.json (the project opencode.json only has a permission block, no mcp). The 1.15.13 location-scoped config loading change (#29625) may make global-only MCPs more likely to be missed by the panel.

    Config was unchanged across the update — v1.15.12 displayed all MCPs correctly, v1.15.13 does not.

  3. Hona commented on Jun 4, 2026

    @Hona
    Member

    Fixed in next version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions