Share secrets with AI agents

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 .env file 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

Every option encrypts before anything goes over the network. There's no hosted endpoint that accepts plaintext.

MCP server

The MCP server runs locally over stdio, so plaintext and keys stay on the machine running the agent. npx fetches it straight from evergist.com. There's nothing to install first.

Claude Code

claude mcp add evergist -- npx -y https://evergist.com/cli/evergist.tgz mcp

Codex CLI

codex mcp add evergist -- npx -y https://evergist.com/cli/evergist.tgz mcp

Claude Desktop, Cursor, Windsurf, and other clients use the same JSON:

{
  "mcpServers": {
    "evergist": {
      "command": "npx",
      "args": ["-y", "https://evergist.com/cli/evergist.tgz", "mcp"]
    }
  }
}

Tools

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

# Share a file, readable once, gone in an hour
npx -y https://evergist.com/cli/evergist.tgz create .env --views 1 --expires 1h

# Pipe text in, add a generated password, get JSON back
echo "root password: correct-horse" | npx -y https://evergist.com/cli/evergist.tgz create -g --json

# Read a gist (uses one view)
npx -y https://evergist.com/cli/evergist.tgz read "https://evergist.com/g/<id>#<key>"

# Check it without using a view, or delete it
npx -y https://evergist.com/cli/evergist.tgz status "https://evergist.com/g/<id>#<key>"
npx -y https://evergist.com/cli/evergist.tgz 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.

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);

Why there's no hosted MCP endpoint

A remote MCP server would receive your text before encrypting it. That would make "we can't read it" a promise instead of a fact. So the MCP server runs on your machine and talks to the API with ciphertext only. If an agent probes https://evergist.com/mcp, it gets a JSON message pointing here.

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: 1 for 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.
• Keep the delete token private. It deletes the gist without needing the link.