auth-vault
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 "Install 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-vaultlog 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/auth-vault
🧩 Branch template — czysta wersja do klonowania i adaptacji.
Brak testów specyficznych dla Q-ekosystemu, brak danych wrażliwych.
Własne serwisy konfigurujesz przezadd_service— wystarczą selektory CSS.
MCP server for secure credential management, browser-based login automation, and TOTP/2FA auto-solving.
Status: active | License: MIT | Version: 0.1.0Overview
Auth Vault stores encrypted credentials and secrets (AES-256-GCM), automates browser login flows via Playwright, and auto-solves TOTP-based 2FA challenges. 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: playwright-sse-mcp-server
Features
Encrypted vault — credentials and secrets stored with AES-256-GCM
Browser automation — Playwright-based login with form filling
TOTP/2FA auto-solve — RFC 6238 implementation, generates and submits 2FA codes
QR code support — generate QR for Google Authenticator setup
Secrets management — API keys, bearer tokens, access/refresh tokens
Tailscale-only access — binds to Tailscale IP by default, blocks external traffic
Two service modes — STDIO (MCP standard) and SSE (HTTP for persistent connections)
Quick Start
Prerequisites
Node.js 22+
Playwright Chromium (installed via
postinstall)Tailscale (recommended for SSE mode)
Setup
# Install dependencies
npm install
# Build TypeScript
npm run build
# Configure environment
cp .env.example .env
# Edit .env: set VAULT_ENCRYPTION_KEY (64 hex chars) or leave empty for auto-generatedConfiguration
All 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) |
|
| Logging level: debug, info, warn, error |
Usage
STDIO Mode (default for MCP clients)
node dist/index.jsSSE Mode (HTTP server for persistent connections)
# Set AUTH_SSE_PORT=5501 in .env, then:
node dist/index.jsWeb UI Dashboard
node dist/web/server.js
# Dashboard at http://<tailscale-ip>:5500/CLI Commands
npm run add-creds # Add credentials interactively
npm run add-secret # Add a secret interactively
npm run list-creds # List stored credentials
npm run list-secrets # List stored secrets
npm run get-creds # Get credential detailsSystemd Services
# MCP SSE server (port 5501)
systemctl status mcp-auth-vault
# Web UI dashboard (port 5500)
systemctl status mcp-auth-vault-webBoth services restart automatically on failure and enable at boot.
Security
AES-256-GCM encryption for all stored credentials and secrets
Tailscope-restricted — SSE mode blocks non-Tailscale connections
Encryption key persisted in
.env— if lost, data cannot be recoveredHeadless browser — no visible UI during automated logins
Project Structure
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
├── secrets/
│ ├── manager.ts # Encrypted secrets store
│ └── types.ts # Secret type definitions
├── 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
│ ├── secrets.ts # MCP tool definitions for secrets
│ ├── services.ts # MCP tool definitions for services
│ └── login.ts # MCP tool definitions for login
└── cli/
├── add-credentials.ts
└── add-secret.tsTech Stack
Runtime: Node.js 24, 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
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceAn MCP server for browser automation that allows AI to perform web tasks using Playwright through direct commands, reusable YAML shortcuts, or custom scripts. It features secure environment variable management and guided automation creation to build robust, repeatable browser workflows.Last updated40MIT
- Flicense-quality-maintenanceAn MCP server that provides browser automation capabilities via Playwright using Server-Sent Events (SSE). It enables clients to perform web operations and scraping through a containerized Docker environment.Last updated
- AlicenseAqualityCmaintenanceA high-performance browser automation MCP server that provides AI agents with a fast, persistent Chromium instance via Playwright. It features reference-based element interaction, snapshot diffing, and manual handoff capabilities to handle complex tasks like CAPTCHAs.Last updated612632MIT
- Flicense-qualityCmaintenanceMCP server for grocery-related web automation using Playwright, enabling AI assistants to interact with grocery websites.Last updated
Related MCP Connectors
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
Hash passwords with bcrypt and issue/verify JWT session tokens over A2A + MCP.
Personal assistant MCP server with search, execute, packages, jobs, secrets, and integrations.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/borysttk/auth-vault-template'
If you have feedback or need assistance with the MCP directory API, please join our Discord server