Does updating restart Local MCP?

Yes. When update_local_mcp installs a new version, it downloads the update and restarts LMCP automatically so the new build takes effect. Wait a few seconds for it to reconnect before sending your next command.

Will an update affect my permissions or data?

No. The update only swaps the signed app binary. Your Mac data stays local, and your previously granted permissions persist because LMCP is code-signed with a stable Developer ID.

Can web AIs like ChatGPT trigger the update?

Yes. ChatGPT, Claude.ai, Grok and Perplexity reach update_local_mcp through the LMCP Cloud Relay connector, while Claude Desktop, Cursor, VS Code, Windsurf and Zed call it over a local stdio connection.

Update Local MCP on Mac: Let AI Install LMCP Updates

The update_local_mcp tool lets your AI assistant keep Local MCP (LMCP) current on your Mac without you touching the menu bar or a download page. When you call it, the AI checks whether a newer LMCP version is available, and if you confirm, it downloads the update and restarts LMCP so the new version takes effect immediately. A natural prompt looks like:

"Check if there's a Local MCP update and install it."

That single sentence triggers the version check, surfaces what's new, and applies the update in place. No DMG, no drag-to-Applications, no manual relaunch. Because installing restarts LMCP, give it a few seconds to come back online before issuing your next command.

LMCP is a free, native macOS MCP server with 150+ tools. It lets AI assistants use your real Mac apps — Mail, Calendar, Contacts, Messages, Notes, Reminders, Safari and more — entirely on your machine. No API keys, no cloud account, nothing stored on a server. Keeping it updated means you get the latest tools and reliability fixes the moment they ship.

Which AI agents work?

LMCP works with every major MCP-capable assistant. Desktop clients auto-configure over a local stdio connection:

Claude Desktop
Cursor
VS Code (GitHub Copilot)
Windsurf
Zed

Web-based AIs connect through the LMCP Cloud Relay connector:

ChatGPT
Claude.ai (web)
Grok
Perplexity

Whichever you use, update_local_mcp behaves the same: ask in plain language and the update runs against your local install.

Automation

This tool is the maintenance backbone for everything else LMCP does. Chain it into a routine: have your AI run a daily brief, then check for an update and install it if one exists — so your toolset is always fresh before the day's work. It also pairs with diagnostics: if a tool misbehaves, ask the AI to check for an update first, since a fix may already be waiting. Because the update restarts LMCP, sequence it before, not in the middle of, a multi-step task.

Context

Everything LMCP touches is your real Mac data. The AI isn't working with a synced copy or a stale snapshot in some datacenter — it reads and acts on the actual apps running on your machine. Updating LMCP keeps that bridge healthy, so when you ask the AI to find an email, draft a reply, or pull up tomorrow's calendar, it's operating on live, accurate local information.

Productivity

Manual updates mean noticing a banner, downloading a DMG, quitting the app, dragging, reopening and re-granting focus — a few minutes of context-switching you rarely remember to do. With update_local_mcp, it's one sentence and a confirmation. Wire it into a weekly routine and you'll never run a months-old build again, which is the single biggest cause of avoidable tool errors.

Privacy & GDPR

LMCP runs entirely on your Mac. The update itself only fetches a signed application binary — your mail, messages, contacts and files never leave the device, and nothing is copied to a server. There's no account holding your data and no cloud mirror of your content. This local-only design makes LMCP GDPR-compliant by architecture. Ready to start? Download LMCP and let your AI keep it up to date from then on.