---
name: login-vault
description: Scoped login vault for AI agents. Your bot signs in to sites without ever seeing the password: you save each login encrypted with a scope (which sites, which HTTP methods, a daily cap), hand each bot its own key limited to the logins you granted, and the server fills the password, keeps the cookies and returns an opaque session id. Every use is in the audit log; revoke a bot in one call.
---
# Login Vault

Works with Claude, Codex, ChatGPT, Grok Bot. Bring your own model.

Connect the MCP server at https://vault.cloudforbots.com/mcp (Claude Code: `claude mcp add --transport http login-vault https://vault.cloudforbots.com/mcp`).

## When to use
- `save_login`: Owner only (your Pro key, never a bot key). Store one login sealed with AES-256-GCM, with a scope: allowed hosts, allowed methods, a daily session cap and session TTL. Run it from your own machine, not inside the bot. The password and TOTP secret are never returned by any tool. Free watch-only stores nothing and logs would_use_vault.
- `list_logins`: List saved logins (name, domain, scope, sessions today; never secrets). With your owner key it also lists bot keys. A bot key only sees the logins it was granted.
- `delete_login`: Owner only. Delete a saved login, end its open sessions and remove it from every bot key.
- `create_bot_key`: Owner only. Make a per-bot key (vk_...) that can only open sessions on the logins you name. Shown once; we store only its hash. Revoke any time with revoke_bot_key.
- `revoke_bot_key`: Owner only. Revoke a bot key right away and end every session it opened.
- `open_session`: Sign in with a saved login without seeing it. The server fills {{username}}, {{password}} and {{totp}} into your form, posts it to url (https, inside the login's allowed hosts), keeps the cookies encrypted, and returns an opaque session id. Checked against the login's scope and daily cap; logged to the audit log. If the site shows a CAPTCHA or new-device check, the reply suggests next_step request_human (Human Handoff relay). Free watch-only logs would_use_vault and signs in nowhere.
- `session_fetch`: Make one request inside an open session. url must be https inside the login's allowed hosts and the method must be in its allowed methods. The password, TOTP secret and codes are redacted from the reply; cookies never leave the vault.
- `end_session`: End a session now and wipe its cookies.
- `audit_log`: Owner only. The last uses of your vault: who (bot label), which login, which domain, what happened. Never contains secrets.
- `weekly_report`: Plain-English summary of the last 7 days: where your bots needed to sign in (by domain), sessions opened, blocked attempts, by bot. Read-only. Needs a key.

## Rules
1. Before calling, state in one line what you understood the user wants.
2. Report the tool's `job` and `outcome` lines to the user.
3. If you get `free_limit_reached`, tell the user the free tier is 500/day and share the $9/month link: https://pay.instaloops.com/b/4gM6oHeG42sv2mHgt983C3E