This MCP server securely manages credentials/secrets and automates authenticated browser workflows, with TOTP/2FA, service templates, health checks, and documented SSH/audit/REST/Web UI features.
Store, get, list, filter, and delete AES-256-GCM-encrypted credentials; optionally include passwords.
Store, retrieve, list, filter, and delete encrypted secrets (API keys, tokens, private keys, generic) with scopes/expiry metadata.
Generate Authenticator QR codes, test TOTP secrets/codes, and solve 2FA challenges during browser logins.
Manage service login templates: list, inspect, and add custom services with login URLs/selectors.
Control Playwright browser sessions: launch, navigate, check, close, and list sessions.
Automate logins: fill forms, detect/solve CAPTCHA, click submit, detect/solve 2FA, and check session/login status.
Run health/testing utilities for vault, sessions, TOTP, selectors, secret expiry, CDP connectivity, and service reachability.
Per README, also use REST/Web UI for SSH key vault, discovery, audit logging, health monitoring, and systemd services.
Provides login automation for Google services, including form filling and credential management.
Supports TOTP/2FA auto-solving and QR code generation for Google Authenticator setup.
Click 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., "@auth-vault log into my Google account"
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.
MCP server for secure credential management, browser-based login automation, SSH key vault, TOTP/2FA auto-solving, and audit logging.
Status: active | License: MIT | Version: 0.2.0Auth Vault stores encrypted credentials, secrets, and SSH keys (AES-256-GCM), automates browser login flows via Playwright, auto-solves TOTP-based 2FA challenges, and tracks sensitive actions via an audit log. It provides both an MCP interface (for AI clients) and a Web UI dashboard (for manual management).
Interface | Port | URL |
Web UI Dashboard |
|
|
MCP SSE |
|
|
MCP Health |
|
|
Related MCP server: @aiwerk/mcp-server-vault
Encrypted vault — credentials, secrets, and SSH keys stored with AES-256-GCM
SSH Key Vault — generate, store, retrieve, and export SSH keys (Ed25519, RSA-2048/4096)
SSH Config generation — export SSH config fragments and key files
Browser automation — Playwright-based login with form filling
CAPTCHA detection — automatic detection of CAPTCHA challenges during login
Trusted devices — device fingerprinting with trusted device management
TOTP/2FA auto-solve — RFC 6238 implementation, generates and submits 2FA codes
TOTP rotation detection — suggests code refresh when window is near expiry
QR code support — generate QR for Google Authenticator setup
Secrets management — API keys, bearer tokens, access/refresh tokens
Audit logging — JSONL audit log with auto-rotation for sensitive actions
Vault health monitoring — periodic integrity checks every 12 hours
Discovery API — metadata overview of all vault contents without decryption
Tailscale-only access — binds to Tailscale IP by default, blocks external traffic
Two service modes — STDIO (MCP standard) and SSE (HTTP for persistent connections)
Node.js 22+
Playwright Chromium (installed via postinstall)
Tailscale (recommended for SSE mode)
# Install dependencies
pnpm install
# Build TypeScript
pnpm run build
# Configure environment
cp .env.example .env
# Edit .env: set VAULT_ENCRYPTION_KEY (64 hex chars) or leave empty for auto-generatedAll configuration via .env file or environment variables:
Variable | Default | Description |
|
| Storage directory for encrypted vault files |
|
| AES-256 key (64 hex chars, persist for data survival) |
| — | Enable SSE mode on given port (empty = STDIO mode) |
| auto (Tailscale) | Explicit bind address for SSE mode |
|
| Run Playwright in headless mode |
|
| Browser operation timeout (ms) |
|
| Audit log rotation threshold (10 MB) |
|
| Logging level: debug, info, warn, error |
node dist/index.js# Set AUTH_SSE_PORT=5501 in .env, then:
node dist/index.jsnode dist/web/server.js
# Dashboard at http://<tailscale-ip>:5600/pnpm run add-creds # Add credentials interactively
pnpm run list-creds # List stored credentials (JSON)
pnpm run get-creds # Get credential details (JSON)pnpm run add-secret # Add a secret interactively
pnpm run list-secrets # List stored secrets (JSON)pnpm run add-ssh-key # Add existing SSH key interactively
pnpm run generate-ssh-key # Generate new SSH key pair and store
pnpm run list-ssh-keys # List stored SSH keys (JSON)
pnpm run get-ssh-key # Get SSH key details (JSON)Method | Path | Description |
|
| List all credentials (metadata only) |
|
| List all credentials (with passwords) |
|
| Get credential details (password hidden by default) |
|
| Create a new credential |
|
| Update a credential |
|
| Delete a credential |
|
| List trusted devices |
|
| Add a trusted device |
|
| Remove a trusted device |
|
| Audit log entries for a credential |
|
| Shortcut to add a trusted device |
Method | Path | Description |
|
| List all secrets (metadata only) |
|
| Create a new secret |
|
| Delete a secret |
|
| Get decrypted secret value |
Method | Path | Description |
|
| List all SSH keys |
|
| Get SSH key details (private key hidden by default) |
|
| Store an SSH key |
|
| Update an SSH key |
|
| Delete an SSH key |
|
| Generate and store a new SSH key pair |
|
| Get SSH config fragment |
|
| Extract public key from private key |
|
| Generate new key pair for existing entry |
|
| Get public key in plain text |
Method | Path | Description |
|
| Generate a new TOTP secret with QR code |
|
| Verify a TOTP code (returns |
|
| Attach a TOTP secret to a credential |
|
| Replace TOTP secret on an existing credential |
|
| Get current + next TOTP codes |
|
| Get TOTP rotation status |
Method | Path | Description |
|
| Start automated login (returns |
|
| Submit 2FA code during login |
|
| Check login session status |
|
| Cancel an active login session |
|
| List active login sessions |
|
| Get recovery options (TOTP recovery, backup codes) |
Method | Path | Description |
|
| Metadata overview of all vault entries (no decryption) |
|
| Aggregate statistics (counts by type, TOTP status) |
|
| Recent activity (last 10 audit entries + updated credentials) |
Method | Path | Description |
|
| List audit log entries (newest first) |
|
| Manually log an action |
|
| Activity summary for last 24 hours |
|
| Services with audit activity |
Method | Path | Description |
|
| Service health check |
|
| Vault file integrity validation |
|
| Combined health (integrity + storage stats + audit stats) |
# MCP SSE server (port 5501)
systemctl status mcp-auth-vault
# Web UI dashboard (port 5600)
systemctl status mcp-auth-vault-webBoth services restart automatically on failure and enable at boot.
AES-256-GCM encryption for all stored credentials, secrets, and SSH keys
Tailscale-restricted — Web UI and SSE mode block non-Tailscale connections
Encryption key persisted in .env — if lost, data cannot be recovered
Headless browser — no visible UI during automated logins
Audit logging — all sensitive actions logged to append-only JSONL file
Vault integrity — periodic validation every 12 hours
Private key material — SSH private keys encrypted at rest, never exposed in list endpoints
src/
├── index.ts # MCP server entry (STDIO + SSE)
├── config.ts # Zod-validated configuration
├── credentials/
│ ├── totp.ts # TOTP (RFC 6238) implementation
│ ├── qr.ts # QR code generation + TOTP secret generator
│ ├── vault.ts # Encrypted credential store
│ └── types.ts # Credential type definitions
├── ssh/
│ ├── vault.ts # Encrypted SSH key store
│ ├── generator.ts # SSH key pair generation (Ed25519, RSA)
│ └── types.ts # SSH key type definitions
├── secrets/
│ ├── manager.ts # Encrypted secrets store
│ └── types.ts # Secret type definitions
├── audit/
│ ├── log.ts # JSONL audit log with auto-rotation
│ └── health.ts # Vault integrity check module
├── authVault/
│ └── fingerprint.ts # Trusted device fingerprinting
├── browser/
│ └── manager.ts # Playwright session management
├── services/
│ └── definitions.ts # Login templates (Google, etc.)
├── web/
│ ├── server.ts # Web UI HTTP server + REST API
│ └── dashboard.ts # HTML dashboard template
├── tools/
│ ├── credentials.ts # MCP tool definitions for credentials
│ ├── ssh.ts # MCP tool definitions for SSH keys
│ ├── secrets.ts # MCP tool definitions for secrets
│ ├── services.ts # MCP tool definitions for services
│ ├── login.ts # MCP tool definitions for login
│ ├── audit.ts # MCP tool definitions for audit/health
│ └── totp.ts # MCP tool definitions for TOTP
└── cli/
├── add-credentials.ts
├── add-secret.ts
├── add-ssh-key.ts
├── generate-ssh-key.ts
├── get-ssh-key.ts
├── list-ssh-keys.ts
├── list-credentials.ts
├── list-secrets.ts
└── get-credential.tsRuntime: Node.js 22+, TypeScript ESM
MCP: @modelcontextprotocol/sdk v1.16
Encryption: Node.js crypto (AES-256-GCM)
Browser: Playwright (Chromium)
Config: Zod validation
UI: Vanilla JS (no framework)
QR: qrcode npm package
MIT
Register a custom service login template at runtime
Inputs: id (required), label (required), loginUrl (required), usernameSelector (required), +4 more.
Close a browser session
Inputs: sessionId (required).
Launch a new browser session for logging into a service
Inputs: service (required), headless.
Check if a browser session is still active and optionally verify login status
Inputs: sessionId (required), verifyLogin.
Click the submit button on the login form (useful after captcha solving)
Inputs: sessionId (required), service (required).
Permanently delete stored credentials by ID
Inputs: id (required).
Permanently delete a stored secret by ID
Inputs: id (required).
Check the current page for a 2FA code challenge
Inputs: sessionId (required), service.
Check the current page for captcha challenges
Inputs: sessionId (required).
Generate a Google Authenticator QR code for a stored credential's TOTP secret
Inputs: credentialId (required).
Retrieve stored credentials by ID. Returns decrypted username and password.
Inputs: id (required), includePassword.
Get all credentials for a specific service
Inputs: service (required), includePasswords.
Retrieve a stored secret by ID (returns decrypted value)
Inputs: id (required).
Get detailed login template for a specific service
Inputs: service (required).
List stored credentials, optionally filtered by service
Inputs: service.
List stored secrets, optionally filtered by service or kind
Inputs: service, kind.
List all supported services with their login templates
Inputs: no named parameters.
List all active browser sessions
Inputs: no named parameters.
Automate login to a service using stored credentials. Launches browser, fills form, handles captcha.
Inputs: sessionId (required), credentialId (required), solveCaptcha.
Generate a TOTP code from the stored secret and fill it into the 2FA input field
Inputs: sessionId (required), credentialId (required), service.
Solve a detected captcha on the current page using configured captcha service
Inputs: sessionId (required), apiKey.
Store login credentials for a service securely with AES-256-GCM encryption
Inputs: service (required), label (required), username (required), password (required), +2 more.
Store an API key, access token, or other secret encrypted with AES-256-GCM
Inputs: label (required), kind (required), service (required), value (required), +5 more.
Test all registered service templates — check if login pages are reachable
Inputs: no named parameters.
Test Chrome DevTools Protocol connectivity — verify CDP endpoint is reachable
Inputs: port, host.
Test if credentials exist in vault and validate their structure (returns non-sensitive info only)
Inputs: id, service.
Check all secrets for expiration — identifies expired, expiring soon, or valid secrets
Inputs: warningDays, service.
Test if a CSS selector works on a service's login page (launches browser, checks selector matches)
Inputs: service (required), selectorType, selectorOverride.
Check if browser sessions are alive and can interact with pages
Inputs: sessionId.
Verify TOTP secret by generating a current code and optionally checking against expected value
Inputs: credentialId (required), expectedCode.
Comprehensive health check of the auth-vault system — encryption, storage, services, sessions
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 32 tools
Most tools have distinct purposes (credential management, browser automation, captcha/2FA, testing), but some overlap exists between test_* tools and session checks (e.g., test_session_integrity vs check_session), causing minor confusion.
All tool names follow a consistent verb_noun pattern using snake_case, with clear prefixes (browser_, test_, get_, store_, etc.), making the set predictable and easy to navigate.
With 32 tools, the server is over-scoped. Many testing and health tools could be consolidated, and the core authentication/secret operations could be separated into a smaller, focused set.
Core operations for credentials and secrets are present (store, retrieve, delete), but missing update functionality means agents cannot modify existing entries, creating a workflow gap.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
