API Locker
by apilockercommunityv1.0.3
API Locker is a CLI that stores API keys and OAuth credentials in an encrypted vault and injects them as environment variables when running commands. It also exposes an MCP server so MCP-compatible clients can read and manage the vault through the CLI bridge.
From the registry: Encrypted credential vault: LLM, service & OAuth keys. 21-tool MCP server for your AI agent.
Install & configure
Prerequisites
- requiredInstall Node.js 18+API Locker requires Node.js 18 or newer.
- requiredInstall API Locker CLIInstall the API Locker CLI globally with npm.
$ npm install -g apilocker - requiredRegister this device with API LockerRun the device registration flow once. This opens a browser for confirmation and stores the master token locally so the MCP bridge can authenticate automatically.
$ apilocker register
Install in your client
Paste into the AI you're chatting with — it will figure out the rest
Please install the `apilocker` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install Node.js 18+** — API Locker requires Node.js 18 or newer.
- **Install API Locker CLI** — Install the API Locker CLI globally with npm. Run: `npm install -g apilocker`
- **Register this device with API Locker** — Run the device registration flow once. This opens a browser for confirmation and stores the master token locally so the MCP bridge can authenticate automatically. Run: `apilocker register`
Canonical MCP server config (stdio transport):
- command: `apilocker`
- args: ["mcp"]
Note: The MCP server is provided by the API Locker CLI as a stdio bridge. It reads authentication from ~/.apilocker/config.json automatically, so no environment variables are required in MCP client config. For self-hosted deployments, registration can be performed against a custom API endpoint with `apilocker register --url <your-api-url>`.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.Note: The MCP server is provided by the API Locker CLI as a stdio bridge. It reads authentication from ~/.apilocker/config.json automatically, so no environment variables are required in MCP client config. For self-hosted deployments, registration can be performed against a custom API endpoint with `apilocker register --url <your-api-url>`.
Tools (25)
apilocker register
Register the current device via browser confirmation.
apilocker store
Store a credential in the vault; supports regular keys and OAuth credentials.
apilocker list
List stored credentials, grouped by type and filterable by tag, provider, category, or search.
apilocker run -- <cmd>
Run a command with vault secrets injected as environment variables.
apilocker get <alias>
Print a single stored secret value to stdout.
apilocker env
Emit shell export statements for loading vault secrets into the current shell.
apilocker init
Create a project-level .apilockerrc file that pins required credentials.
apilocker import .env
Import an existing .env file into the vault.
apilocker rotate <alias>
Replace the value of an existing credential.
apilocker rename <old> <new>
Rename a credential alias without breaking existing references.
apilocker pause <alias>
Pause proxy access for a credential without deleting it.
apilocker resume <alias>
Resume proxy access for a paused credential.
Prerequisites
- • Node.js 18
Packages
apilocker
npmv1.0.3transport: stdio
Details
- Language
- TypeScript
- License
- MIT
- Released
- Apr 10, 2026
- Last commit
- Apr 10, 2026
- Registry name
- io.github.apilocker/apilocker