@lobsterkit/vault-mcp
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@lobsterkit/vault-mcp store my OpenAI API key as openai_key"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@lobsterkit/vault-mcp
MCP server for LobsterVault — encrypted secret storage for AI agents. Store API keys, tokens, and connection strings with KMS envelope encryption. No API keys, no human signup, no configuration.
Quick Start
Add to your MCP config (.mcp.json, claude_desktop_config.json, .cursor/mcp.json, etc.):
{
"mcpServers": {
"lobstervault": {
"command": "npx",
"args": ["-y", "@lobsterkit/vault-mcp@0.1.0"]
}
}
}On first use, an account is created automatically and your token is saved to ~/.lobstervault/token.
Related MCP server: sops-mcp
Tools
Tool | Description |
| Store or update a secret (KMS-encrypted). Returns version number. |
| Retrieve a decrypted secret value. Returns null if not found. |
| Permanently delete a secret. |
| List all secret names, versions, timestamps. Values never returned. |
| Load all secrets into process.env. Returns count injected. |
| Re-encrypt with fresh DEK (Pro+ tier). |
| Create a time-limited, read-only share link for a secret (Builder+). |
| List all active share links on the account (Builder+). |
| Revoke a share link immediately (Builder+). |
| Retrieve a shared secret using a share token (no auth required). |
| View tier, limits, and current usage. |
Environment Variables
Variable | Description |
| API key (skips auto-signup and file persistence) |
| Custom API base URL (default: |
Links
Website: theclawdepot.com/vault
SDK: @lobsterkit/vault
API docs: api.theclawdepot.com/vault/docs
LobsterKit Ecosystem
This MCP server is part of the LobsterKit multi-product ecosystem. Accounts can be linked across LobsterVault, LobsterDB, and LobsterMail using a linkToken at signup, enabling a single Stripe customer and an automatic 15% multi-product discount.
License
MIT
Available Tools
11 toolsdelete_secretDelete SecretA
Permanently delete a secret.
Inputs: name (required).
get_accountGet AccountA
Get your account tier, secret usage, and limits.
Inputs: no named parameters.
get_secretGet SecretA
Retrieve and decrypt a secret value by name. Returns null if not found. Pass a version number to retrieve a specific historical version (Builder+ tier).
Inputs: name (required), version.
inject_secretsInject SecretsA
Load all secrets into the process environment (process.env). Returns the count of secrets injected. Use at agent startup to make all stored secrets available as env vars.
Inputs: no named parameters.
list_secretsList SecretsA
List all secret names on the account. Values are never returned in list operations.
Inputs: limit, cursor, prefix.
rotate_secretRotate SecretA
Re-encrypt a secret with a fresh Data Encryption Key. Use after KMS key rotation or as a security best practice. Requires Pro tier.
Inputs: name (required).
set_secretSet SecretA
Store or update a secret. The value is envelope-encrypted server-side using AWS KMS. Returns the new version number.
Inputs: name (required), value (required), metadata, expiresAt, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Every tool targets a distinct resource and action: secret CRUD, share lifecycle, account info, and environment injection. The similar-looking get_secret and get_shared_secret are clearly separated by authentication model and token/name input.
All tools follow a consistent snake_case verb_noun pattern, such as set_secret, list_shares, delete_secret, and revoke_share. This makes the toolset predictable and easy for an agent to navigate.
Eleven tools is well within the ideal range and each tool earns its place by covering a distinct secrets-management capability. There are no redundant or filler tools.
Secrets support create/update, read, versioned retrieval, delete, list, rotation, and environment injection. Shares support create, list, revoke, and anonymous retrieval, with account tier visibility, so the surface covers the full lifecycle with no obvious dead ends.
Maintenance
Related MCP Connectors
Secure and manage MCP servers through the Speakeasy AI Control Plane from your agent.
Cloud-hosted MCP server for durable AI memory
MCP server for building and testing AI agents with multi-model experimentation and insights.
MCP server teaching AI agents to implement TideCloak: auth, E2EE, IGA, security analysis
Related MCP Servers
AlicenseAqualityBmaintenanceMCP server for secure, just-in-time secret retrieval from 1claw vault and malicious content inspection, enabling AI agents to access secrets and security analysis.1560 npm4MIT- AlicenseAqualityBmaintenanceMCP server for creating and managing SOPS-encrypted secret files using age encryption, enabling AI agents to generate and manage secrets without ever seeing plaintext values.1256 PyPIApache 2.0
- AlicenseNot gradedqualityDmaintenanceSecrets management MCP server that injects credentials into API requests for AI agents, enforcing policies and logging all activity without exposing raw keys.109 npm30MIT

wundervaultofficial
AlicenseAqualityBmaintenanceMCP server for Wundervault zero-knowledge secret management. Lets AI Agents use secrets via the Model Context Protocol — secrets are decrypted using a broker that runs on your local computer on a protected account that your agent cannot access the plaintext.11893 npm2AGPL 3.0