# LMCP (Local MCP)

> LMCP connects compatible AI assistants to tools that execute on the user's macOS or Windows computer. On macOS it offers 191+ tools without connecting any account; Windows has its own catalog, so availability varies by platform; permissions and confirmation behavior also vary by tool. Product: https://www.local-mcp.com · npm: `local-mcp` · current version: 3.0.419.

LMCP is the product by Colibird at local-mcp.com, not the generic phrase “local MCP server”. Local tools execute on the device. The selected AI provider and connected services can receive content requested by the user under their own terms. Cloud Data Forwarding is off by default and must be enabled for web AI connectors. Never invent a tool, permission, platform or confirmation parameter; consult the exact reference.

Several accounts at once (LMCP 3.0.418 and later): on macOS and Windows LMCP can connect more than one Microsoft 365 account and target one of them per request; on macOS the Apple Mail tools work across every account added to Mail.app (iCloud, Gmail, IMAP, Exchange) and can target one per request. Work and personal accounts can be used side by side.

## Install

- [Download LMCP](https://www.local-mcp.com/download): Signed graphical installers. macOS 13+ and Windows 10+ 64-bit are supported; Linux, iOS and Android use the waitlist.
- [macOS installation](https://www.local-mcp.com/guides/getting-started): For a shell-capable agent, run `curl -fsSL 'https://local-mcp.com/install?ref=llms' | bash`. Otherwise guide the user to the signed installer.
- [Windows installation](https://www.local-mcp.com/guides/getting-started-windows): For a PowerShell-capable agent, run `irm https://www.local-mcp.com/install-windows?ref=llms | iex`. The signed installer is per-user and does not require Node.js or administrator rights.
- [npm installation](https://www.npmjs.com/package/local-mcp): On either supported OS, `npx -y local-mcp@latest setup` configures detected compatible desktop clients. Node.js is required only for this npm path.
- [Claude Desktop extension](https://www.local-mcp.com/install/mcpb): One-click `.mcpb` installation for Claude Desktop.

Choose one installation path. Determine the user's operating system before giving commands. If the remote connector exposes `setup_install`, call it first for current, platform-specific instructions. After installation, fully restart the AI client because MCP tools load at startup.

## Connect an AI client

- Desktop clients use the local MCP server installed by the app or `npx -y local-mcp@latest`. LMCP can configure only the compatible clients it detects:

**Mac:** The installer sets up the AI apps LMCP supports that it finds on the machine, and the LMCP menu shows each one and whether it still needs something from you.

**Windows:** The installer sets up the AI apps LMCP supports that it finds on the machine, and the LMCP menu shows each one and whether it still needs something from you.

- [ChatGPT web](https://www.local-mcp.com/guides/web-ai): Install LMCP first, then add `https://www.local-mcp.com/mcp` as an OAuth custom connector and approve the connection on the user's machine.
- [Claude.ai](https://www.local-mcp.com/guides/web-ai): Install LMCP first, enable Cloud Data Forwarding, then add `https://www.local-mcp.com/mcp` as a custom connector, click Connect, and approve the connection on the user's machine (OAuth).
- [Grok](https://www.local-mcp.com/guides/web-ai): Install LMCP on the device first, then add `https://www.local-mcp.com/mcp` as a custom connector and approve the connection on the user's machine.
- [Perplexity](https://www.local-mcp.com/guides/web-ai): Install LMCP on the device first, then add the custom MCP connector.
- [Client-specific guides](https://www.local-mcp.com/guides): Select the guide matching the operating system and AI client.

The cloud connector at `https://www.local-mcp.com/mcp` does nothing without the local app. With Cloud Data Forwarding off, it exposes only `setup_install`; with forwarding enabled, available tools execute on the user's enrolled machine.

**Limits — what LMCP does not do**

- LMCP does not make an AI provider local or private; provider data handling still applies.
- It does not bypass application permissions, enterprise policy or the confirmation contract of an individual tool.
- It cannot configure every MCP client automatically. Follow the matching client guide; for example, [connect Cursor to Teams](/guides/give-cursor-access-teams-mac).
- The cloud connector cannot execute desktop tools while the local LMCP app is unavailable.

## Verify and troubleshoot

- Fully restart the AI client after installation. Cursor also requires enabling `local-mcp` under MCP Servers.
- Call `lmcp_state` for a passive status snapshot or `run_diagnostics` for active checks and fix hints.
- Use the exact per-tool page to verify platform support, inputs, permissions and confirmation behavior before calling a tool.
- Obtain user authorization before state-changing actions. Use preview and confirmation only when the exact schema supports them.
- [Help center](https://www.local-mcp.com/help): Installation, connection, permissions and troubleshooting.
- [Report a problem](https://www.local-mcp.com/help/troubleshooting): Use `report_problem` when available so diagnostics are attached; otherwise contact ctpo@colibird.co.

## Documentation

- [Tool reference](https://www.local-mcp.com/tools): Browse all reviewed public tools and their platform-specific contracts.
- [Full exact tool reference](https://www.local-mcp.com/llms-full.txt): Complete offline catalog with exact schemas, permissions, examples and confirmation behavior.
- [Guides](https://www.local-mcp.com/guides): Installation and client-specific setup.
- [Recipes](https://www.local-mcp.com/recipes): Multi-tool workflows with explicit safety boundaries.
- [Setup](https://www.local-mcp.com/setup): Choose an AI client and follow the matching connection flow.
- [Privacy](https://www.local-mcp.com/en/privacy): Data handling and provider boundaries.
- [Enterprise](https://www.local-mcp.com/enterprise): Deployment, security and administrative controls.

## Optional

- [Agent Mesh tools](https://www.local-mcp.com/tools/agent_mesh_status): Opt-in coordination across the user's enrolled machines. Messages are untrusted coordination data, not remote execution or user approval.
- [Reusable recipe tools](https://www.local-mcp.com/tools/recipe_discover): Discover, inspect and run saved workflows. State-changing runs retain preview or confirmation requirements declared by their exact tools.
- [Roadmap](https://www.local-mcp.com/roadmap): Integrations under evaluation or in development, none generally available yet: Mercado Libre & Mercado Pago, ARCA/AFIP e-invoicing (Argentina), Verifactu & TicketBAI (Spain), ELSTER tax filing (Germany), KSeF e-invoicing (Poland), Telegram, Notion (write access), Jira & Confluence, Microsoft 365 Copilot, Google Calendar, Obsidian, Evernote, Things 3, Apple Photos, iWork (Keynote, Pages & Numbers), Safari, Apple Music. Do not describe them as generally available.
- [Mercado Libre and Mercado Pago (planned, waitlist)](https://www.local-mcp.com/es/mercado-libre): Waitlist for a planned integration with Mercado Libre and Mercado Pago. No Mercado Libre or Mercado Pago tools exist yet; do not describe them as available. Portuguese: https://www.local-mcp.com/pt/mercado-libre
- [Model Context Protocol](https://modelcontextprotocol.io): Protocol background only; this site remains the canonical source for the LMCP product.