Documentation Map

Pages

StrataSpace DocumentationStrataSpace is a real-time document editor where people and AI agents edit together. Import DOCX, PDF, or PPTX files, add comments and suggestions, publish, and connect Claude or ChatGPT through MCP (Model Context Protocol).
Get StartedThe fastest way in is the Claude Code plugins. Add the StrataSpace marketplace once, then install the plugins you want. The MCP server and the Spaces skills come with them.
Claude Code PluginThe StrataSpace plugin is the fastest way to connect Claude Code. Installing it registers the StrataSpace MCP server automatically and adds the Spaces skills, so research, publish, and review work the moment it's installed. The CLI is optional, only for mounting Spaces as local files.
PresentationsCreate, edit, and present slide decks in StrataSpace. Start with a blank deck, ask StrataSpace Agent to draft one from your source documents, or import Markdown.
MCP Tools ReferenceStrataSpace exposes 33 tools via the Model Context Protocol, organized into groups. By default, core and comments tools are enabled. Choose other groups via the X-Strata-Tool-Groups header.
CLI InstallationThe StrataSpace CLI lets you keep your Spaces on disk as Markdown, on macOS and Linux. The simplest install is the download page, which detects your OS; the commands below do the same from the terminal.
CLI Command ReferenceComplete reference for all 55 strata commands, generated directly from the CLI itself. What you read here is exactly what --help prints.
REST APIStrataSpace is built on a REST API described by an OpenAPI 3.1 specification. Most integrations use the MCP server rather than calling REST directly, but the full spec is available for tooling and custom clients.
Documentation MapEvery documentation page and section on one page: all guides, every CLI command, every MCP tool, and every frontmatter schema, deep-linked.
Get things done in StrataSpaceStep-by-step help for editing documents, reviewing changes, making presentations, and publishing your work.
Edit a document with your agentConnect your agent, point it at a StrataSpace document, and choose whether it should edit directly or propose changes for review.
Propose and review suggested editsSelect text, propose a replacement, and accept or reject suggestions from collaborators and agents in StrataSpace.
Review a document with commentsAttach feedback to selected text in StrataSpace, reply in a thread, and resolve the discussion when the change is settled.
Inspect and restore document historyCompare past edits, restore a previous version, or undo a specific change in StrataSpace.
Share a document with collaboratorsInvite people to a StrataSpace document, choose their access level, and distinguish collaboration from public publishing.
Give your agent a focused SpaceCollect StrataSpace documents in a Space, link folders, and make the collection discoverable to your agent.
Import a document into StrataSpaceImport Markdown, HTML, DOCX, PDF, or PPTX into editable StrataSpace blocks and check conversion notes.
Create a presentation with your agentUse StrataSpace’s agent handoff to create a deck, then open it in Deck view to review and revise it.
Edit slides and speaker notesUnderstand Deck and Document views, choose slide layouts, and keep speaker notes separate from visible slide content.
Present a deck with speaker notesOpen StrataSpace’s presenter view, follow your notes, and show the audience window during a presentation.
Change a presentation’s themeChoose a shipped or company theme in StrataSpace and understand how imported theme copies and validation work.
Add an interactive visual to a slideUse an HTML slide in StrataSpace, bind it to document data, and check its static state before sharing or exporting.
Export or share a presentationPublish a StrataSpace presentation or export PDF or standalone HTML, then check what your audience will see.
Publish a document to your profileMake your StrataSpace profile public, choose a document URL, and publish a reading edition.
Publish an HTML page from Claude as a live, shareable linkAsk Claude to build an interactive HTML page in StrataSpace, publish it to a public link, and keep updating it without changing the URL.
Update or unpublish a public documentUnderstand Edits pending, publish a revised edition, and remove a post from your StrataSpace profile.
Style a published documentUse StrataSpace’s blog settings to control a published page’s appearance, summary, and table of contents.

Guide sections

From conversation to slidesUse strata-presentation to turn the conversation into an audience, purpose, and sequence of supported claims. Read the source material and company design system before styling. Use one headline per slide, evidence in its visual, and narration in ordinary section prose. Save with create_document/replace_document_text and read the result back; inspect available HTML previews and report any rendering limits.
Document grammarA leading YAML block with presentation: true enables defaults. A presentation map accepts only aspect (16:9, 16:10, 4:3), transition (fade, none, slide), form (slides, whole-deck), and notes (presenter, none). Defaults are 16:9, fade, slides, presenter. The YAML limit is 16 KiB. Theme is not a frontmatter setting.
Design systems and company themesFind and read the company design system, then copy its CSS into one css name=theme fence. Record source and sourceVersion together using the actual document ULID and decimal version when known; both are required for provenance. Preserve an existing locked=true. The copy is local content: resolution never fetches or refreshes the source. If no company theme is available, start with strata-light.
Sharing and exportingOwners and editors read the full document. Viewers, commenters, and suggest-only readers receive an edition containing accepted slide headings and visuals, with ordinary notes removed. Put private narration outside visual fences. notes: none describes pane visibility, not privacy. Removing or disabling presentation settings makes the document ordinary again, so readers can receive its full body.
Bringing an existing deckPreserve existing files and inspect their format. For UTF-8 Markdown, measure bytes, call presign_document_upload with contentLength plus documentId or title/folderId, PUT the exact bytes with all returned requiredHeaders, then finalize_document_upload with uploadId. Read back after finalization. Adapt HTML decks into a whole-deck Markdown copy and check sandbox dependencies and internal notes. Office-file upload converts PPTX/PDF/DOCX into ordinary documents; it does not promise original slide fidelity. Do not send those binary files to the Markdown upload flow. Using an existing documentId requests full replacement at finalize_document_upload; the PUT only stages bytes. Neither finalize_document_upload nor rewrite_document accepts an expected version, so replacement can overwrite collaborator changes without a version-conflict error. Prefer small, uniquely anchored replace_document_text calls with replaceAll=false; they check only the serving task’s replica, and block edits can fall back to a structural rewrite. No MCP body-write path guarantees safety against a concurrent editor. If the deck appears actively edited, tell the user and coordinate a pause or prepare a separate copy. If replacement is unavoidable, reread immediately before finalization, compare documentVersion with the version used to prepare the file, and abort if it changed. An unchanged version narrows the race window but does not close it.
Validation and repairRun validation before presenting or exporting. validate_presentation checks layout, contrast, data bindings, structure, and themes, and stores captures. Each call checks at most two slides at one viewport; continue with next while status is more, keeping the selection unchanged. Validation uses one capture per slide per viewport, with no repeat charge for the same render key in the billing cycle. Review findings, repair the source, and check again.
Keeping a deck currentUse list_company_themes and get_company_theme to copy a verified company theme revision. One agent routine per deck watches updated document events for both the theme source and the deck, with target naming the deck and no output. It proposes anchored suggestions with baseVersion and sourceRef; it never accepts, edits, or publishes. Newer source generations supersede older pending proposals. On suggestionBaseMoved or suggestionSourceMoved, wait for the next run or rerun instead of overwriting. Other documents’ copied data remains a snapshot. An administrator provisions the Themes folder when setupRequired is true.
Blog designUse a blog: mapping in the first YAML frontmatter block to design a published post. The appearance panel edits this same text and preserves unrelated keys and comments.
Make a presentationOpen Presentations in your workspace. Choose New deck and enter a title, or ask StrataSpace Agent for a deck. For an AI draft, describe the topic, audience, and purpose; choose a length, theme, and source documents. Review the credit estimate and maximum credits before starting.
Agent frontmatterAn agent definition is a Markdown document under your /Agents folder. The YAML frontmatter declares the agent's identity, tool allowlist, and orchestrator visibility; the body below the frontmatter is the system prompt the orchestrator hands the user's request to verbatim. Every field is validated server-side on save.
Interactive HTML blocksCode blocks tagged html render as live, sandboxed previews in the StrataSpace editor and in exported PDFs — charts, diagrams, 3D scenes, and small interactive widgets, written as ordinary fenced code.
Prompt frontmatterA prompt template is a Markdown document under your /Prompts folder. The YAML frontmatter declares the prompt's name, description, arguments, and orchestrator visibility; the body below the frontmatter is the prompt template — {{argument}} placeholders are substituted at render time. Argument values are collected by the chat composer's slash sheet or the MCP prompts/get request.
Template frontmatterA document template is a Markdown document inside a templates folder. The YAML frontmatter declares the template's name, typed variables, and section contract; the body below the frontmatter is the reusable content — {{key}} placeholders are substituted when a document is created from the template, via the gallery, the MCP create_document_from_template action, or an agent's create_document_from_template tool.

Documentation Map

Pages

Guide sections

CLI commands

MCP tools