Aisha
Free
Users seeking culturally grounded AI responses
Every browser extension blocker breaks the moment you open a different browser, an incognito tab, or a browser you forgot you had installed. LockIn MCP routes around that by writing blocks directly to your hosts file — and lets your AI assistant manage the whole thing.
The tool runs a background daemon that exposes a small set of callable functions: block a site, start a timed focus session, grant a temporary unblock that expires automatically, and check what's currently blocked. Your AI assistant — Claude, ChatGPT, Perplexity, or Gemini — calls those functions when you ask in plain language. Blocks survive restarts and new browser tabs because they sit at the OS level, not inside any single application. The single-command installer wires up the MCP server and license verification in one step. The surface area is deliberately small — this does one thing, not a dashboard full of analytics.
Bottom line: Reach for this if you want your AI chat to enforce focus sessions without touching browser settings — but look elsewhere if you need cross-device sync, team policy enforcement, or blocks that travel outside your local machine.
Billed monthly at $2.50/mo
Billed yearly at $29.99 (saves 16% vs monthly)
Pay once, keep forever
View full pricing on lockinmcp.com →
Pricing may have changed since last verified. Check the official site for current plans.
Find your fit
More options in Personal Assistants. Compare pricing, platforms, and features side by side.
Free
Users seeking culturally grounded AI responses
Freemium
Individual users needing multimodal AI tools
Most focus blockers live inside a browser, which means a second browser is all it takes to route around them. LockIn MCP works differently: it edits the system hosts file so blocked domains resolve to localhost regardless of which browser, app, or tab you open. A background daemon keeps those blocks active across restarts, runs the countdown on timed temporary unblocks, and exposes four MCP tool functions — block_site, unblock_temp, focus_session, and get_status — that any compatible AI assistant can call on your behalf.
The differentiating mechanic is the MCP integration itself. Rather than a standalone app with its own interface, LockIn MCP turns your existing AI chat — Claude, ChatGPT, Perplexity, Gemini, or Poke — into the control surface. You type a natural-language request, the assistant calls the appropriate function, and the block is in place at the OS level within the same conversation. The vendor also provides a stable relay URL so remote MCP connections authenticate without extra configuration.
This fits developers and knowledge workers who already live inside an AI chat window and want focus enforcement without switching to a separate app. The scope is narrow by design: system-level blocking on a single machine, managed through AI commands. It does not sync blocks across multiple machines, enforce rules at a team or organizational level, or provide usage analytics. Teams that need centralized policy management or cross-device coverage will find the single-machine, single-user architecture a hard limit rather than a starting point.
Installation runs via a single npx command — npx -y lockin-mcp install — which handles license verification, initial site selection, and MCP server connection. The vendor states blocks persist in the hosts file and temp-unblock timers stay active through the daemon after reboot. A Chrome extension is mentioned in the FAQ as an additional integration path, though the core blocking mechanism operates independently of any browser extension.
Sign in to rate this tool or suggest an edit.