API Locker
Store LLM, service, and OAuth keys in an encrypted vault your agent reaches through 21 MCP tools instead of pasting secrets into chat.
Overview
io.github.apilocker/apilocker is a Ship-phase MCP server that provides an encrypted vault and 21 tools for LLM, service, and OAuth credentials your AI agent can use safely.
What is this MCP server?
- Encrypted credential vault for LLM keys, service tokens, and OAuth credentials
- 21-tool MCP server surface documented in the catalog description
- npm package apilocker v1.0.3 launched via npx with positional argument mcp
- stdio transport suited to local Claude Code and Cursor setups
- Website apilocker.app and GitHub source under apilocker/apilocker cli subfolder
- 21-tool MCP server (per catalog description)
- npm package apilocker version 1.0.3 with npx mcp invocation
- Transport: stdio
What problem does it solve?
Pasting API and OAuth keys into agent sessions or repos is the fastest way for indie projects to leak production credentials.
Who is it for?
Solo builders who run multiple MCP integrations and need one encrypted store with a broad tool API for agents.
Skip if: Teams that already mandate a corporate HSM-only workflow with no third-party vault, or builders who only need a single .env locally with no agent access.
What do I get? / Deliverables
After you run apilocker via npx mcp, your agent retrieves secrets from the encrypted vault through MCP tools instead of handling raw keys in conversation.
- Local stdio MCP server backed by API Locker encryption
- Agent access to vault operations across the documented 21-tool surface
Recommended MCP Servers
Journey fit
How it compares
21-tool encrypted secrets vault MCP, not an API discovery marketplace or smart-home device bridge.
Common Questions / FAQ
Who is io.github.apilocker/apilocker for?
It is for indie developers and agent users who need centralized encrypted storage for LLM, OAuth, and service keys reachable from MCP-compatible coding tools.
When should I use io.github.apilocker/apilocker?
Use it during Ship security when you are launching or hardening a project and want agents to pull credentials from a vault instead of chat logs or committed env files.
How do I add io.github.apilocker/apilocker to my agent?
Configure stdio MCP to run npx apilocker mcp (package apilocker 1.0.3 per catalog), complete API Locker setup at apilocker.app if required, then point Claude Code or Cursor at that command.