Docs

MCP tools

Three HTTP servers. Creator tools need OAuth or bearer. Respond tools need only a Capsule link.

Servers

  • https://standin.app/api/mcp — create, review, publish (OAuth)
  • https://standin.app/api/respond/mcp — read, ask, bind (no auth)
  • https://standin.app/api/stand-in/<slug>/mcp — bound read/ask

Registry: server.json. Agent protocol: llms.txt.

Creator loop (call order)

  1. who_am_i — credential kind, actorClientId, open work
  2. session_start — optional session note + gaps
  3. create_stand_in or add_context / add_file / add_source_url
  4. approve_capsule_items — human authority in Mirror; agent can call after human says yes
  5. publish_capsule — live link
  6. update_capsule · unpublish_capsule · mark_asks_seen

Creator tools (default surface)

Identity & session: who_am_i, session_start, session_end

Authoring: create_stand_in, create_capsule, add_context, add_source_url, add_file, host_page, set_primary_artifact

Read: get_capsule_state, read_capsule_items, list_capsules, search_context, list_sources, read_source

Review & publish: approve_capsule_items, remove_capsule_item, publish_capsule, update_capsule, unpublish_capsule

Rehearsal & activity: run_coverage_check, get_demand_insights, start_bake, get_bake_status, preview_capsule, preview_ask_capsule, compose_capture_reply, approve_agent_filings, reject_agent_filings, set_source_consolidation

Demand: list_questions, list_asks, mark_asks_seen, list_capsule_gaps, answer_capsule_gap

Keys & automation: mint/list/revoke capsule keys, webhooks, add-links; watch_source; export_library; item revisions

Per-tool reference: /docs/mcp-reference · Store kit: /docs/mcp-store · CLI: npx usestandin login

Legacy Gather/Give tools require STANDIN_LEGACY_MCP=1 on the server. Bearer token rotation is only at /home/connect (not an MCP tool).

Respond tools

read_capsule, read_capsule_items, read_briefing, ask_capsule, bind_capsule, diff_since, poll_answer, download_capsule_file, start_intake, answer_intake, finalize_intake

Errors agents should handle

  • revision_conflict — re-read, merge, retry with new ifRev
  • Sensitive screen — ask human; retry with confirmSensitive: true only if they approve
  • 401 on creator server — OAuth sign-in or bearer at /home/connect; use respond server for read-only