Docs

Connect, create, review, share.

The full creator loop in one page. About two minutes once MCP is connected.

1. Connect

Pick your client. Creating uses the authoring server; reading a shared link uses the respond server (no account).

Claude Code (recommended for a demo)

# Create and file (signs in on first use)
claude mcp add --scope user --transport http standin \
  https://standin.app/api/mcp

# Read or ask any shared capsule (no sign-in)
claude mcp add --scope user --transport http standin-read \
  https://standin.app/api/respond/mcp

Claude (web / desktop)

Customize → Connectors → add https://standin.app/api/mcp. It signs in in the browser. Details: /install/claude.

Cursor

Download the JSON at /install/cursor, or add the same MCP URLs in settings.

Do not paste a bearer token into chat. OAuth and Connect on home exist so credentials never live in the transcript.

2. Create

In Claude, say something like:

  • “Create a Stand In from this repo for the next agent picking up auth work.”
  • “File these notes and the PDF as a Stand In, then give me the review link.”

Or from a terminal (after Connect on home):

npx usestandin create --from .

You can also drop a PDF or markdown on standin.app and sign in. Same Capsule, same Mirror.

3. Review in Mirror

Open the review link your agent returns. Proposed items are drafts. Approve what may travel, reject what should not, then publish. Until you publish, someone else’s agent sees nothing.

That gate is the product. Skipping it turns Stand In into another untrusted dump.

4. Share the link

Send the published URL.

  • A person opens it, reads the briefing, asks questions in the page.
  • An agent: add /api/respond/mcp (or bind the capsule URL), then ask. No account.
  • CLI: npx usestandin ask <link> "why session cookies"

Questions the Capsule cannot answer return to you as gaps on home. Answer them there; the Capsule improves.

Done when

You have published once for a real handoff, someone else read or asked it, and you made a second Capsule without a founder driving the setup. That is the proof loop. More ingest surfaces can wait.

Back to docs · Agent protocol · All clients