AgentVault MCP Server
Related Servers
Alternatives to AgentVault MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding tools to securely manage secrets via MCP tools for vault operations, diagnostics, and cloud sync, ensuring real keys never enter the LLM context.16MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to securely manage API keys and secrets via the MCP protocol, with encrypted storage at rest and a simple CLI and Python SDK.1MIT

Kova Mind MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI memory persistence and secure credential management via vault tools for MCP-compatible clients like Claude Desktop, Cursor, and VS Code.1214 npmMIT- AlicenseNot gradedqualityCmaintenanceMCP server enabling AI agents to use secrets (API keys, tokens) via encrypted vault, executing HTTP/shell/SSH actions server-side while never exposing secret values to the AI.MIT
- AlicenseAqualityAmaintenanceMCP server for Vaultwarden/Bitwarden vault management. Enables AI agents to securely create, search, read, and update vault items via the official Bitwarden CLI, with safe-by-default redaction and support for both stdio and SSE transports.53548 npm17MIT
- FlicenseAqualityCmaintenanceA local-first secrets vault for MCP clients that lets AI assistants use secrets by injecting them into child processes, without the plaintext ever entering the model's context.5-
TDQS
Scored across 7 tools
While av_get_secret and av_resolve both retrieve secret data, av_get_secret returns the full field map while av_resolve targets a specific field via reference. av_put_secret and av_rotate_secret are similarly distinct (create/update vs. replace). The purposes are mostly clear, though the boundary between get/resolve and put/rotate could momentarily confuse.
The av_ prefix is consistent, and most tools follow av_<verb>_<noun> (create_vault, put_secret, get_secret, list_secrets, issue_token, rotate_secret). The verb style is uniform, but 'av_resolve' lacks an explicit object, a minor deviation.
With 7 tools, the set is well-scoped for a vault management server, fitting the typical 3-15 range. Each tool addresses a distinct operation without redundancy or bloat.
The server covers the core lifecycle of vaults and secrets: create, read, update, list, rotate, and token issuance. However, there is no delete operation for vaults or secrets, which could be considered a gap for complete lifecycle management, though it may be intentional for security.