Log inSubmit server
Local MCP logo

Local MCP

by lanchuske

Connects AI assistants to email, calendars, files, messages, and other Mac or Windows apps through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Local MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "lanchuske-local-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "local-mcp@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

lanchuske/local-mcp connects compatible AI assistants to native apps and online services through MCP, with tools for searching information and taking authorized actions. The local application runs tools on the user's computer and can work with email, calendars, contacts, messages, files, documents, browsers, and task systems. Reach for it when an assistant needs context assembled across multiple apps rather than a single service. Local clients use the installed app, while supported web assistants connect through an MCP endpoint with OAuth and optional Cloud Data Forwarding.

Use cases

  • Search email, messages, and files for related commitments
  • Combine calendar events and tasks to plan a workday
  • Draft customer replies using accessible order information
  • Create notes and reminders from an assistant conversation
  • Update supported records after reviewing proposed actions

Key features

  • MCP access to desktop apps and connected accounts
  • Email, calendar, contact, message, and task tools
  • File storage and Office document integrations
  • Local execution on macOS or Windows
  • Optional web-assistant connection through OAuth
  • Cursor plugin and npm-based client setup

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

15/15 checks healthy over the last 87d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · local-mcp@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars79Stargazers on the source repository.
npm downloads15kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Directory activity12 viewsConfig copies, upvotes, and views on AllMCPs.

How Local MCP works

What lanchuske/local-mcp does

lanchuske/local-mcp gives compatible AI clients MCP access to information and actions across desktop applications, connected accounts, and local or synchronized files. Its integrations cover areas such as email, calendars, contacts, messages, reminders, notes, tasks, file storage, browser automation, and Office documents. Examples named by the project include Apple Mail, Outlook, Microsoft Teams, Slack, WhatsApp, Signal, Google Drive, OneDrive, Microsoft 365, OmniFocus, Notion, and ServiceNow.

The main use case is cross-application context. An assistant can search related messages, email, calendar entries, and files, then use available tools to draft content, organize information, or make supported updates after authorization. The exact tools and integrations depend on the operating system, connected accounts, permissions, and client.

How it works

The installed LMCP application runs the MCP tools on the user's computer. A compatible assistant sends requests through MCP; LMCP selects the available application or account integration and returns context or performs an authorized action. Some integrations read native data, local caches, or synchronized files. Others require a network connection and sign-in.

Desktop and command-line clients generally launch the server through the local-mcp npm wrapper or an installed integration. Web assistants use https://www.local-mcp.com/mcp as a custom connector with OAuth. That route requires the local application and Cloud Data Forwarding; forwarding is disabled by default, and without it the connector exposes only setup_install.

Setup and configuration

Install LMCP for macOS or Windows first, then select the assistant and integrations to use. The supported platforms are macOS 13 or later and 64-bit Windows 10 or later. Required operating-system permissions and service sign-ins must be granted during setup.

For a Node.js-based setup, run:

Terminal
npx -y local-mcp@latest setup

The setup command configures compatible clients it detects. A client can also be configured directly with the npx -y local-mcp@latest command and its corresponding MCP settings format. Cursor offers both the setup command and a repository plugin. A Claude Desktop .mcpb extension, signed installers, and platform-specific installation commands are also available.

Restart the AI client after installation because MCP tools load at startup. For web assistants, complete connector authorization and verify that tools are available; an endpoint by itself does not confirm a working connection.

Tools and capabilities

Available capabilities include:

  • Search and work with email, messages, contacts, calendars, reminders, notes, and tasks.
  • Access files and connected storage such as OneDrive and Google Drive.
  • Work with Office documents and Microsoft 365 services.
  • Use browser automation and supported productivity applications.
  • Combine information from multiple apps to support planning, drafting, and follow-up actions.
  • Apply app-specific permissions and account access rather than granting universal access automatically.

The project directs users to its live tool reference and setup guides for current tool names, requirements, and platform coverage.

Limitations and notes

Integration availability differs between macOS and Windows. Apple-native tools require macOS, while connected services may need their own authentication and permissions. Some integrations operate on cached or synchronized data rather than a complete cloud account.

Assistant behavior and tool permissions still determine what can be read or changed. Demonstrated workflows are examples of possible tool combinations, not guarantees of autonomous results. The core binary is proprietary, while the repository documentation and scripts have a separate license.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Local MCP

lanchuske/local-mcp is an MCP server that connects AI assistants to desktop apps and connected accounts on macOS and Windows. Its tools work with email, calendars, messages, files, documents, contacts, tasks, browser automation, and supported productivity services, allowing assistants to gather context and perform authorized actions.

Install the LMCP application for macOS or Windows first, then run `npx -y local-mcp@latest setup` for a Node.js-based configuration. The setup command configures compatible clients it detects. Restart the client afterward so its MCP tools load.

Yes, lanchuske/local-mcp works with Cursor through `npx -y local-mcp@latest setup` or the repository's Cursor plugin. Install LMCP before adding the plugin, because the plugin starts the local server but does not replace the required desktop installation.

Yes, supported web assistants can connect through `https://www.local-mcp.com/mcp` as a custom connector with OAuth. The local app must be installed and Cloud Data Forwarding enabled; with forwarding disabled, the connector exposes only `setup_install`.

lanchuske/local-mcp supports macOS 13 or later and 64-bit Windows 10 or later. Available integrations vary by platform, and Apple-native tools require macOS.

Related MCP servers

All in Communication All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLocal MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/lanchuske-local-mcp?style=directory)](https://allmcps.com/mcp/lanchuske-local-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/lanchuske-local-mcp"><img src="https://allmcps.com/api/badge/lanchuske-local-mcp?style=directory" alt="Local MCP on AllMCPs" /></a>