LockIn MCP

LockIn MCP's whole pitch is that blocking was never the hard part; starting the block was. That is a real distinction. Most focus tools lose to friction: you have to notice you're drifting, quit the browser, open the app, pick a profile, and start a session. LockIn deletes those steps by living inside the chat window you're already staring at. You type a sentence, the assistant calls enter_focus_mode or block_domains, and the entry lands in your hosts file. Because the block is written at the OS level as 127.0.0.1, opening a second browser, a private window, or a fresh profile doesn't get you around it — the usual escape hatches from extension-based blockers are closed. The background daemon keeps MCP alive and timed unblocks ticking across restarts, and macOS, Windows, and Linux are all covered, with platform-specific DNS flush on the latter two. Installation is genuinely short: one terminal command, then per-agent configuration. Where it gets interesting is the optional Chrome extension, which is where task-aware blocking lives. While a focus task is active, the extension can check a page against that task, let the documentation you need through, and block the rabbit holes before they load. In its own example, youtube.com is blocked because it doesn't relate to the current task while tiktok.com and gmail.com are not. That is a meaningfully different mechanic from a static blocklist. The privacy design is also more restrained than it could have been: only distraction attempts reach the dashboard, LockIn states it does not upload your full browsing or search history, and task checks may send a page URL and short excerpt to LockIn's server for a relevance check that it says stays on its side. Disconnecting an agent is OAuth revocation under Dashboard → Agents, though you may still need to remove the connector inside Claude, ChatGPT, or Poke separately. The honest limitations. Blocking is desktop-only — there is no iOS or Android app, so your phone is untouched and you will want Screen Time or similar alongside it. There is no cross-device sync and no team management layer: no admin console, no shared blocking policy across machines. Hosts-file blocking is all-or-nothing per domain, so you can't block one browser and leave another alone. And the task-aware part depends on letting the extension send a page URL and excerpt for a relevance check — if that crosses a line for you, you're down to static domain blocks. Pricing options are narrow but cheap: $2.99/mo, $29.99/year (billed yearly at $2.50/mo), or $59.99 lifetime, each with a 3-day free trial on the subscriptions. Where it fits: AI power users who already run an MCP client, students and remote workers fighting afternoon doomscrolling, developers who want an enforced deep-work block that survives a restart, and people with ADHD who do better when the boundary is drawn by something other than willpower. Where it doesn't: anyone who needs phone blocking, teams needing multi-device policy