When an agent should use Evergist
Reach for Evergist whenever an agent needs to pass text that shouldn't live forever in a transcript, a ticket, or a chat log:
- An API key, database password, or token that a person or another agent needs once
- A
.envfile or config for a teammate's machine - Logs or stack traces that contain customer data
- A handoff note between agents running in different sandboxes
- Anything the user asks to "send privately" or "share securely"
The agent gets a link like https://evergist.com/g/7mQx2Ld9KpTa#Zm9v.... Whoever has the full link can read the note until it expires or runs out of views. Nobody else can, including Evergist.
Pick an integration
| Integration | Best for | Needs |
|---|---|---|
| ChatGPT plugin | Browser-encrypted ordinary notes inside ChatGPT | ChatGPT with plugin access |
| MCP server | Claude, Cursor, Codex, and other MCP clients | Node.js 20+ |
| SKILL.md | Agents that load skills or read instructions from URLs | A shell with Node.js 20+ |
| CLI | Scripts, CI jobs, terminals | Node.js 20+ |
| JavaScript module | Deno, Bun, browsers, Workers | Web Crypto |
| REST API | Any language | Your own AES-GCM and HKDF |
Every option encrypts before anything goes over the network. There's no hosted endpoint that accepts plaintext.
This page is the setup reference. For the rules and handoff patterns to give an agent, read How AI agents can share secrets.
MCP server
The MCP server runs locally over stdio and needs no account. It encrypts and decrypts on the machine running the agent, so Evergist only receives ciphertext. The agent itself does see the text, as a tool argument on create and a tool result on read. npx fetches the evergist package from npm, so there's nothing to install first. If you'd rather not go through the npm registry, evergist.com serves the same package: replace evergist with https://evergist.com/cli/evergist.tgz in any command below.
Claude Code
claude mcp add evergist -- npx -y evergist mcp
Codex CLI
codex mcp add evergist -- npx -y evergist mcp
Claude Desktop, Cursor, Windsurf, and other clients use the same JSON:
{
"mcpServers": {
"evergist": {
"command": "npx",
"args": ["-y", "evergist", "mcp"]
}
}
}
Tools
The MCP tools, the CLI, and the API call a note a gist. A gist is a note.
| Tool | What it does | Uses a view? |
|---|---|---|
create_gist |
Encrypts text and returns url, expiresAt, maxViews, deleteToken. Options: expires_in (1 minute to 30 days, for example 10m, 1h, 30d), max_views (1 to 1000), password, generate_password |
No |
read_gist |
Decrypts a gist from its full url (plus password if set) |
Yes |
gist_status |
Shows expiry, views left, and whether a password is needed | No |
delete_gist |
Deletes by url, or by id plus delete_token |
No |
Both create_gist and read_gist pass the text through the model. create_gist takes it as an argument and read_gist returns it. To keep a value out of the agent's context, use the command line with files. The MCP server walkthrough shows what the agent sees in each call.
Skill
The skill file teaches an agent when and how to use Evergist with the CLI. Agents can read it directly from evergist.com/SKILL.md. To install it for Claude Code:
mkdir -p ~/.claude/skills/evergist
curl -fsSL https://evergist.com/SKILL.md -o ~/.claude/skills/evergist/SKILL.md
Other agents that support skills or AGENTS.md-style instructions can use the same file. You can also paste this line into an agent's instructions:
To share secrets or private text, use Evergist. Read https://evergist.com/SKILL.md first.
Command line
The CLI is the same evergist npm package. Run it with npx -y evergist, or install it once with npm install -g evergist and use evergist directly.
# Share a file, readable once, gone in an hour
npx -y evergist create .env --views 1 --expires 1h
# Share the clipboard (macOS), add a generated password, get JSON back
pbpaste | npx -y evergist create -g --json
# Read a gist into a file (uses one view, keeps the text out of the agent's output)
npx -y evergist read "https://evergist.com/g/<id>#<key>" > .env.local
# Check it without using a view, or delete it
npx -y evergist status "https://evergist.com/g/<id>#<key>"
npx -y evergist delete "https://evergist.com/g/<id>#<key>"
The CLI is a single file with no dependencies. If you'd rather pin it, download evergist.mjs, read it, and run it with node evergist.mjs.
Pass secrets as a file or on stdin. A value typed into the command itself, as in echo "the-password" | ..., stays in shell history. Share a secret from the command line covers files, the clipboard, and generated passwords.
| Option | Meaning |
|---|---|
-e, --expires |
10m, 1h, 1d, 7d, 30d, or seconds. From 1 minute to 30 days. Default 1d |
-v, --views |
Delete after this many reads, 1 to 1000. Default: no limit |
-p, --password |
Add a password. EVERGIST_PASSWORD works too and keeps it out of shell history |
-g, --generate-password |
Generate a strong password and print it |
--json |
Machine-readable output |
--base-url |
Another Evergist server. EVERGIST_URL works too |
JavaScript module
Runtimes that can import from a URL can use the client library directly. It runs anywhere Web Crypto does.
import { createGist, readGist } from "https://evergist.com/sdk/evergist.js";
const gist = await createGist({ text: "deploy key: ...", maxViews: 1, expiresIn: 3600 });
console.log(gist.url); // share this
const { text } = await readGist(gist.url);
Hosted ChatGPT plugin
The hosted endpoint at https://evergist.com/mcp opens an embedded editor. It accepts expiry and view preferences, never note text, decryption keys, or passwords. Users paste ordinary notes and links directly into the widget, which encrypts and decrypts in the browser using the same core library as the website. Actions require a user click, and note contents and links are not returned to the chat model.
The ChatGPT plugin supports ordinary notes and drafts. Passwords, API keys, authentication secrets, payment card data, health records, and government identifiers are outside its scope. It cannot open or delete password-protected notes. See the ChatGPT guide for setup and limits.
The local stdio MCP server above has a separate tool set. It encrypts on your machine and accepts text as tool arguments.
Good habits for agents
- Share the whole link. The key is the part after
#. Without it the note can't be opened. - Use
max_views: 1for credentials. The first read burns the note, so a leaked link is useless afterwards. - Keep expiry short. An hour or a day is plenty for most handoffs.
- Send passwords separately. If you add one, deliver it through a different channel than the link.
- Don't echo the secret back. After creating a gist, report the link, not the contents.
- Know what the model sees. An agent that reads a note through the MCP tool, or prints a file, does see the value. Redirecting
evergist readto a file keeps it out of the tool output. - Keep the delete token private. It deletes the gist without needing the link.
Guides
- How AI agents can share secrets: rules and handoff patterns for agent to person, person to agent, and agent to agent.
- Give Claude Code an API key without pasting it: get a key into a project file without it entering the chat.
- An MCP server for sharing secrets: what each tool call sends and what the model sees.
- Share a secret from the command line: files, stdin, the clipboard, and JSON output.
- Send a secret from CI to a person: a GitHub Actions job that hands a generated credential to someone.
- One-time links or a vault for AI agents: when a handoff link fits and when the agent needs a secrets manager.