Cloud AI assistants make you disclose privileged material to a third party. LMCP connects a local AI client to your Mail, Files and Notes 100% on-device — no cloud API keys, and nothing sent to our servers.
100% local · no cloud API keys · 233 tools in one install · macOS 13+
Every mainstream way to use AI on legal work moves that work off your machine — and each hop is an outside disclosure you have to justify.
Cloud AI assistants send whatever you paste — including privileged material — to a third-party provider. Disclosing to an outside vendor can risk waiver and expands the confidentiality surface you have to defend.
Browser extensions & SaaS connectors route your mailbox and matter files through their servers. Another vendor with access to client confidences, another data-processing agreement to review.
Copy-paste into a chat window moves privileged text off your machine by hand — untracked, ungoverned, and hard to defend if opposing counsel asks where it went.
Keep the AI and the documents on the same Mac. There is no third-party cloud in the loop, so there is no outside disclosure to defend.
LMCP is a local MCP server. It reads your Mail, Files, Notes, and Calendar on the machine itself — nothing is uploaded to LMCP.
Point Claude Desktop (or any desktop MCP client / local model) at LMCP. The AI and your documents stay on the same machine — no third-party cloud in the loop.
LMCP has no cloud API keys and stores no documents. On the local path nothing is disclosed to any third party — including us.
LMCP is architecture, not a compliance certificate, and nothing here is legal advice. No connector protects privilege by itself — that depends on your practices and jurisdiction. What LMCP guarantees is that the connector is 100% local and never receives your documents. Pair it with a local AI client and privileged files never leave your Mac. Use a web AI (ChatGPT, Claude.ai) and the material goes to that provider under their terms — LMCP is only the pipe.
No software protects privilege on its own — that depends on your practices, your jurisdiction, and how you handle the material. What LMCP does is keep the connector 100% local: paired with a local AI client, privileged documents never leave your Mac and no third party (including us) receives them, which avoids the outside-disclosure that creates waiver and confidentiality risk in the first place.
Then the material you ask about is sent to that AI provider, and their terms apply — LMCP is only the pipe. For privilege-conscious work, pair LMCP with a local desktop AI client or a local model so nothing leaves the device.
On the local path: nowhere. The MCP server reads files and mail on your Mac and hands them to the AI client running on the same Mac. LMCP’s own servers only ever see license and anonymous telemetry — never your documents or client data.
Yes — the local path is auditable: no outbound connection carries your document content when you use a local AI client. Reach out and we’ll walk your IT/GC through exactly what the connector does and does not send.
Free for individual practitioners. Install in two minutes and pair it with a local AI client — nothing leaves the device.