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

API Locker

by apilockerversion 1.0.3i★ –iRuns on your computer
Registry nameio.github.apilocker/apilocker

Install

Overview

Description from the maker (original English)

Encrypted credential vault: LLM, service & OAuth keys. 21-tool MCP server for your AI agent.

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 on your computer
  • Transport: stdio
  • Category: Search & AI memory

Install

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

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

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

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "apilocker": {
      "command": "npx",
      "args": [
        "-y",
        "apilocker",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add apilocker -- npx -y apilocker mcp

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "apilocker": {
      "command": "npx",
      "args": [
        "-y",
        "apilocker",
        "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": {
    "apilocker": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "apilocker",
        "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.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

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

Runs on your computer; the tool list appears in your AI app after you install it.

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 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account apilocker, 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 applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 7226 servers in this category
  • Published to the registry more recently than 8% of the other 7226 servers in this category
  • Basic checks equal to or better than 100% of the other 7226 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 API Locker 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 on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.3) reached the registry 7 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

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

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated 3 days ago
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 44 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.

API Locker

One vault, three types of credentials. LLM API keys, service API keys, and OAuth credentials — all encrypted, all injectable into your code with a single command.

API Locker replaces the .env file with one encrypted vault. Store your OpenAI key, your Stripe secret, your Google OAuth client — all in one place — and inject them into any command with apilocker run -- npm start. Your raw credentials never touch disk, never live in shell history, never get committed to git.

This is the command-line interface. Website · Dashboard

Install

npm install -g apilocker

Requires Node.js 18 or newer.

Get started in three commands

# 1. Install the CLI (above)

2. Register this device — opens your browser for a one-click confirmation

apilocker register

3. Run any command with your vault secrets injected as env vars

apilocker run -- npm start

That's it. Your process.env.OPENAI_API_KEY, process.env.STRIPE_SECRET_KEY, process.env.GOOGLE_OAUTH_CLIENT_SECRET — everything you'd normally drop in a .env file — is now injected into the subprocess for exactly the duration of that command. When the command exits, the secrets are gone.

One vault, three types of credentials

🧠 LLM API Keys

OpenAI, Anthropic, Gemini, Groq, Mistral.

apilocker store --name OPENAI_API_KEY --provider openai --key sk-proj-xxxxx

apilocker run -- node my-ai-app.js

⚡ Service API Keys

Stripe, Twilio, Resend, ElevenLabs, Cloudflare, GitHub, Clerk, Sentry, PostHog, Cloudinary, Mux, SendGrid, Vercel, Upstash, LemonSqueezy — plus custom for anything else.

apilocker store --name STRIPE_SECRET_KEY --provider stripe --key sk_live_xxxxx

apilocker run -- npm start

🔗 OAuth Credentials

Google, GitHub, Slack, Microsoft, Notion, Spotify, Twitter/X, LinkedIn, Discord, Zoom, Dropbox, Salesforce, HubSpot — plus custom OAuth for anything else.

apilocker store --oauth \

--name google-oauth \ --provider google-oauth \ --client-id 856449...apps.googleusercontent.com \ --client-secret GOCSPX-xxxxx \ --scopes "openid email profile"

Injects GOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET, etc.

apilocker run -- node oauth-app.js

The full command set

CommandWhat it does
apilocker registerRegister this device via browser confirmation. No pasted tokens.
apilocker storeStore a credential. --oauth for multi-field OAuth, otherwise --key.
apilocker listList credentials grouped into LLM / Service / OAuth buckets. Filter with --tag, --provider, --category, --search.
apilocker run -- Run any command with vault secrets injected as environment variables.
apilocker get Print a single secret value to stdout (for scripting). --field for OAuth fields.
apilocker envEmit shell-eval-able export statements. eval "$(apilocker env)" to load into current shell.
apilocker initPin specific keys to a project directory via a committable .apilockerrc file.
apilocker import .envMigrate an existing .env file into the vault. Pattern-matches provider prefixes and offers to replace the .env with an .apilockerrc.
apilocker rotate Replace a credential's value. Scoped tokens keep working; rotation is transparent to consumers.
apilocker rename Rename a credential alias. Lossless — existing .apilockerrc files that reference the old name keep working via transparent fallback.
apilocker pause / resume Freeze proxy access without deleting. Reveal / run / get / env still work on paused credentials.
apilocker delete Permanently delete a credential.
apilocker devices list / revoke Manage devices registered to your account.
apilocker token create/list/pause/resume/deleteManage scoped access tokens for app/proxy use.
apilocker activityView the audit log. Add --follow / -f to stream new events live.
apilocker doctorSecurity health check: stale rotations, unused keys, expiring tokens, local config permissions.
apilocker updateCheck npm for a newer version.

The .apilockerrc file

Pin a project to a specific set of credentials with a committable config file. apilocker init walks you through creating one:

# .apilockerrc — safe to commit to git, contains only pointers

keys:

  • OPENAI_API_KEY
  • STRIPE_SECRET_KEY
  • google-oauth

After apilocker init, anyone cloning your repo who runs apilocker run -- npm start gets the same env vars — assuming they have access to those aliases in their own vault. It's like a package.json for credentials: the file declares what the project needs, each developer has their own vault.

Why the CLI doesn't ask for a pasted master token

Unlike most developer tools, apilocker register doesn't want you to paste a secret from the dashboard. Instead:

  1. You run apilocker register
  2. Your browser opens to a single-card confirmation page
  3. You click "Authorize"
  4. The CLI receives a per-device master token over an authenticated polling channel — it never touches your clipboard, shell history, or screen

This is the RFC 8628 device authorization flow (the same pattern gh, vercel, wrangler, flyctl, and gcloud use). It's strictly safer than pasted tokens because the secret never appears anywhere a human can accidentally leak it.

New users? The same flow handles signup — your first OAuth click with GitHub/Google creates the account automatically. No separate visit to the web portal required.

MCP integration — connect your AI assistant

API Locker exposes a full Model Context Protocol server with 25 tools so Claude Code, Claude Desktop, Cursor, Zed, Continue, and any other MCP-compatible client can read and manage your vault directly.

Claude Code — one command
claude mcp add apilocker -- apilocker mcp

Verify with claude mcp list. You should see apilocker: apilocker mcp - ✓ Connected. The server is available in your next Claude Code session automatically.

Claude Desktop, Cursor, Zed, Continue

The CLI ships with apilocker mcp — a stdio bridge that handles the connection automatically. Configure any MCP client with:

{

"mcpServers": { "apilocker": { "command": "apilocker", "args": ["mcp"] } } }

The bridge reads your master token from ~/.apilocker/config.json automatically. No credentials go in the client config itself.

Print client-specific config with the built-in helper:

apilocker mcp config --client claude-desktop   # or claude-code, cursor, continue, zed, generic

Full docs: https://www.apilocker.app/docs/mcp — includes config file locations for each client, troubleshooting, and the full 25-tool catalog.

Visual status: the dashboard has a dedicated MCP panel at https://www.apilocker.app/dashboard#mcp showing server status, a test-connection button, copy-pasteable config for every major client, and a live feed of recent MCP activity.

Security posture

  • AES-256-GCM encryption on every stored credential. Keys never leave the vault in plaintext except when revealed to an authenticated master-token holder (you).
  • Per-device tokens with independent revocation. Stolen a laptop? Revoke that one device; every other device keeps working.
  • OAuth CSRF protection with state tokens bound to a 10-minute KV window.
  • Strict file permissions (0600) on ~/.apilocker/config.json.
  • Audit-logged everywhere: every reveal, every proxy call, every rename, every rotation. Watch them live with apilocker activity --follow.
  • Lossless rename with previous_names fallback: renaming a credential never breaks existing code. Old aliases transparently resolve to the current credential with a gentle nudge to update configs.
  • Pause/resume to freeze proxy access during incident response without losing the credential itself.

Configuration

Config lives at ~/.apilocker/config.json (mode 0600). Don't check it in.

Override the API endpoint for self-hosted deployments:

apilocker register --url https://api.your-locker.example.com

Status

API Locker is free to use with unlimited keys, unlimited tokens, and unlimited proxy calls. Early adopters get grandfathered into free Pro permanently when paid plans launch.

Links

License

MIT © 2026 API Locker

Ask PopNx