CLI, MCP, and agentic workflows

Secret handoffs for humans, scripts, and agents.

Shhhs gives humans a web app, operators a CLI, teams a scoped API, and agents a local MCP adapter. The job is the same everywhere: create a short-lived encrypted handoff without leaking plaintext into the wrong system.

CLI for operators, CI, and scripts

The shhhs CLI is built for shell-driven workflows: create encrypted pushes, request links, burns, vault lookups, event delivery checks, account checks, and package inspection from scripts or terminals.

  • curl installer for macOS/Linux
  • Hidden prompt for shhhs push text
  • Explicit shhhs update, no background updater

MCP for local agent runtimes

shhhs-mcp runs as a local stdio adapter. It exposes tools for encrypted pushes, request links, submissions, and burns while keeping account material on the user's machine.

  • setup-skill for repo or user agents
  • Local encryption before upload
  • Do not expose it as an unauthenticated remote MCP server

Agentic secret sharing

Instead of pasting credentials into prompts, one agent can create a temporary encrypted link or request link and another agent can submit through that controlled channel.

  • Agent-to-agent request intake
  • No plaintext in transcripts
  • TTL, view limits, opening codes, and burn

Team API under Cloudflare API Shield

Team API keys are scoped separately from human login. API v1 is described by OpenAPI and protected by Cloudflare API Shield schema validation before requests reach the Worker.

  • Scoped API keys
  • OpenAPI served at /openapi.json
  • Schema validation blocks invalid /api/v1 payloads

Enterprise automation path

Enterprise extends the same model into customer admin, Microsoft and Google lifecycle hooks, browser extension enrollment, and an outbound on-prem agent for internal IAM events.

  • Customer Enterprise Admin
  • Microsoft and Google integration planning
  • On-prem agent with signed metadata events

The boundary that does not move

Automation does not mean Shhhs reads secrets. Prompts, logs, audit, support, event notifications, and connector logs should contain metadata and ciphertext only.

  • No AI processing on secrets
  • No plaintext operational logs
  • No secret recovery promise

Packages

Free

Anonymous text-only sharing for occasional secrets.

USD 0
  • Text secrets
  • Short TTL
  • View limits
  • No opening codes

10 Secret Bundle

10 secrets / 3 months for paid, occasional work.

USD 29
  • 10 real uses
  • Files
  • Opening codes
  • Request links

7-day Project Pass

A short project window for clients, vendors, and urgent handoffs.

USD 49
  • 7-day access
  • Files
  • Request intake
  • Short TTLs

Pro Monthly

Better value for regular secure sharing.

USD 12/mo
  • 1,000 pushes/month
  • Files
  • Opening codes
  • Console

Team Monthly

A base workspace plus admin seats for teams and API-driven workflows.

USD 49/mo workspace + USD 9/seat
  • Base workspace
  • Admin seats
  • API keys
  • Request intake

Enterprise

Private deployment, customer admin, IAM lifecycle hooks, and Microsoft or Google Workspace integration planning.

Contact us
  • Customer Enterprise Admin
  • On-prem agent
  • Microsoft 365/Teams
  • Google Workspace

FAQ

What is the difference between CLI and MCP?

Use shhhs for terminals, scripts, CI, and operator runbooks. Use shhhs-mcp when an agent runtime needs local MCP tools for encrypted secret handoffs.

Does the MCP server send plaintext to Shhhs?

No. Secret creation flows encrypt locally before upload. The MCP adapter should run locally and must not be exposed as an unauthenticated remote service.

Can this run in CI?

Yes. Team automation should use scoped API keys, stdin for secret input, JSON output for scripts, and short TTL/view limits.

Can agents exchange secrets without sharing account tokens?

Yes. The safer pattern is a request link: one agent creates it, another submits into it, and the owner reveals from the Shhhs console.