[FEATURE] Claude.ai should use Remote Control's MCP tunnel

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

small business with a local ChromaDB knowledge base containing 33,000+ chunks of business data, exposed via a local MCP server. Claude Code accesses it perfectly through Remote Control from my phone — full KB access, full file system, everything works.
But when I switch to a Claude.ai conversation in the same app on the same device, I lose all access to that same MCP server. Claude.ai has no way to reach my local tools, even though Remote Control is actively tunneling to my workstation through Anthropic's infrastructure at that exact moment.
This means my strategic planning conversations in Claude.ai are completely disconnected from my business data, while my Claude Code session ten seconds away has full access. I'm forced to either do all work in Claude Code (which is optimized for doing, not discussing), or manually copy context between the two surfaces.
The only current workaround is exposing my local MCP server to the internet as a remote endpoint — which adds unnecessary security surface for a small business operating under NIST 800-171 compliance requirements. The secure tunnel already exists. My Claude.ai conversations just can't use it.

Proposed Solution

When Remote Control is active, any Claude.ai conversation in the same app (web, mobile, or desktop) should be able to opt into accessing the local MCP servers available through that tunnel.
Ideally: I open a Claude.ai chat, see my local MCP servers listed alongside my existing remote connectors (Gmail, Google Calendar, etc.) in the tools menu, and toggle them on. Claude.ai can then call my local KB the same way Claude Code already does — search, retrieve, write — all routed through the existing Remote Control connection. No new endpoints to expose, no additional auth to configure.
When Remote Control disconnects, those local MCP tools simply become unavailable in Claude.ai, the same way any disconnected connector behaves today.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

MCP server integration

Use Case Example

_No response_

Additional Context

---

1. I'm at home on a Friday night with my phone. My workstation is running at the office with Remote Control active.

1. I open Claude Code on my phone via Remote Control. I ask it to pull my current task state from my local ChromaDB knowledge base. Works perfectly — full MCP access through the tunnel.

1. I want to think through a strategic question — like how to restructure sales territories based on 26 years of sales history in my KB. This is a planning conversation, not a coding task. Claude.ai is the right surface for it.

1. I switch to a Claude.ai conversation in the same app. Now I'm blind. Claude.ai can't access my KB, can't look up sales data, can't search customer records, can't read my architectural decisions. The tunnel to my workstation is live — Claude Code is still using it — but Claude.ai can't touch it.

1. My only options are: manually copy-paste context from Claude Code into Claude.ai (slow, lossy), do all my strategic thinking inside Claude Code (wrong tool for the job), or expose my MCP server to the internet as a remote endpoint (unnecessary security risk).

1. With this feature, I'd stay in Claude.ai, my local MCP tools would show up in the tools menu because Remote Control is active, and I'd have a strategic planning conversation with full access to my business data. No workarounds, no security exposure.