Strata Plugin for Claude Code and Codex

Strata Plugin for Claude Code and Codex

This release switches MCP to https://api.strata.space/mcp. Update the plugin and authenticate again after the API hostname cutover. Manually configured MCP clients must re-add the server with the new URL.

Work with your Strata documents from inside Claude:link a folder to a Space for live two-way sync, mount your Spaces as localfolders of Markdown, or read, search, publish, and review your documentsdirectly in conversation, including writing blog posts and creating and revising presentations. Installing the plugin registers the Strata MCP serverautomatically (no setup step), so the in-conversation skills work out of thebox; the filesystem skills add an optional CLI.

Table of contents

• What you get
• Quickstart
• Install the plugin
• Install the Strata CLI (optional)
• Requirements
• The seven skills
• Getting documents onto disk: link vs mount vs snapshot
• Other MCP clients
• Privacy and consent
• Troubleshooting
• Development
• License

What you get

The plugin ships seven skills and a bundled .mcp.json that registers theStrata MCP server on install. Two halves:

• Conversation skills use the MCP server without the Strata CLI. Search your Spaces, readdocuments, publish a draft, leave review comments, write and style blog posts, and create presentationsfrom a conversation or an existing local deck file.
• Filesystem skills drive the strata CLI to bring a Space onto disk asreal .md files — as a live-linked folder, a virtual-drive mount, or aone-time snapshot — so any editor can open them.

You only need the CLI for the filesystem half. Everything else works the momentthe plugin is installed.

Quickstart

1. Install the plugin (registers the MCP server):

   /plugin marketplace add strata-space/marketplace
   /plugin install strata@strata-space
   

2. Sign in — the first Strata tool call opens a browser once for OAuth. Ifyou are already signed in to strata.space, it completes in a click.

3. Try a conversation skill (no CLI needed). Ask Claude:

   Search my Strata Spaces for the Lighthouse rollout plan and summarize itwith citations.

4. (Optional) bring a Space onto disk. Install the CLI (below), then ask:

   Keep a local folder in two-way sync with my "Engineering" Space.

   or, for a virtual drive that shows the Space as a mounted volume:

   Mount my "Engineering" Space as a local folder.

Install the plugin

Add the Strata marketplace, then install the plugin:

/plugin marketplace add strata-space/marketplace
/plugin install strata@strata-space

inside any Claude client that speaks the marketplace protocol. On install, thebundled .mcp.json registers the Strata MCP server with your client; on thefirst tool call it opens a browser once for sign-in. No further configuration isrequired for the conversation skills.

Or, without the marketplace, install the plugin directly from its repo:

/plugin install strata-space/strata-claude-plugin

Codex

The same repository ships a Codex manifest (.codex-plugin/plugin.json), soCodex users get the bundled MCP server and the seven skills too. Add themarketplace source and enable the plugin (or install it from the Codex app'splugin directory):

# ~/.codex/config.toml
[plugins."strata@strata-space"]
marketplace = "github:strata-space/marketplace"

Then run /plugins in Codex and install strata.

Install the Strata CLI (optional)

The CLI is only needed for the filesystem features: linking a folder forlive sync, mounting a Space (strata-spaces), and bulk folder publish(strata-publish).The strata-spaces skill installs it for you on first run under explicitconsent, so you can skip this section and let the skill drive. To install ityourself ahead of time:

macOS (Homebrew):

brew install --cask strata-space/tap/strata

This taps strata-space/tap and installs the strata cask (the CLI plus thebundled FSKit filesystem module). After install, enable the module once:System Settings → General → Login Items & Extensions → File SystemExtensions → Strata CLI (switch the Extensions list to By Category if thetoggle looks stuck in the By App view).

macOS or Linux (official installer):

curl -sSf https://github.com/strata-space/strata/releases/latest/download/install-cli.sh | sh

The installer detects your OS and architecture, verifies the download, andplaces strata in ~/.local/bin by default (override withSTRATA_INSTALL_DIR). On Linux it lays out the binary alongside thest-agent background agent and its libstrata_fuse.so cdylib; on macOS itinstalls the app and symlinks strata.

Windows (early-adopter): download strata-windows-x86_64.zip from thelatest release,extract it somewhere stable (keep strata.exe and st-agent.exe together),and add the folder to PATH. The build is not yet code-signed — terminals runit without fuss; Explorer shows a SmartScreen prompt ("More info" → "Runanyway"). Live folder links work; virtual-drive mounts are macOS/Linux only.

Linux (manual): download the matching tarball from thelatest release —strata-linux-x86_64.tar.gz or strata-linux-aarch64.tar.gz — verify itagainst checksums.txt, and extract strata (plus libstrata_fuse.so, kept inthe same directory) onto your PATH. A live mount also needs the fuse3userspace helper from your distro (sudo apt install fuse3, or the dnf /pacman / zypper / apk equivalent).

Verify:

strata --version
strata login          # opens a browser; on a headless host, prints a URL + code
strata status         # shows auth, mounts, and sync sessions

Requirements

• Conversation skills (strata-research, strata-publish single-doc,strata-review, strata-blog, strata-presentation, strata-doctor connectivity half) — an MCP client that supports remote HTTP servers with OAuth (in Claude Code, run /mcp and choose Authenticate on first use). No Strata CLI needed.
• Live folder link (strata link, recommended) and bulk folder publish(strata-publish folder mode) — the Strata CLI only. Linking uses ordinaryfiles and the Strata background agent (one per-user login item thatsupervises every linked folder; strata agent status shows it), not akernel filesystem, so it works cross-platform (macOS, Linux, and Windows)on systems where a mount cannot (older macOS, WSL, containers) as long asthe agent can run.
• Virtual-drive mount (strata mount, optional) — the Strata CLI, pluseither macOS 15.4+ (FSKit backend, read-only, needs a one-time System Settingspermission) or Linux with kernel ≥ 4.18 and the fuse3 userspace helper (FUSEbackend, read/write).
• Windows is detected and routed to the in-conversation MCP skills; a nativemount is out of scope.

The seven skills

Skills activate from natural language — you do not call them by name. Theexample prompts below are illustrative.

strata-research — answer from your Spaces (MCP, no CLI)

Searches and reads your documents over the MCP server and links every claim backto its source. Read-only.

What did we decide about the buoy firmware OTA process? Cite the docs.

strata-publish — push local content up (MCP + CLI)

Two shapes. A single document (a draft in the conversation or one file) goesup over MCP with no CLI. A folder of Markdown (many files, possibly nested)syncs via the CLI's strata sync push — the only path that handles creates,updates, and deletes in one operation and can mirror a nested folder tree (with--folders). A new document's audience is the folder it lands in; new docsdefault to your private personal folder.

Publish this draft to my "Specs" Space.

Push my ./notes folder up to the "Research" Space, keeping the subfolders.

strata-review — comment, don't rewrite (MCP, no CLI)

Reads a document and posts feedback as anchored comments rather than editing thebody. Read-only with respect to the document text.

Review the "API Gateway LLD" doc and leave comments on anything risky.

strata-blog — write and style blog posts (MCP, no CLI)

Drafts a blog post from your prompt or turns an existing document into one, inyour voice. Sets the post's blog: frontmatter: summary, tags, coverthumbnail, header image, typography, colors, wallpaper, and series. Fixesevery validation finding and leaves the post as a draft for you to publish.

Turn my "launch notes" doc into a blog post. Use the photo as the thumbnailand a wide crop of it as the header.

strata-presentation — create and revise decks (MCP, no CLI)

Authors a presentation as a Strata document from your prompt and source documents.Infers the audience, purpose, length, and theme, bundling necessary questions intoone round. Supports slide edits, company themes, existing HTML deck import,validation, and export through the connected server's available tools.

Turn these project notes into a short presentation for the leadership team.

Use our company theme and tighten the recommendation on slide three.

strata-spaces — bring a Space onto disk (CLI)

Links a folder to a Space for live two-way sync as the recommended,cross-platform path: installs the CLI on first run, logs in, sets up the linkGit-safely (auto-adds the folder to .gitignore, never commits), and managesthe lifecycle — list, unlink, recover stuck sessions. As an optionalvirtual-drive alternative it can strata mount the Space (handling the macOSFSKit extension or the Linux FUSE helper), and it falls back to a one-timestatic-snapshot pull when even a link is not wanted.

Keep ~/strata/engineering in sync with my "Engineering" Space.

Mount the Lighthouse Space as a virtual drive.

strata-doctor — diagnose why Strata is not working (MCP + CLI)

Read-only diagnostician. Probes the MCP connection (registered, signed in, writescope, tool groups) and, when the CLI is present, its auth state, environmentconsistency, mount-backend prerequisites (the macOS FSKit module / the LinuxFUSE runtime), mount health, live folder-sync health (stuck / paused /degraded sessions, the pending write journal, blocked supervised mounts), andthe most recent write failure (with the owner and a request-access link). Itroutes every finding to a fix — a command you run or a hand-off to the owningskill — and never remediates by side effect.

Strata isn't showing my documents in Claude — what's wrong?

My edits aren't syncing / my save failed. Diagnose it.

Getting documents onto disk: link vs mount vs snapshot

There are three ways to get a Space's documents into a local folder. Thestrata-spaces skill picks the right one for your platform; here is the model.

Live link is the recommended path and the most portable: a backgroundservice keeps a folder and a Space in two-way CRDT sync — local saves pushto Strata and remote edits land in the files within seconds — cross-platform onmacOS and Linux, with no kernel extension and no permissions. Concurrent editingon both sides is safe: the service does a base-aware three-way merge and pauses alocal overwrite while you are mid-edit, so there is no clobber window. By defaultstrata link <folder> --space <id> installs a supervised background service(launchd on macOS, systemd on Linux); pass --foreground to run it in theterminal for one session (stop with Ctrl-C), or --no-autostart to installwithout starting. Stop and remove a link with strata unlink <space> (--pausestops it but leaves it to resume at next login).

The mount is the optional virtual-drive alternative: it shows the Space as amounted volume. On Linux it is read/write (FUSE); on macOS it is read-only andneeds a one-time System Settings permission (FSKit). Stop it with strata unmount.

Deleting a file locally unlinks the document from the Space and propagatesimmediately. Unlinks are reversible: the document is never destroyed and can bere-added by recreating the file. If a sync session is interrupted or stuck,re-run strata link <folder> --space <id> to recover it.

Check the health of any mount or sync session at a glance:

strata status --json | jq '{mounts, syncSessions, pendingJournal, blockedMounts}'

Other MCP clients

Claude Code picks up the Strata MCP server from the bundled .mcp.json(authenticate once via /mcp); Claude Desktop and claude.ai use the StrataSpaceconnector from the Connectors directory, and Cursor reads the bundled mcp.json.For another MCP client (VS Code, Zed, Continue, Cline, Windsurf), add the server to that client's MCP configyourself:

{
  "mcpServers": {
    "strata": {
      "type": "http",
      "url": "https://api.strata.space/mcp",
      "headers": { "X-Strata-Tool-Groups": "core,comments" }
    }
  }
}

The X-Strata-Tool-Groups header opts into the comments capability group sostrata-review works (that group also exposes Strata's suggestion tool, whichstrata-review deliberately does not use); drop the header entirely forread-only research and publishing. On the first tool call the server opens abrowser for OAuth. That login is separate from the CLI's keychain token, but ifyou are already signed in to strata.space in your browser it completes in oneclick, because it reuses your browser session rather than your CLI token.

Privacy and consent

Every privileged command (brew install, apt install, dnf install,pacman, zypper, apk, sudo usermod, diskutil unmount force,fusermount3 -uz) is proposed in conversation and requires explicit userconfirmation before execution. Operations that write to your Strata content(publishing, commenting) are confirmed in conversation before the first write.Deleting a synced file unlinks the document from the Space (reversible, neverdestroyed) and propagates immediately. No binary downloadproceeds without SHA-256 verification against a published checksum. Noenvironment-specific URLs are hardcoded beyond the MCP endpoint; the rest is readfrom your CLI auth state.

Troubleshooting

The fastest path is to ask Claude — the strata-doctor skill runs a fullread-only diagnosis and routes each finding to a fix:

Diagnose my Strata setup.

A few things you can check yourself:

• The Strata tools are missing in Claude. The plugin's .mcp.json registersthe server on install; confirm the strata plugin is installed and enabled,and restart Claude if you just installed it.
• A tool call fails with an auth error. The first call opens a browser forsign-in; complete it and retry. For the CLI half, run strata login.
• strata-review has no comment tool. Re-authorize and accept the writescope, and make sure your MCP config sends X-Strata-Tool-Groups:core,comments.
• A mount silently does nothing on macOS. The FSKit module is installed butnot approved — enable Strata CLI under System Settings → General → LoginItems & Extensions → File System Extensions (use the By Category view).
• Edits are not syncing. Run strata status --json and look atsyncSessions (is it live, degraded, or paused?) and pendingJournal(is the backlog draining?). strata-doctor interprets these for you.

Development

Layout:

.claude-plugin/plugin.json   # plugin manifest
.mcp.json                    # auto-registers the Strata MCP server
skills/
  strata-research/SKILL.md   # ask your Spaces (MCP)
  strata-publish/SKILL.md    # push local content up (MCP + CLI)
  strata-review/SKILL.md     # comment on a document (MCP)
  strata-blog/SKILL.md       # blog post authoring and styling (MCP)
  strata-presentation/      # deck authoring skill and references (MCP)
  strata-spaces/SKILL.md     # mount + live-sync lifecycle (CLI)
  strata-doctor/SKILL.md     # diagnose connectivity, mounts, sync, write failures (MCP + CLI)
tests/                       # VM smoke runners (bash)

Run the smoke tests on a clean VM (each script no-ops on a wrong platform, exitsnon-zero on a failed assertion):

bash tests/macos-first-mount.sh           # macOS 15.4+
bash tests/linux-debian-first-mount.sh    # Ubuntu / Debian
bash tests/linux-fedora-first-mount.sh    # Fedora
bash tests/linux-arch-first-mount.sh      # Arch
bash tests/git-mount-gitignore.sh         # any platform
bash tests/snapshot-fallback.sh           # any platform with strata CLI
bash tests/unmount-lifecycle.sh           # any platform with strata CLI
bash tests/permission-denied.sh           # any platform with strata CLI

The MCP skills (strata-research, strata-review) are conversation-drivenorchestration over the MCP server; there is no host-side bash to smoke-test, sothey have no test runner. CI runs the platform-agnostic tests on every push andPR; per-OS first-mount tests are reserved for release rehearsal.

Presentation tests use the built-in Node.js test runner (Node.js 20+):

node --test tests/presentation/*.test.mjs

The import cases and documentation overview are committed snapshots, so CIneeds neither the monorepo nor Strata credentials. For release rehearsal againsta freshly generated platform corpus, pass its manifest explicitly:

STRATA_DOCS_MANIFEST=/path/to/aidocs/packages/shared/src/generated/docs-manifest.json node --test tests/presentation/compatibility.test.mjs

See the import rehearsal for fresh agent runs.The live documentation corpus remains the runtime authority for the skill.

License

MIT. See LICENSE.