You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Regression: MCP prompts are no longer listed after connecting MCP server #28579
Previously, when an MCP server was connected to OpenCode, the prompts exposed by the MCP server were listed and could be selected/used from OpenCode.
In the current version, the MCP server connects successfully, but MCP prompts are not listed anymore.
Tools may still work, but prompts are missing from the UI/autocomplete/listing with /. This looks like a regression because the same MCP server setup used to show the prompts in older OpenCode versions.
Expected behavior
When an MCP server exposes prompts, OpenCode should list those prompts after the MCP server is connected.
For example, prompts should be visible/usable from the relevant prompt list/autocomplete, similar to the previous behavior.
Actual behavior
The MCP server is connected, but the prompts exposed by the MCP server are not shown/listed.
Steps to reproduce
Configure an MCP server that exposes one or more prompts.
Start OpenCode with this MCP server configured.
Verify that the MCP server is connected.
Try to list/select/use MCP prompts.
Observe that MCP prompts are not listed.
Regression
Yes. This used to work in older OpenCode versions. After upgrading to the current version, MCP prompts are no longer listed.
While your issue describes a regression where prompts used to work and no longer appear (rather than a server not implementing prompts/list at all), the root cause may overlap. Please review the above issues to see if they address your problem or if this is a distinct regression.
I think this regression is caused by Command state being cached via InstanceState (a ScopedCache with infinite TTL) and never invalidated when MCP clients connect or their prompts change. The MCP.ToolsChanged bus event exists but no subscriber invalidates the Command cache, so if MCP prompts aren't available at Command init time, they never appear.
I'll work on a fix that subscribes to MCP state changes and invalidates the Command cache accordingly.
MCP prompts are listed correctly when the MCP server is enabled during OpenCode startup. But when the same MCP server is enabled manually after startup, the prompts are not listed.
Activity
github-actions commentedon May 21, 2026
This issue might be a duplicate of existing issues. Please check:
prompts/list— related issue about MCP prompts/list errors causing visibility problemsprompts/listis unsupported (-32601) — related issue about prompt listing errors and MCP compatibilityWhile your issue describes a regression where prompts used to work and no longer appear (rather than a server not implementing
prompts/listat all), the root cause may overlap. Please review the above issues to see if they address your problem or if this is a distinct regression.Arcadi4 commentedon May 21, 2026
Cannot reproduce under
1.15.16, perhaps this is already fixed?kagura-chen commentedon May 21, 2026
I think this regression is caused by
Commandstate being cached viaInstanceState(aScopedCachewith infinite TTL) and never invalidated when MCP clients connect or their prompts change. TheMCP.ToolsChangedbus event exists but no subscriber invalidates the Command cache, so if MCP prompts aren't available at Command init time, they never appear.I'll work on a fix that subscribes to MCP state changes and invalidates the Command cache accordingly.
mustafagoksever commentedon May 21, 2026
MCP prompts are listed correctly when the MCP server is enabled during OpenCode startup. But when the same MCP server is enabled manually after startup, the prompts are not listed.
github-actions commentedon Jul 21, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.