
API Locker
io.github.apilocker由 GitHub 帳號 apilocker 發布v1.0.3更新於 Oct 25, 2026
Encrypted credential vault: LLM, service & OAuth keys. 21-tool MCP server for your AI agent.
概覽
API Locker 的本機 MCP 橋接,連接加密憑證保險庫,讓助理讀取與管理已存的 LLM、服務與 OAuth 金鑰。
- 可以做什麼
- 讀取並列出已存憑證,依 LLM、服務與 OAuth 分類,可用標籤、供應商、類別或關鍵字篩選。儲存、輪替、重新命名、暫停、恢復與刪除憑證,包含多欄位的 OAuth 項目。取出單一金鑰值,或輸出可供 shell 使用的 export 敘述。管理已註冊裝置與受限存取權杖,包含撤銷。檢視揭示、代理呼叫、重新命名與輪替的稽核日誌,並執行安全健康檢查。
- 適用情境
- 當你把 API 金鑰與 OAuth 用戶端憑證存放在 API Locker,並希望助理不必開啟主控台就能查詢、新增、輪替或稽核這些憑證時適用。適合已在用 API Locker 命令列、想在 Claude Code、Claude Desktop、Cursor、Zed 或 Continue 中管理保險庫的開發者。
- 執行需求
- 透過 apilocker npm 套件以 stdio 在本機執行,用 mcp 子命令啟動;需要 Node.js 18 或更新版本。需要 API Locker 帳號,並透過瀏覽器授權流程註冊裝置;橋接會從本機設定檔讀取主權杖。需要能連線至 API Locker 服務的網路。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 API Locker,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
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
Requires Node.js 18 or newer.
Get started in three commands
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.
⚡ Service API Keys
Stripe, Twilio, Resend, ElevenLabs, Cloudflare, GitHub, Clerk, Sentry, PostHog, Cloudinary, Mux, SendGrid, Vercel, Upstash, LemonSqueezy — plus custom for anything else.
🔗 OAuth Credentials
Google, GitHub, Slack, Microsoft, Notion, Spotify, Twitter/X, LinkedIn, Discord, Zoom, Dropbox, Salesforce, HubSpot — plus custom OAuth for anything else.
The full command set
The .apilockerrc file
Pin a project to a specific set of credentials with a committable config file. apilocker init walks you through creating one:
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:
- You run
apilocker register - Your browser opens to a single-card confirmation page
- You click "Authorize"
- 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
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:
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:
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:
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
- Website: www.apilocker.app
- Dashboard: www.apilocker.app/dashboard
- API: api.apilocker.app
- Changelog: www.apilocker.app/changelog
License
MIT © 2026 API Locker
來源:cli/README.md,提交 babe588
工具
0版本歷史
1- v1.0.3最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分