[FEATURE] MCP wrapper and MCP server

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When using Claude Code with an MCP wrapper (e.g., a wrapper for TestRail API),
both the wrapper and the actual server are displayed identically as "(MCP)".

This makes it impossible to visually distinguish which MCP component is active,
raising concerns about auditability and security transparency in team environments.

Expected: Visual distinction between MCP wrapper and MCP server
(e.g., "(MCP wrapper)" vs "(MCP server)" or showing the registered name)

Actual: Both shown as "(MCP)"

Proposed Solution

Display the registered name alongside "(MCP)" label, or distinguish
between MCP wrapper and MCP server in the UI.
Example: "(MCP: testrail-wrapper)" vs "(MCP: testrail-server)"

Alternative Solutions

Show the configured server name instead of generic "(MCP)" label.

Priority

Medium - Would be very helpful

Feature Category

MCP server integration

Use Case Example

A team uses an MCP wrapper to connect Claude Code to the TestRail API
securely (instead of raw bash calls). Both the wrapper and the actual
API endpoint appear as "(MCP)" in Claude Code's UI. During a security
review, a team member could not determine which MCP component was active,
raising concerns about connection transparency and auditability.

Additional Context

In team environments, security reviews require clear identification of
which MCP components are connected. The current uniform "(MCP)" label
makes audit trails difficult to interpret.