Local MCP server/Productivity

LMCP MCP server

Local MCP server

LMCP runs on your Mac or Windows computer and connects an AI assistant to Mail, Calendar, Contacts, Teams, Slack, WhatsApp on Mac, OneDrive, Google Drive, Notion, Outlook on Windows, and Office files. The provider documents a desktop installer that sets up supported AI clients automatically, with 240+ tools on macOS and a separate Windows catalogue. This is a local install, not a hosted server you add by URL; a Cloud Relay is documented separately for web assistants.

Local app sign-in Local install path Reviewed 2026-11-16
About

Where it fits

People who want an AI assistant to use local mail, calendar, Office files and other desktop apps.

  • Read mail and calendar locally.
  • Access Office files on a computer.
  • Use Slack or Teams from an AI.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Desktop app installer

Download the signed macOS or Windows installer. It installs LMCP locally and auto-configures the AI clients it finds; creating an account is required to download.

https://www.local-mcp.com/download

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
  • The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Safety

Before you connect

Local process, your machine
  • The MCP server process runs on your machine, not on a provider host.
  • Data leaves only through the model provider and any MCP servers you attach.
  • Review the local command, package, and files it can reach before running it.
  • Stop the process or remove the client entry when you no longer need it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

LMCP documentationhttps://www.local-mcp.com/setupGitHub repositoryhttps://github.com/colibird-ai/local-mcp-releases