Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

LockIn

by Sky-walkerXversion 1.0.0i★ –iRuns in the cloud
Registry nameio.github.Sky-walkerX/lockin

Install

Overview

Description from the maker (original English)

A notebook your coding agents write to: notes that track the code's commit, and handoffs.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Docs, sheets & office work

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://lockin.namankhandelwal.dev/api/mcp

Run this in your terminal

claude mcp add --transport http lockin https://lockin.namankhandelwal.dev/api/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "lockin": {
      "url": "https://lockin.namankhandelwal.dev/api/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "lockin": {
      "type": "http",
      "url": "https://lockin.namankhandelwal.dev/api/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://lockin.namankhandelwal.dev/api/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Sky-walkerX, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Docs, sheets & office worki

  • More stars than 0% of the other 2181 servers in this category
  • Published to the registry more recently than 57% of the other 2181 servers in this category
  • Basic checks equal to or better than 100% of the other 2181 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is LockIn safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 23 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago
Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 6 days ago
Install

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 3 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

[Try it](https://lockin.namankhandelwal.dev) · Self-host · Connect your agents · Ask your notes · Develop

You learn things inside Claude, Codex and Cursor every day, and most of it is gone when the session ends. LockIn keeps it. Your agents save notes into it over MCP, you file them by subject, and any model you choose answers questions from them.

The launch film, 45 seconds, with sound:

https://github.com/user-attachments/assets/3ae46572-283e-49fd-a3dc-e178dd269e40

How it fits together

Monday: Claude Code saves a note to Project-X, and you witness it. Thursday: Codex picks up where it left off.

flowchart LR

cc["Claude Code"] -- save_note --> mcp cx["Codex"] -- search_notes --> mcp more["Cursor, Claude.ai, ChatGPT, any MCP client"] --> mcp mcp(["LockIn's MCP server /api/mcp"]) --> nb[("Your notebook notes filed by subject")] nb --> you["You witness, read, plan"] nb --> ask["Ask a model you choose, answers cite your pages"]

What's in it

Agents write here

Claude Code, Codex, Cursor or any MCP client can save, search and read your notes. Everything an agent saves says who recorded it and waits for you to witness it.

Ask your notes

Chat with a model in your browser (WebGPU), on your own machine (Ollama, LM Studio), or from Anthropic, OpenAI, Gemini or OpenRouter with your own key. Answers cite the pages of your notes they came from.

Notes by subject

Markdown with code, plus the PDFs and links you're reading, filed under the subject they belong to.

Read without distraction

Any note opens full screen.

A plan when you want one

Tasks, focus time, exam pace and spaced revision live in each subject's Plan tab, out of the way until you need them.

Yours

AGPL-3.0, self-hostable with one command, and everything exports to Markdown or JSON.

Self-hosting

You need Docker with Compose.

git clone https://github.com/Sky-walkerX/LockIn.git && cd LockIn

cp .env.example .env

set AUTH_SECRET in .env: openssl rand -base64 32

docker compose up -d

Open http://localhost:3000 and create an account. The port answers only on the machine itself; for a server, see HTTPS below. The first start pulls the released images, waits for Postgres and applies the database migrations before the app starts. Images are published for amd64 and arm64; where there's none for your version, Compose builds from the checkout instead.

What runs:

ServiceWhat it does
dbPostgres 17. Data in the db volume.
migrateApplies migrations (prisma migrate deploy) and exits.
appLockIn on port 3000. Note images and PDFs are stored in the uploads volume.
ingestOptional. PDF and web-page text extraction plus server-side embeddings.
caddyOptional. HTTPS in front of the app, see below.

To add text extraction and server-side embeddings, set INGEST_SECRET (any long random string) and INGEST_URL=http://ingest:8080 in .env, then:

docker compose --profile ingest up -d

The ingest image carries its embedding model, so it's about 1 GB. Without it, keyword search works, and the browser does embeddings itself. It reads two documents at a time and stops one that takes over 140 seconds; a third waits 20 seconds for a slot and is then told the service is busy. PARSE_CONCURRENCY in .env raises the first number, on a machine with a core and a few hundred MB to spare per document.

To update, pull the new release. The compose file names the version it goes with, so the images always match the checkout. Migrations run on start:

git pull && docker compose pull && docker compose up -d

To run the code in your checkout instead of a release, build it: docker compose up -d --build.

docker compose ps shows whether the app is healthy; the same check is at /api/health (200 when the app can reach its database) for an uptime monitor.

Backups

Everything lives in two volumes: db (Postgres) and uploads (note images and PDFs). Back up both, and take a backup before updating.

# back up

docker compose exec -T db pg_dump -U lockin -Fc lockin > lockin.dump docker compose cp app:/data/uploads ./uploads-backup

restore, into a stack that is up

docker compose exec -T db pg_restore -U lockin -d lockin --clean --if-exists < lockin.dump docker compose cp ./uploads-backup/. app:/data/uploads docker compose exec -u root app chown -R lockin /data/uploads # copied files arrive owned by the host user

Keep AUTH_SECRET with the backups. A restored copy with a different secret signs everyone out.

Settings in .env:

Variable
AUTH_SECRETRequired. Signs sessions and upload links.
PUBLIC_URLThe address people open LockIn at. Default http://localhost:3000.
LOCKIN_PORTHost port. Default 3000.
LOCKIN_BINDWhich of the machine's addresses that port listens on. Default 127.0.0.1: the machine itself, which is you or a proxy running on it.
LOCKIN_VERSIONThe release to run, such as 1.0.0. Default: the release your checkout is.
POSTGRES_PASSWORDPassword for the bundled Postgres.
SIGNUPopen (the default) lets anyone who can reach the address make an account. closed stops new accounts once the first one exists.
GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRETOptional. "Continue with Google" appears only when both are set.
SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASSWORD, SMTP_FROMOptional. Outgoing email, see Accounts below.
OPERATOR_EMAIL, OPERATOR_NAME, OPERATOR_HOSTINGOptional. Privacy and terms pages, see Accounts below.
STORAGE_QUOTA_MBMegabytes of images and PDFs each account may store. Default 1024; 0 for no ceiling.
RATE_LIMITSoff drops the limits below. Default on.
TRUSTED_PROXY_HOPSHow many reverse proxies stand in front of LockIn. Default 1; 0 when visitors reach the port directly.
INGEST_URL, INGEST_SECRETOptional. See above.
HTTPS

On a machine the internet can reach, LockIn needs HTTPS: without it sessions and agent tokens cross the network in the clear, and browsers won't run a local model. The https profile adds Caddy, which gets a certificate from Let's Encrypt and renews it. Point your domain at the machine, open ports 80 and 443, and set in .env:

PUBLIC_URL=https://notes.example.com   # no trailing slash
docker compose --profile https up -d

The proxy's settings are in Caddyfile: a year of Strict-Transport-Security, and a 60 MB cap on a request's body.

With a proxy of your own on the machine (nginx, Traefik) leave the profile off, set PUBLIC_URL, point the proxy at 127.0.0.1:3000 and have it send Strict-Transport-Security. That's the one security header LockIn leaves out, since only the proxy knows the site is served over HTTPS; the rest (a content security policy, no framing by other sites, no content sniffing) it sends itself.

Port 3000 isn't open to the network, so the proxy can't be gone around. To use LockIn from other machines without a proxy, on a home network say, set LOCKIN_BIND=0.0.0.0 and TRUSTED_PROXY_HOPS=0. Docker publishes that port past most host firewalls, and everything, passwords and agent tokens included, then travels unencrypted.

Accounts

Anyone who can open the address can sign up, unless you set SIGNUP=closed: make your own account first, then close it.

With SMTP_HOST set, LockIn sends two emails. A new account gets a link to confirm its address and can't sign in until it's opened, and "Forgot password" sends a link that sets a new one. The links are built from PUBLIC_URL, so set it to the address people really use. Without SMTP there's no email: accounts sign in straight away, and you reset a forgotten password yourself:

scripts/set-password.sh someone@example.com

Changing or resetting a password signs that account out everywhere. Resetting one, by the emailed link or with the script, also disconnects every agent and connected app, in case someone else had been in: a token they made would outlast the new password. Connect them again in Settings. Settings has "Change password" and "Delete account", which removes the notebook, its files and every agent's access.

A notebook you run for yourself has no privacy or terms page. If other people sign up on yours, set OPERATOR_EMAIL, and OPERATOR_NAME if you like: /privacy and /terms appear, linked from the landing and sign-up pages, and name you as the one to write to. OPERATOR_HOSTING is a sentence of your own, shown on the privacy page, on where the data is kept and how long backups are. Both pages describe what LockIn does and make a few promises in your name (that you don't read people's notes, that you'll give notice before closing), so read them before turning them on.

"Continue with Google" makes a new account, or opens the existing one with that address if the address was confirmed. It won't attach to an account made with a password whose address was never confirmed, so nobody can claim an address ahead of its owner.

Limits

LockIn counts a few things so one caller can't wear the instance out, and answers 429 with Retry-After past

Only the beginning is shown; read the rest in the repo

Ask PopNx