ApiVault Docs
ApiVault is a secure API key vault for developers and AI agents. Store encrypted secrets in the cloud, manage them from the web dashboard, inject them into local processes with the CLI, or expose scoped access to Cursor and other MCP clients.
Getting StartedCreate an account, add your first key, and connect the CLI or MCP in minutes.CLI ReferenceFull command reference for terminal workflows, secret injection, and scripting.MCP IntegrationConnect Cursor, Claude Desktop, and other MCP clients with OAuth-scoped access.Web AppDashboard, key management, settings, and account configuration.SecurityEncryption modes, authentication, sessions, and best practices.
Three ways to use ApiVault
ApiVault exposes three integration surfaces. Each talks to the same vault over HTTP — none of them access the database directly.
| Surface | Best for | Authentication |
|---|---|---|
| Web dashboard | Manual key management, account settings, reviewing connections | Browser session (Google, email/password, passkeys) |
CLI (apivault) | Terminal workflows, CI scripts, injecting secrets into local processes | Browser connect flow (apivault login) |
| MCP server | AI agents in Cursor, Claude Desktop, and other MCP clients | OAuth 2.1 with scoped tokens |
Production endpoints
| Resource | URL |
|---|---|
| Web app | https://api-vault-opal.vercel.app |
| MCP server | https://api-vault-opal.vercel.app/mcp |
| OAuth metadata | https://api-vault-opal.vercel.app/.well-known/oauth-authorization-server |
CLI vs MCP — when to use which
| Task | Use |
|---|---|
| Agent needs to look up or manage keys during a coding session | MCP |
Inject secrets into npm start or a local dev server | CLI run |
| CI/CD pipeline or shell script | CLI with --json |
Export .env for Docker, Next.js, or Vite | CLI env export |
| Connect ApiVault in Cursor settings | MCP setup |
| Revoke AI agent access | Settings → MCP Connections |
| Revoke terminal access | apivault logout |
Was this page helpful?