Documents

Semantic blocks and reusable templates.

#What Documents does

Documents built from semantic blocks — structured content your team reuses and your AI can actually read.

  • Semantic block editor. Compose documents from typed blocks. Structure is data, so content can be queried, reused and validated.
  • Reusable templates. Turn any document into a template. Proposals, contracts and briefs start from your best version, not your last one.
  • Attached to the work. Mention a project with @ and the document is tied to it — briefs and notes live with the work, never on a stray laptop.
  • AI-readable by design. Because blocks are semantic, your MCP-connected AI reads your documents as structured data (sstm://documents), not as a wall of text.

#Write with blocks and templates

  1. Click New document for a blank page, or pick a template from the gallery (grouped: Start, Engineering, Delivery, Team).
  2. Type / to open the block menu — headings, lists, quotes, code and more.
  3. Type @ to mention a project: the document links to it and shows up in the project’s workspace.
  4. Use the preview to print or save as PDF, styled by your org’s brand. Markdown export is built in.

#On the MCP surface

Your AI reads the document library over MCP — sstm://documents and sstm://document/{id} — so briefs, notes and decisions become real context when it builds. Writing happens in the editor, by people.

Resources (read):

  • sstm://documents
  • sstm://document/{id}

Full definitions live in the MCP reference.

#On the Cloudflare side

  • Documents are stored in the platform database and exposed to your AI as structured data over MCP (sstm://documents) — no Cloudflare resources of their own.