mykeep

Secrets for AI agents.

Give autonomy.
Keep control.

A secrets vault for your agents, a password manager for you — used, never seen.

Get mykeep — free Read the agent docs

Secrets never leave your devices Open source — publishing soon No account · you approve every use

iOS Android macOS Windows Linux Chrome Safari Any AI agent · REST & MCP

How it works

You hand over a decision, never a key.

The secret gets used on your device and never comes back — not to the agent, not to the cloud.

Stays on your devices

Sealed under a key only your devices hold — at rest, and when synced between them. The relay never gets that key and keeps nothing it passes through.

You approve every use

The agent stops and waits. You approve on your device — face or fingerprint. Once, or for ten minutes. Kill it anytime.

Any agent

Claude Code, Cursor, ChatGPT, your scripts. Plain REST or MCP. No SDK.

Straight about the edges: browser fill is end-to-end encrypted, and device-to-device sync stores only ciphertext the relay can't open. Your agent's memory and the API responses we broker for it cross the relay over TLS — never stored, but not end-to-end sealed yet. Your raw secrets never reach the agent at all: they're injected on your device.

One vault

Your whole secret life — and your agent's memory.

Right now your secrets are scattered — .env, a password manager, an authenticator app. mykeep puts them behind one unlock. Bring them over from 1Password, Bitwarden, or Chrome.

API keyssecret used by reference — the token never enters the agent you approve

Loginssecret autofilled on desktop and mobile you approve

Passkeyssecret phishing-proof. private key sealed on-device you approve

One-time codes2FA / OTP TOTP on-device. ditch the authenticator app you approve

Memorycontext recalled before your agent answers. updated as it learns on your devices

Connect your agent

Connect in a minute.

Two ways in — an MCP server or plain HTTPS. Both take one connect code from the app; no SDK, nothing to build.

Open the app → Connect.

Copy your connect code — your agent uses it to ask for access.

mk_obvious-tumble-bridge_••••••

Add it — MCP or REST.

Drop it in the MCP config (below), or send it as a bearer token over plain HTTPS. Your agent asks to join, you approve it once on your device — then every secret use is approved too.

MCP, one line

Drop the config in and you get memory_recall, vault_fetch, and more as tools. Works in Claude Code, Cursor, Cline, Codex.

Or just HTTPS

No MCP? Any agent that can call a URL works — send the code as Authorization: Bearer. The whole manual: GET www.mykeep.ai/connect.

By reference, never by value

The agent acts with the key — and never sees it.

It asks; mykeep makes the call. A prompt injection can't leak a key the agent never had.

act-as-me.js
// the agent acts as you — the GitHub token never enters the agent
const r = await fetch("https://www.mykeep.ai/v1/vault/fetch", {
  method: "POST",
  headers: { Authorization: `Bearer ${token}` },
  body: JSON.stringify({
    credential: "github",           // by name, not value
    method: "POST",
    url: "https://api.github.com/repos/acme/app/releases",
    body: "{ \"tag_name\": \"v1.2.0\" }",
  }),
});
// → you approve on your device → key injected on-device → you get the response

Plain REST or MCP

HTTPS + a bearer token. GET /connect is the whole manual. MCP optional.

Memory, too

recall before answering, retain after. Embedded on-device.

You stay in the loop

Writes need approval. Revoke anytime.

Live manual: www.mykeep.ai/connect

Pricing

Self-host free. Or let us host it.

Run the gateway yourself, free forever. Or let us host it — free in early access, founder pricing locked in when paid plans land.

Early access

Hosted

We run the gateway, you keep the keys

$0free in early access

Zero setup — paste one connect code and go
All your devices, synced end-to-end encrypted
Face / fingerprint approval on every use — never gated
Unlimited use & unlimited memories
Founder pricing locked in when managed plans launch

Get started — free

Open source — soon

Self-host

Run the gateway yourself

$0free, forever

Core + gateway licensed Apache-2.0 — published in full, soon
Your own Cloudflare account — no vendor, no lock-in
Audit every line of the security-critical code
The escape hatch that keeps hosted honest

Get notified when it's public

Teams — shared vaults, roles, off-boarding — is exploratory; tell us if you'd want it.

mykeep ♥ open source

The hard parts are out in the open.

Security you can't read isn't security. The security core and gateway are licensed Apache-2.0 and will be published in full — every line that touches your secrets, there to read, run and fork.

Coresecurity crypto envelope, SSRF/egress hardening, capability model — proves the secret never leaves your device Apache-2.0

Gatewayrelay Cloudflare Worker relay — holds no keys; sync stores only ciphertext it can't open, relayed frames aren't kept, and the only plaintext it stores is a push token to wake your phone Apache-2.0

Want the repo the day it lands? Tell us and we'll send the link.

Your keys. Your call.

Give your agent the keys. Keep the keys.

Free on every device. Two steps to live. Nothing leaves your devices.