AI in sSystm

One workspace.
AI on both sides.

sSystm ships with AI inside — an editor AI grounded in your brand, your components and your skills. And the whole platform is an MCP surface for the AI you already work with. Same context, both sides — and you stay in control.

CRMProjectsDesign tokensComponentsWireframesDocumentsSkillsWorkspace contexteverything, connectedsstm://project/{id}/contextBuilt-in AIBuild AI · Claude via AI GatewayAssistant · Workers AIYour AI · via MCPClaude · Cursor · any MCP client26 tools · 30 resources

The real architecture: one context bundle feeds the built-in AI and your own — verified against the code.

Act I · Built in

The platform ships
with AI inside.

Not a chatbot in a corner. An editor AI that writes in your brand, an assistant that answers from your workspace — running on Cloudflare, billed through Cloudflare.

Build AI — pick your Claude

The editor AI in Build streams real code, file by file — on Anthropic models through Cloudflare AI Gateway, with prompt caching cutting repeat costs. You choose the model.

Claude Haiku 4.5fast — the default
Claude Sonnet 4.6balanced
Claude Opus 4.8most capable

A workspace assistant

A built-in assistant on Workers AI (Llama 3.3 70B through AI Gateway) that answers grounded in a live bundle of your workspace — and is instructed to never invent data, numbers or names.

Wireframe generation runs on Workers AI too, with a Cloudflare Workflow carrying the long jobs.

All of it on Cloudflare

Workers AI for the assistant and embeddings, AI Gateway in front of every model call, Vectorize for semantic search, Durable Objects for real-time — and team voice in Chat on the Realtime SFU.

No second AI vendor to onboard. Usage is billed through Cloudflare, with per-org cost metadata on every call.

It knows your whole workspace.

Everything in sSystm is connected to everything — so before the Build AI writes a line, the platform assembles the truth around it. Four layers, straight from the code:

  1. 1Design tokens & rules — verbatimYour active design system's tokens and written rules are injected into the prompt before a single line is written: exact colours, radius, fonts — "use these EXACT values".
  2. 2Semantic component searchYour component library is embedded (bge-m3 on Workers AI) and searched in Vectorize — isolated per organisation — so the closest matching components arrive with their full code: "reuse them verbatim".
  3. 3Project-linked components — alwaysComponents you have linked to the project are always in the prompt, full code included. They are the org's chosen parts for this build.
  4. 4Skills packs — alwaysAttached skills (SEO, performance, accessibility …) are always injected: proven techniques the project must follow, with template files.
Build AI · assembling context before writing
you: "Add a pricing section to the Brightside landing page"
inject design tokens + rules
accent #2F6F4F · radius 12px · "never pure black"
search components in Vectorize · org-isolated
PricingCard · SectionHeading — full code, reuse verbatim
inject project-linked components + skills
BrightsideNav · skill: SEO landing pages
✓ On-brand from the first token
Streaming to the editor — live preview as it lands.
Act II · Bring your own

Connect the AI
you already trust.

Claude on claude.ai, Claude Code in your terminal, Claude Desktop, Cursor — any MCP client. One endpoint, one token, and your AI works inside your workspace.

26
tools

sstm_* — real writes: deals, projects, tokens, components, wireframes, skills, chat

30
resources

sstm:// — your live workspace as structured, readable data

3
recipes

component · wireframe · design — the exact data models your AI builds with

1
endpoint

/api/mcp/stream — Streamable HTTP with a per-user Bearer token

Single source of truth
sstm://project/{id}/context

Everything an AI needs to build for one project, bundled: the project, its active design system — tokens, rules and the resolved brand CSS — linked components with full code, attached skills with their instructions and template files, and the wireframes. The same bundle the built-in Build AI is grounded in.

Recipes, not codegen
sstm://component/recipesstm://wireframe/recipesstm://design/recipe

sSystm never generates on your AI's behalf. It serves recipes — the full token vocabulary, the wireframe data model with all 75 blocks, worked examples. The server's own words: "YOU write the component yourself."

Two minutes to connect

The exact setup the MCP module in the app walks you through — endpoint /api/mcp/stream, one Bearer token per user.

Claude Codeshell
claude mcp add --transport http sstm \
  https://<your-workspace>/api/mcp/stream \
  --header "Authorization: Bearer <your-token>"
Cursorjson
{
  "mcpServers": {
    "sstm": {
      "url": "https://<your-workspace>/api/mcp/stream",
      "headers": { "Authorization": "Bearer <your-token>" }
    }
  }
}
Claude Desktopjson
{
  "mcpServers": {
    "sstm": {
      "command": "npx",
      "args": ["-y", "mcp-remote",
        "https://<your-workspace>/api/mcp/stream",
        "--header", "Authorization: Bearer <your-token>"]
    }
  }
}
claude.aiurl
Settings → Connectors → Add custom connector
https://<your-workspace>/api/mcp/stream?token=<your-token>
Human in control

Your AI can read everything.
You approve what matters.

Every write your AI makes lands visibly in the workspace — components render live in the catalogue, chat posts are always attributed as AI, reviews reach your Health view as findings. And infrastructure changes on your Cloudflare account are gated: safe reads may run, anything risky is staged as pending until a human approves it.

Visible by design

AI-written components, wireframes and messages appear instantly in the workspace, attributed and reviewable by the team.

Gated infrastructure

sstm_cloudflare_execute never auto-runs risky or destructive operations — they wait as pending approvals in the UI.

Reviews, recorded

Your AI records findings on real project output with severities — and you decide what gets resolved.

AI · built in and bring your own

One workspace.
AI on both sides.

Join the waitlist — when your spot opens, the built-in AI writes in your brand from day one, and Claude, Cursor or any MCP client connects to the same workspace, gated by you.

When you're in: no email, no password — one Cloudflare grant · core workspace free · your data lives in your own account