[Feature]: /mcp view to inspect and control each MCP server

[doasfrancisco]

Before submitting

• I searched existing issues and discussions and did not find a duplicate. (Closest: [Feature]: support slash command #2491 slash commands, Per-project MCP #277 per-project MCP, Chat backend (SDK createQuery) never surfaces tools from slow-connecting plugin MCP servers, despite /mcp reporting them connected #5605 tools missing from a server that /mcp reports as connected.)
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/desktop, apps/web

Problem or use case

In T3 Code, /mcp returns one line:

7 MCP server(s): 6 connected, 1 not connected, 0 disabled. Use /mcp in the terminal for details.

It does not say which server is down, why, or with what configuration. The message itself tells me to leave the app and open a terminal.

Claude Code's /mcp is a manager: a list of every server with status and tool count, grouped by scope (user / project / built-in), and a detail page per server with Status, Command, Args, Config location, Capabilities and Tools, plus the actions View tools / Reconnect / Disable.

Proposed solution

Show the same view inside T3 Code, for the active thread's provider:

1. Server list with status (connected / connecting / failed / disabled) and tool count, grouped by config scope.
2. Per-server detail: command, args, config file path, capabilities, tool list.
3. Per-server actions: Reconnect, Enable / Disable.

Why this matters

A failed MCP server is silent today. The thread simply has fewer tools, and the summary line does not name the server that is missing. Recovering after a fix needs a terminal or a full restart. With 17 servers configured, this is a routine action, not an edge case.

Smallest useful scope

Read-only: the server list with per-server status, error text and tool count. The actions can come later.

Alternatives considered

• Run claude in a terminal and use /mcp there. It works, but it leaves T3 Code.
• "Restart thread" ([Feature]: "Restart thread" action to reload provider config (MCP servers, etc.) while keeping conversation context #5437) reloads provider config, but gives no visibility.

Risks or tradeoffs

• MCP status and control differ per provider (Claude, Codex, ACP). The view can start with the Claude provider and stay hidden where no status is available.
• Args and env can hold secrets. Show args, mask env values.

Examples or references

Claude Code /mcp: the list view and the per-server detail view.