LockIn MCP

Let AI block distractions for you when you need to lock in

Productivity

Developer Tools

Artificial Intelligence

Visit WebsiteSee on Product Hunt

This is exactly the kind of MCP-native tool I've been wanting — no more willpower battles with browser extensions.

One use case I'd love: conditional unblocking tied to my actual dev workflow. Like "keep GitHub/Twitter blocked until my CI passes" or "unlock HN only after I close 3 Linear tickets."

Have you thought about integrating with GitHub Actions / Linear webhooks as unblock triggers? That would turn it from a timer-based blocker into a goal-based gatekeeper.

Great launch 🚀

Really like the idea of moving focus controls into the same workflow as the AI agent instead of another app or browser extension.

One feature I'd love to see is task-based automation. For example, "keep YouTube, X, and Reddit blocked until my test suite passes or my coding task is marked complete." That would make focus feel like part of the workflow rather than something I have to remember to manage manually.

Nice use of MCP for focus mode. The thing I’d want most for a hosts-file blocker is a clear recovery path: show the exact domains changed, the scheduled unblock time, and a one-command restore if the agent/session dies.

For agent workflows, task-scoped blocks feel safer than global “go demon mode”: block X/YouTube while a specific coding task is open, then require the agent to report what it restored. That makes it feel less like a trap and more like a reversible focus contract.

Editing the system hosts file directly is the part I like, no bypassable extension layer. Does the MCP server run fully locally so the block holds even with no network, and where does the blocklist/focus-schedule config actually live: a local file I can reuse across machines, or tied to an account? And if the agent or MCP process dies mid-block, does the hosts file get cleanly restored, or could I get stuck locked out until I edit it by hand?

I've lost more focus sessions to "just open a private window" than I'd admit. Hosts file blocking is the first thing that actually closes that loophole. Does the daemon need to stay running for temp-unblocks to expire, or is that handled on the OS side? Congrats on the launch!

Leta gooooo @LockIn MCP

Using MCP as the interface so the AI controls focus mode is clean. The agent that already knows your context can decide when you're drifting. MCP's stateless nature creates interesting session continuity challenges for tracking focus blocks. Does LockIn persist focus state across server restarts? And how do you handle the OS permission model for app blocking across platforms?

using MCP for this is a clever application. most MCP tools are focused on productivity and data access, using it for focus management is an unexpected angle. the "no bypassing" part is key because the whole reason chrome extensions fail is that you can just disable them in 2 seconds when willpower drops. does the agent enforce the block at a system level or is there still a way to override it if you really need to?

This should be so much higher! Literally the BEST distraction blocker I've ever used! Feels so much more natural than those other bs chrome extensions.

The hosts-file move is the actual unlock, every extension-based blocker dies the second you remember you can just toggle it off. And triggering it from an MCP command is smart, you're already in the agent so there's no dashboard to open and "accidentally" get sucked into. For demon mode I usually just full-screen one window and kill every tab, but I bypass my own willpower constantly, so something I can't easily undo is the real appeal here. Building on MCP myself, good to see more land in that space 👊

Huge congrats on shipping, Mil! Context-switching is the absolute killer of momentum. When deep into system integrations or complex API mapping, opening a separate dashboard just to block distractions usually creates another vector for getting side-tracked.

Shifting that control layer natively to the agent via an MCP command is a massive workflow upgrade. Since the agent handles the block natively, is it possible to chain this to specific tasks? For instance, instructing the agent to keep social domains locked until a specific script finishes executing or a local build passes?

Excited to test out this direct-to-system approach!