Skip to content
mcpvault logo

mcpvault

Stores many accounts per service in one encrypted local vault and switches the active one for AI agents over MCP.

Maintained

At a glanceswept Oct 18, 2026

26 linking domains

Emerging

For
Developers using AI coding agents like Claude Desktop or Cursor who juggle multiple accounts per service
Activity
Maintainedsite updated 5 months ago
Runs as
CLI
Used for
  • switch between personal and work Supabase accounts mid-conversation
  • keep API tokens out of agent MCP config files
  • log which account an agent used for each request
Worth knowingcomputed from what we read · each with its source
Your datawhat they publish, each line with its page · read Oct 22, 2026

    These are mcpvault's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.

    Alternatives in Securityby use, among tools still maintained

    Figure and bar: visits/mo, estimate · year: online since

    Compare mcpvault with

    Pick up to two.

    All 10 alternatives to mcpvault →

    All Security tools →

    Not it? Say what you need

    beta

    Three tools from the Atlas for the job you describe, each with what fits and what does not.

    From people who use itnot part of the reading

    No notes yet. What do you use mcpvault for?

    Sign in to leave a note
    Questions this page answers
    • What is mcpvault?

      Stores many accounts per service in one encrypted local vault and switches the active one for AI agents over MCP. It is listed in the Atlas under Security, Developer tools.

    • Who is mcpvault for?

      Developers using AI coding agents like Claude Desktop or Cursor who juggle multiple accounts per service

    • Do people use mcpvault?

      Emerging.

    • Is mcpvault still maintained?

      Maintained: site updated 5 months ago.

    • What are alternatives to mcpvault?

      In Security, by use: Lumo by Proton, Hekkova, SecureNow, Penny, Haas, Yungle.

    How we read a tool

    No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

    • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
    • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
    • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
    • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

    How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

    How we read every tool → · By INITE Atlas Desk