Quick verdict

LockIn MCP is a desktop-focused, hosts-file–based distraction blocker that pairs OS-level blocking with configurable third‑party AI assistants to support focused sessions; consider it if you want local, system-wide blocking and are comfortable with technical setup and system changes.

What it is

Confirmed: the website describes a tool that edits your system hosts file and runs a local background service (an MCP server) to redirect or block distracting domains. The product pages and docs also describe connecting multiple AI assistants (examples listed include ChatGPT, Claude, Perplexity, Gemini and others) to run guided focus sessions.

Who should consider it

• Technical users comfortable running a terminal command and installing Node.js (the installer requires Node.js 18+).
• People who prefer system-level blocking (hosts-file) rather than only browser-based extensions.
• Users who want to experiment with integrating third‑party AI assistants into a distraction-blocking workflow.

Why it may be useful

• System-level blocking: because it edits the hosts file, blocks are intended to apply across browsers and many apps, not just a single browser profile.
• Persistent blocking: the site states a background service maintains hosts-file entries so blocks persist across restarts.
• AI-guided sessions: the product pairs blocking with AI assistants configured via a dashboard or CLI, which may help with session prompts, planning, or focused workflows.

Confirmed facts (what the site states)

• Installer: the site documents a one-line installer (npx -y lockin-mcp install) that starts a local MCP server and walks through license verification and site selection.
• Cross-platform: the site targets desktop OSes (macOS, Linux, Windows) and references a Chrome extension for browser-side integration.
• Pricing options: the site lists monthly/yearly subscription and a lifetime license option and references a free trial on the yearly plan.
• Account and tokens: the privacy text notes collection of email/account info and the use of tokens for license checks and device authorization.

Limitations and cautious interpretation

• Integration polish: the website presents blocking + AI coaching as an integrated workflow; how smooth that integration is in everyday use appears to vary by agent and may require extra setup for some assistants.
• Technical surface: some agent integrations are noted as requiring CLI or additional setup steps, so expect configuration work for certain features.
• Installer effects: because the installer edits the hosts file and runs a background service, users are responsible for those system changes per the terms of service.

What to verify before you rely on it

• Exact plan features and current prices: the site lists plans and examples, but confirm current pricing and what each plan includes on the official pricing page.
• Refunds, cancellations, and trial terms: the site mentions a trial but does not clearly detail full refund or cancellation policies.
• Uninstall and recovery: the site does not clearly state whether uninstall always reverts hosts-file edits—confirm uninstall and hosts-file recovery steps.
• Privacy and telemetry: verify full telemetry details, retention periods, and third‑party sharing practices on the privacy page if data handling matters to you.
• Security posture and transparency: the website does not clearly state a public security audit history, a vulnerability disclosure process, or whether the codebase is open-source; verify these if they are important for your risk profile.

Bottom line

If you are technically comfortable with system-level installs and want an OS-wide blocker that the site pairs with configurable AI assistants, LockIn MCP appears worth investigating. Before installing or paying, confirm pricing/plan details, uninstall and hosts-file recovery behavior, full privacy/telemetry terms, and any security or open-source information you require.