Turn Claude or ChatGPT Into a Coding Agent on Your Mac — Files, Terminal, Browser

Give your AI real hands on your Mac: read your files, run terminal commands, and drive the browser — locally and with your permission. A local, permissioned alternative to remote computer-use, running on your own machine from the Claude or ChatGPT you already use.

L
LMCP··5 min read
Try it — copy this prompt into your AI

Read the errors in ./build.log, find the failing test in this repo, run the suite, and tell me what's wrong.

Most people use AI as a chat box: it talks, you copy-paste. The people who get the most out of it give it hands. With LMCP — a free, native macOS MCP server — Claude or ChatGPT can read the files on your Mac, run commands in your terminal, and drive your browser, so it can actually do the work instead of describing it. It runs entirely on your machine, with your permission, and no API keys.

Local computer-use, on your own Mac

Remote "computer-use" and agentic IDEs spin up a sandbox in the cloud, then you re-upload your repo, your credentials, your context. LMCP flips that: the agent runs on the Mac you're already sitting at, against your real files, your real shell, your real logged-in browser. Nothing is copied to someone else's server, and you decide exactly what it can touch. It's the difference between renting a stranger's computer and lending your AI your own — with a leash.

The hands it gets

  • Filesystemfs_read, fs_list, fs_search: read any file and walk any folder, scoped to the directories you allow (your home folder by default; add project folders or drives in Settings).
  • Terminalrun_terminal_command: run a build, a test suite, git, a script, a one-off shell command — on your machine, in your environment.
  • Browserchrome_* / safari_* / web_*: navigate, read a page, click, fill forms, run JS, and pull structured data from a real, logged-in browser. You sign in yourself; the AI never sees your password.
  • Everything else — the same connection also exposes Mail, Calendar, Notes, Reminders, Messages and 200+ tools, so an agent can chain "read this file → run the tests → email me the result."

What that looks like

Give your agent a goal and let it work the loop:

  • "Read the errors in ./build.log, find the failing test in this repo, and tell me what's wrong."
  • "Run the test suite and summarize which tests fail and why."
  • "Look through ~/Projects/api for every place we call the old auth endpoint and list them."
  • "Open our staging dashboard, read the error rate, and if it's above 2% draft me a Slack message."

The agent reads, runs, checks the output, and iterates — dozens of tool calls behind a single sentence — the way a capable teammate would.

You hold the leash

Power on your own machine needs guardrails, and they're built in: filesystem access is scoped to folders you allow (add or remove them in Advanced Settings → Allowed folders), everything runs locally so your code and data never leave the Mac, and there's an audit log of what the agent did. This local-first, permissioned design is the same model LMCP uses for everything else — you get an agent's leverage without shipping your machine to the cloud.

Which AI can be the agent?

  • Desktop clients — Claude Desktop, Cursor, VS Code, Windsurf and Zed auto-configure via a local stdio connection. Nothing to wire up.
  • Web AIs — ChatGPT, Claude.ai, Grok and Perplexity connect through the LMCP Cloud Relay, so the agent you already pay for can reach your Mac from the browser — while the files, shell and browser stay on your machine.

Ready to stop copy-pasting and give your AI real hands? Download LMCP, connect your assistant, and hand it a goal.

Ready to try it?

Works with Claude, Cursor, VS Code, ChatGPT and any MCP client

Download for Mac
FreemacOS 12+ · Apple Silicon & Intel

✦ llms.txt