How to Connect Claude.ai Web to Your Mac
In short: Give Claude.ai (web) direct access to your Mac apps — Mail, Calendar, Contacts, Teams, OneDrive, and 201+ tools.
To use Claude.ai on the web with the apps on your Mac — Mail, Calendar, Microsoft Teams, OneDrive and more — install LMCP and connect it through its Cloud Relay. Claude.ai’s chat runs in Anthropic’s cloud, but your inbox, your calendar and your Teams chats live on your Mac; the Cloud Relay is the encrypted tunnel that lets one reach the other. You add LMCP as a custom connector in Claude.ai’s settings, approve it once from a dialog that opens on your Mac, and from then on every tool call routes through the tunnel, runs locally on your machine, and returns a result — typically in under two seconds. No desktop app to install on the Claude.ai side, no separate client: any browser, on any device signed into your account, reaches the same Mac.
What This Lets You Do
Claude.ai web runs in the cloud, but your email, calendar, and Teams chats live on your Mac. With LMCP plus the Cloud Relay, Claude.ai can call tools that run directly on your Mac — over an encrypted WebSocket tunnel — and the data is forwarded to Claude.ai through the relay when requested.
From Claude.ai web you can ask:
- “Summarize my unread emails from this week”
- “What’s on my calendar today?”
- “Search emails about the Q3 budget”
- “Summarize the engineering Teams channel from yesterday”
Claude.ai sends the request to LMCP’s backend, the backend forwards it through the encrypted tunnel to your Mac, your Mac executes the tool locally (Mail.app, Calendar via EventKit, Teams through your connected Microsoft 365 account), and the result returns to Claude.ai — usually in under 2 seconds.
Why Claude.ai Web Instead of Claude Desktop?
Claude Desktop already talks to LMCP: install both, and the desktop app discovers the local lmcp connector over stdio automatically, no relay involved. So why bother adding the same tools to the web version too?
Because the connector lives on your Claude.ai account, not inside an installed app. Add LMCP once in Settings → Customize → Connectors and it is reachable from any browser tab you sign into — a work laptop that will not let you install software, a borrowed computer, a Chromebook — as long as your own Mac stays powered on and LMCP keeps running back home. Claude Desktop, by contrast, only works on the one Mac it is installed on, and only while you’re sitting in front of it.
The trade-off is a network hop. Claude Desktop’s local lmcp connector talks to your Mac over stdio — a pipe between two processes on the same machine — so there is no tunnel and no relay backend. Claude.ai web adds one hop: your request goes to Anthropic, then through the Cloud Relay to your Mac, then back. In practice the difference is invisible — tool calls still land in a second or two — but it’s why Claude Desktop stays the right default when you’re already at your Mac, and Claude.ai web is what you reach for everywhere else.
How the Cloud Relay Works
The Cloud Relay is the piece that makes any of this possible from a browser tab that has no idea your Mac exists. When LMCP starts, it opens a persistent, encrypted connection outbound from your Mac to LMCP’s cloud backend — initiated from your side of the network, the same way your Mac already reaches iMessage or iCloud, so there is nothing to open on your router or firewall.
Claude.ai does not talk to your Mac directly — it can’t, since your Mac has no public address. Instead, Claude.ai’s custom connector points at LMCP’s backend, authorized by the approval you gave on your Mac when you connected it. When Claude calls a tool, the backend looks up which open tunnel belongs to that authorization, forwards the request down it, and your Mac’s LMCP process executes it against the real app — Mail.app for email, EventKit for Calendar, your connected Microsoft 365 account (via Microsoft Graph) for Teams. The result travels back up the same tunnel and out to Claude.ai.
The backend’s job is routing, not processing — it never opens Mail.app itself and never holds an OAuth token for your Microsoft account. All of that lives in the LMCP binary on your Mac, exactly as for Claude Desktop’s local connector. The only difference is that a request arrives over the tunnel instead of stdio.
Privacy: What Travels and What Doesn’t
Cloud Data Forwarding is on after installation, and you can turn it off from the menu bar at any time; Claude.ai only uses it after you connect the connector and approve the connection on your Mac. When off, the connector's tools/list advertises only setup_install (onboarding) — data tools are not listed until you enable forwarding.
LMCP executes local tools on your device. Cloud AI providers and connected services can receive requested data; their terms apply.
In concrete terms: an email’s subject, body and attachments only exist on your Mac and inside Claude’s context window for that conversation. The relay backend sees the encrypted bytes in flight, the way any router sees encrypted packets, but by design does not log, cache or persist the payload once it’s forwarded. What the backend does retain is connection metadata needed to route — which Mac a connector maps to, whether the tunnel is currently open — never the content of a tool call.
LMCP executes local tools on your device. Cloud AI providers and connected services can receive requested data; their terms apply. Local execution alone does not establish GDPR or CCPA compliance. Assess the data you authorize, the selected AI provider, connected services and your organizational requirements.
How Is This Different From Uploading Files to the Chat?
You could always attach a .csv export of your calendar or paste an email thread into Claude.ai — that still works. The connector changes three things.
First, it’s live instead of a snapshot: a file you uploaded five minutes ago is already stale if a new email arrives, while a tool call reads Mail.app at the moment you ask, every time. Second, it’s queryable instead of exhaustive — the AI can search for the one thread it needs instead of you exporting and re-uploading every time the question changes. Third, and most important, it can act: create_calendar_event, reply_email and move_email actually change something in your real apps, with a preview before anything sends or moves. A pasted file is read-only by definition — there’s nothing for the AI to write back to.
The cost is the one-time setup of the connector: a couple of minutes now, instead of an export step you’d otherwise repeat every time you wanted a current answer.
What You Will Need
- macOS 13 (Ventura) or later — Apple Silicon or Intel
- A Claude.ai account — Pro recommended for custom connectors
How to Connect Claude.ai to Your Mac
Connect Claude.ai to your Mac
claude.ai → Settings → Customize → Connectors- 1
Install LMCP on your Mac
Download LMCP from local-mcp.com and run the installer — it installs Local MCP to Applications and auto-configures your AI clients in ~30 seconds.
- 2
Turn on web access and copy your Connection URL
Click the LMCP icon in your menu bar and find Your web AI · Cloud Relay. Make sure web access is ON (it is on after installation unless you turned it off), then open your assistant’s panel and click Copy URL.
The URL is — it carries no token and is the same for everyone; every step below that says “the URL you copied” means this one. Access is granted by approving the connection on your Mac, not by the URL. - 3
Open Claude’s connector settings
Open Settings → Customize → Connectors (connectors moved here from the old Settings page), or go straight to claude.ai/settings/connectors. On Team/Enterprise an owner has to add it first from Organization settings → Connectors.
- 4
Add a custom connector
Click Add → Add custom connector. Set Name: and Remote MCP server URL: paste the URL you copied (). Click Add.
- 5
Connect it — this is the step people miss
Add only registers the connector. It now reads “You’re not connected to LMCP yet” — click Connect, then Approve in the dialog that opens on your Mac. Claude only loads the tools after this.
- 6
Enable it in a chat
Start a new conversation, enable the LMCP connector, and ask: “List my email accounts” or “What’s on my calendar today?” With Cloud Data Forwarding ON you’ll see 201+ tools.
Steps verified 2026-08-08. Local tools run on your device; selected AI providers and connectors receive requested content. Review each tool’s permissions and approval behavior.
The connector URL is always https://www.local-mcp.com/mcp — exactly what Copy URL copies, with nothing after it. What ties the connector to your Mac is the approval: Add only registers LMCP, then Connect opens the LMCP sign-in and you approve in the dialog that opens on your Mac. If no dialog shows up, or it says LMCP isn’t running, the approval simply expired — it lasts 5 minutes — so click Connect again; nothing needs reinstalling.
Try It in a Chat
Open a new conversation in Claude.ai, make sure the LMCP connector is enabled (the connector toggle in the input bar), and ask in plain language:
- “List my email accounts”
- “What meetings do I have today?”
- “Show me the latest messages in the engineering Teams channel”
- “Find the OneDrive file about the Q3 budget and summarize it”
- “Create a reminder to follow up with Sarah tomorrow morning”
Claude routes the request through the Cloud Relay to your Mac, which executes the tool and returns the result. You’ll see a “Used LMCP integration” indicator above the response, and the answer usually arrives in under 2 seconds.
What Tools Are Available?
With Cloud Data Forwarding on, Claude.ai sees the same 201+ tools as the local lmcp connector:
- Mail (Mail.app + Outlook): list, read, search, send, reply, move, save attachments
- Calendar: list events, create, delete, check availability
- Contacts: search, list, get details
- Microsoft Teams: list chats, read messages, channel messages (through your connected Microsoft 365 account)
- OneDrive: list, read, write, move, delete, search files
- Notes & Reminders: list, search, create, complete
- Messages: read iMessage chats
- OmniFocus: list tasks, projects, complete, search
- Word, Excel, PowerPoint, PDF: read and create
- Finder: search files (Spotlight), list folders
Claude.ai Web vs Claude Desktop vs Claude.ai Without a Connector
All three run on the same LMCP install. The difference is where you’re sitting, and whether your Mac has to be part of the picture at all. Here is the honest comparison:
| Option | Works from | Path to your Mac | Best for |
|---|---|---|---|
| Claude.ai web + LMCP | Any browser, any device signed into your account | Encrypted Cloud Relay tunnel — your Mac must be on and LMCP running | Access away from your desk: a work laptop, a borrowed computer, your phone’s browser |
| Claude Desktop + LMCP | Only the Mac LMCP is installed on | Local stdio — no network hop, no relay involved | LMCP executes local tools on your device. Cloud AI providers and connected services can receive requested data; their terms apply. |
| Claude.ai, no connector | Any browser | None — no access to your apps or files | General questions that don’t depend on your data |
LMCP executes local tools on your device. Cloud AI providers and connected services can receive requested data; their terms apply.
Turning It Off
Open the LMCP menu bar popover → Web AIs section, toggle Cloud Data Forwarding back to OFF. The change is instant: Claude.ai immediately loses access to data tools (it’ll see the “cloud data forwarding is off” message). Your tunnel stays connected for onboarding (setup_install), but no data flows through.
Troubleshooting
Claude.ai shows only setup_install (1 tool)
Two causes: (1) Cloud Data Forwarding is OFF — toggle it ON in the Web AIs section. (2) The connector was added but never connected — Add only registers it; click Connect and approve in the dialog on your Mac. After either fix, open the LMCP connector in Claude.ai and use ⋮ → Refresh tools list (or remove and re-add).
Claude.ai says LMCP is not authenticated
Connect it again: find LMCP in Settings → Customize → Connectors, click Connect and approve once more in the dialog on your Mac. There’s no need to re-add the connector with a different URL — the URL never changes.
Connector connects but tools fail
Make sure LMCP is running (menu bar dot is green) and Cloud Data Forwarding is ON, then open the LMCP connector in Claude.ai and use ⋮ → Refresh tools list.
Claude.ai says it can’t reach your Mac
Every tool call travels all the way to your Mac and back — there is no cached copy in between. LMCP has to be running and your Mac has to be awake. Open the LMCP menu bar: the dot should be green and Cloud Relay should read Connected. A Mac that’s asleep, shut down, or has LMCP quit leaves Claude.ai with nothing to call.
Clicked Connect but nothing happened on my Mac
The approval dialog opens on your Mac, not in the browser — check for it behind another window, or in the LMCP menu bar for a pending request. If you genuinely don’t see one, or it says LMCP isn’t running, the approval expired — it lasts 5 minutes — so click Connect again in Claude.ai; nothing needs reinstalling.
Real-World Workflows
The connector is most useful exactly when you’re not at your own Mac:
Triage from your phone’s browser
Summarize my unread emails from today, flag anything urgent, and tell me what's on my calendar for the rest of the day.
Your Mac stays on your desk; Claude.ai reaches it through the tunnel exactly as it would from a laptop — nothing to install on the phone, just the browser.
Catch up on Teams before a meeting
Summarize what I missed in the engineering Teams channel since yesterday, and check my calendar for any conflicts this afternoon.
Two apps, one prompt: Claude reads the Teams channel and Calendar in the same turn.
A weekly digest from a machine that isn’t yours
Go through this week's emails and Teams messages, group them by project, and give me a short digest of decisions made and what's still open.
Sign into Claude.ai on a work laptop or a shared computer, and the connector you set up once is already there.
What Else Can LMCP Do?
Email and Teams are two of 201+ tools LMCP exposes. See Apple Mail with Claude Desktop, Microsoft Teams without API keys, or the ChatGPT Cloud Relay guide. The full list of guides covers every app the same install reaches.
Frequently Asked Questions
Can Claude.ai on the web access my Mac apps?
Yes. With LMCP's custom connector, approved once on your Mac, Claude.ai web can read your email, manage your calendar and search Teams — requests route to your Mac and run locally.
Do I need API keys?
LMCP needs no API keys. Adding a custom connector on Claude.ai's side requires a Pro, Max, Team or Enterprise Claude.ai plan — that's an Anthropic requirement, not an LMCP one.
How is this different from Claude Desktop?
Claude Desktop connects to LMCP locally over stdio; Claude.ai on the web reaches your Mac through the encrypted Cloud Relay tunnel. Same tools, either way — see the full comparison above if you’re deciding which one to set up first.
Does my Mac need to be on and LMCP running?
LMCP executes local tools on your device. Cloud AI providers and connected services can receive requested data; their terms apply.
Can I use Claude Desktop and Claude.ai web at the same time?
Yes, they don’t conflict. Claude Desktop talks to LMCP over local stdio, Claude.ai web talks to it through the Cloud Relay — two independent connectors to the same tools, and turning one off doesn’t affect the other.
Is the connector URL a secret?
No. https://www.local-mcp.com/mcp is the same for everyone and carries no token. What connects Claude.ai to your Mac is the approval you give in the dialog that opens on your Mac when you click Connect.
Related Guides
Comments
Questions and experiences welcome — comments are reviewed before they appear.