AI on patient data.
Local-first on Mac and Windows.
LMCP connects your chosen AI assistant to supported apps and files on Mac and Windows. Local tools process supported data on-device. Optional cloud AI clients and connectors receive necessary content under their own terms.
Local-first · permission-aware · 188+ tools · macOS 13+ and Windows 10+
Why AI + PHI is a compliance headache
Cloud-connected workflows can send clinical or administrative data to external providers. Review every provider, permission and agreement involved in your chosen workflow.
Cloud AI assistants send whatever you paste — including PHI — to a third-party provider, which usually requires a signed BAA and expands your breach-exposure surface.
Browser extensions & SaaS connectors route your mailbox and files through their servers. Another vendor, another BAA, another audit.
Copy-paste workflows move PHI into a chat window by hand — untracked, ungoverned, and easy to get wrong.
The local-first path
Local tools run on your Mac or Windows PC. To keep inference on-device too, choose a model that runs locally and review each connector for any external data transfer.
Runs on your computer
LMCP is a local MCP server for Mac and Windows. It works with supported apps and files on the device; cloud integrations are explicit and permissioned.
Choose your AI client
Connect a desktop client or use the optional relay for web assistants. A desktop app may still use cloud models; choose a model running on-device when your workflow requires local inference.
Review each permission
Local tools process supported data on-device. Optional cloud AI clients and connectors receive the content needed for authorized requests under their own terms and agreements.
A straight answer on compliance
LMCP is architecture, not a compliance certificate. No connector can make you HIPAA compliant by itself — that depends on your whole environment, policies, and agreements. Local tools process supported data on-device. Optional cloud AI clients and connectors receive necessary content under their own terms and agreements. A desktop client can use a cloud model, so review the complete data flow before handling protected health information (PHI).
Questions from compliance teams
Does LMCP make my workflow HIPAA compliant?
No tool can make a workflow HIPAA compliant on its own — compliance depends on the full environment, policies, agreements, AI client and integrations. LMCP keeps local tools on your Mac or Windows PC and makes cloud-connected paths explicit.
What if I use a web AI (ChatGPT, Claude.ai) instead of a desktop client?
The content needed to answer is sent to that AI provider under its terms and agreements. Desktop clients can also use cloud models. Review the actual model, connectors and data flow before using sensitive information.
Do you sign a BAA?
Your organization should assess which providers handle protected health information and which agreements the complete workflow requires. Contact us about your deployment; do not treat installing LMCP as a substitute for that assessment.
Where does the data actually go?
On the local path, the MCP server works with data on your Mac or Windows PC and hands it to the AI client you selected. A web AI or cloud integration receives only the data required for the request under that provider’s terms.
Keep PHI where it belongs.
Install on Mac or Windows, choose your AI client and review every integration before using it with sensitive information.