[FEATURE] Multiple authenticated accounts per MCP server, and show which account each MCP is authenticated as

Problem Statement

When an MCP server uses OAuth (remote MCP servers and claude.ai connectors used from Claude Code), Claude Code holds exactly one authenticated account per MCP server, and gives no indication of which account that is.

This causes two problems:

1. No multiple accounts per MCP server. Many of us have several accounts on the same service (e.g. a work and a personal Google account, several Slack workspaces, a team account and a personal account on a SaaS tool). Today the only way to switch is to log out of the MCP server and re-authenticate with another account, which is slow and means you can never use both in the same session.
2. No visibility on the authenticated identity. /mcp shows that a server is "connected" / "authenticated", but not as whom. It's easy to run tools (including write actions) against the wrong account without realizing it.

Proposed Solution

1. Multiple authenticated accounts per MCP server

• Allow authenticating the same MCP server several times, each stored as a separate credential/connection.
• Each connection gets a label, either:
• a user-defined name (e.g. gmail (work), gmail (perso)), set at auth time or renamed later, or
• by default, the account identity returned by the provider (email / username, e.g. from the OIDC id_token, userinfo endpoint, or a server-provided identity).
• Expose them either as distinct tool namespaces (e.g. mcp__gmail_work__* / mcp__gmail_perso__*), or as one server with a selectable active account (per session / per project, switchable from /mcp).

2. Show the authenticated account

• In /mcp (list and detail views), display the account each MCP server is authenticated as, e.g.:

``
gmail · ✔ connected · christopher@work.com
gmail · ✔ connected · christopher@gmail.com
``

• Also show it in claude mcp list / claude mcp get <name>, and ideally in the tool-call permission prompt for write actions, so users know which account a tool call will act on.

Alternative Solutions

• Re-adding the same server under several names in config works only partially: OAuth tokens/connectors are not always scoped per configured name, and nothing shows which identity each one is logged in as.
• Logging out / back in each time: works but is cumbersome and error-prone.

Related

• #27302 — multiple connector accounts on claude.ai / Claude Code on the web (GitHub-focused)
• #36024 — multiple Gmail accounts in MCP
• #44243 — multiple Slack workspaces in the Slack connector

This request is the general, server-agnostic version for Claude Code (CLI + connectors), plus the "show which account I'm authenticated as" part, which none of the above cover.