openclaw - 💡(How to fix) Fix [Feature]: Add MCP service connectivity status panel in Control UI [1 participants]

Problem

MCP services are configured in openclaw.json under mcp.servers, but after configuration, there is no way to verify whether an MCP service is actually connected and functioning correctly — without checking logs manually.

When an MCP service is misconfigured (wrong token, wrong URL, server down, etc.), the agent silently fails to use it. Debugging requires digging into gateway logs, which is time-consuming and not user-friendly.

Proposed Solution

Add a dedicated "MCP Connectivity" section in the Control UI that:

1. Shows connection status per MCP server — green/red indicator for each configured server (connected / disconnected / error)
2. Lists available tools per server — after a successful connection, display the tool count and names exposed by that MCP server
3. One-click reconnect / refresh — allow users to manually re-trigger the connection handshake for a specific server
4. Shows error details — when a server fails to connect, surface the specific error (auth failure, timeout, 404, etc.) in the UI instead of hiding it in logs

Use Cases

• Pre-flight check: Before a session starts, verify all MCP tools are available as expected
• Faster debugging: Immediately know which MCP server is misconfigured without reading logs
• User confidence: Users can confirm their MCP setup is working end-to-end

Alternatives Considered

• Reading gateway logs — requires CLI access and log grepping, not accessible to non-technical users
• Relying on the agent to report — by the time the agent fails, it's too late; a proactive status panel would catch issues earlier

Additional Context

Example MCP servers this would help debug:

• mcd-mcp (streamable-http) — token validity, endpoint reachability
• amap-maps (HTTP) — API key validity, daily quota status
• minimax (stdio) — process startup, env var issues
• taobao-native (localhost HTTP) — local server availability