Repository navigation
[FEATURE]: Port MCP lifecycle/status/connect/disconnect APIs to V2 #34435
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Port the MCP lifecycle/status and elicitation surface to V2.
From #34359, the TUI migration needs V2 coverage for MCP functionality rather than relying on the legacy SDK surface.
Expected scope:
- Port/expose MCP status to V2.
- Port/expose MCP connect to V2.
- Port/expose MCP disconnect to V2.
- Port/expose MCP elicitation to V2.
- Add the required protocol/server/client surface and regenerate
@opencode-ai/clientif needed. - Preserve useful status/error/elicitation details for TUI presentation.
- Add tests around status, connect, disconnect, elicitation, and unavailable/failed MCP servers.
UI polish can follow after the V2 API/port is in place.
This issue is split out from the broader TUI client migration umbrella #34359.
Activity
[-][FEATURE]: Port MCP lifecycle APIs to V2[/-][+][FEATURE]: Port MCP lifecycle and elicitation APIs to V2[/+]opencode-agent commentedon Jun 29, 2026
Expanded scope to include V2 MCP elicitation too; UI polish can follow after the API/port lands.
opencode-agent commentedon Jul 2, 2026
Tracker update from V2 TODO LIST audit (2026-07-02):
Related current work:
Suggested tracker state: narrow this issue to remaining MCP lifecycle/elicitation gaps after separating prompt/command work into the linked issues above. Aiden is currently tracking MCP elicitation and related improvements in the V2 TODO LIST thread.
opencode-agent commentedon Jul 2, 2026
Additional tracker update (2026-07-02):
Related open PR:
This is still the concrete implementation PR for MCP prompts. Command execution remains tracked separately in #34685/#34429; do not treat #34531 alone as end-to-end slash-command prompt support.
opencode-agent commentedon Jul 3, 2026
Update: #35064 (
feat(core): MCP elicitation support) is the active V2 implementation PR for the elicitation portion of this tracker.After it lands, remaining scope here should be narrowed to any MCP lifecycle/status/connect/disconnect gaps that are still not covered by V2 APIs/TUI.
opencode-agent commentedon Jul 3, 2026
Update from Aiden's Discord status:
MCP elicitation is done via #35064 (
feat(core): MCP elicitation support), which is merged.I did not find clear completed coverage for the rest of this tracker's original lifecycle/status/connect/disconnect scope, so this issue should stay open and be narrowed to any remaining V2 MCP lifecycle/status/connect/disconnect gaps.
Source Discord URL: https://discord.com/channels/1391832426048651334/1520962938733723720/1522663895003697433
[-][FEATURE]: Port MCP lifecycle and elicitation APIs to V2[/-][+][FEATURE]: Port MCP lifecycle/status/connect/disconnect APIs to V2[/+]rekram1-node commentedon Jul 3, 2026
Final tracker update:
The intended V2 scope here is complete.
mcp.status.changedare in place.form.created,form.replied,form.cancelled) with MCP metadata for TUI presentation.mcp.browser.open.failedevent from the current MCP event inventory/generated V2 SDK surface and added coverage for MCP error messages.We are intentionally not adding V2 MCP connect/disconnect APIs; lifecycle reconnect/auth behavior remains service-owned rather than exposed as public connect/disconnect endpoints.
Given that clarification, I think this issue can be closed.
rekram1-node commentedon Jul 3, 2026
Closing as complete based on the clarified V2 scope above.