Install & connect.

{
  "extraKnownMarketplaces": {
    "crue-os": { "source": { "source": "github", "repo": "crue-os/crue-os" }, "autoUpdate": true }
  },
  "enabledPlugins": {
    "crue-brand@crue-os": true,
    "crue-web@crue-os": true,
    "crue-product@crue-os": true,
    "crue-media@crue-os": true,
    "crue-content@crue-os": true,
    "crue-studio@crue-os": true,
    "crue-ops@crue-os": true
  }
}

Admins use admin-settings.json: the same plus "crue-hub@crue-os": true. Both files live in the repo under GETTING-STARTED/claude-code/.

Auth. GitHub read on crue-os/crue-os (gh auth login). For background auto-update set GITHUB_TOKEN with repo scope. By hand instead: /plugin marketplace add crue-os/crue-os, then /plugin install crue-web@crue-os and the rest.

Where the work comes from. Directory connector, or https://mcp.clickup.com/mcp, OAuth. Skills stay inside the crue space; each person sees only the lists ClickUp lets them see, so Sales and Admin stay with Roman and Edvin.

The official remote MCP, https://mcp.figma.com/mcp, OAuth. Reads designs, writes files, pages, images and SVG, pushes a built page back into Figma. Writing needs a Full seat. In Claude Code the official plugin adds Figma’s own skills: /plugin install figma@claude-plugins-official.

Licensed stock: photos, video, music, sound, fonts, graphics, mockups, 3D, templates. Org custom connector https://mcp.envato.com/mcp, no login: click Connect once under Settings → Connectors. It searches and returns watermarked previews with links; the download and the licence registered to the client project happen in Envato Elements under the crue account (1Password). Certificate to SharePoint Projects/<Client>/licences/.

Claude Code without a claude.ai login: claude mcp add --transport http --scope user envato https://mcp.envato.com/mcp.

600k+ real screens and flows. Directory connector, or https://api.mobbin.com/mcp, OAuth with your Mobbin seat.

Ideogram for type in image: https://mcp.ideogram.ai/mcp. Recraft for real vector, icon sets and brand style sets: https://mcp.recraft.ai/mcp. Higgsfield for image and video: https://mcp.higgsfield.ai/mcp, one shared crue account. All OAuth. After generating, open the result in the tool to download.

The hands behind lock to client. Add custom connector https://api.githubcopilot.com/mcp/ and sign in. Grant only crue-os/crue-clients and crue-projects, Contents read and write. Never crue-os, crue-house or crueweb. Claude Code commits with git, so the MCP is optional there.

Directory connectors. Outlook drafts, never sends; SharePoint is read-only today. Sanity and Supabase for web builds that need a CMS or a backend.

Directory connector, or https://mcp.vercel.com, OAuth. It sees only the Vercel teams the person belongs to: team crue holds Roman and Edvin as owners and Fisnik as Developer for care. Production only after the Roman Pass.

Add custom connector https://bexio-mcp.crue.ch/mcp, sign in with your crue Microsoft 365 account. ALLOWED_EMAILS lists Roman and Edvin only, and it is enabled in the crue · House Project only. Creates, never sends.

shadcn and Tailwind component scaffolds, restyled to the tokens. Old Magic keys were reset: get a fresh one at 21st.dev/mcp, then:

npx @21st-dev/cli@latest init --client claude

Or as a plugin: /plugin marketplace add 21st-dev/magic-mcp, /plugin install 21st, key in API_KEY_21ST.

Captures reference sites and checks our own builds. Ships inside the crue-web pack, so it registers itself. Needs Node 18+; the first run downloads a browser. On the web surface the skills use the Chrome connector instead.

Real traffic and funnels, read-only. In Google Cloud enable the Analytics Admin and Data APIs and create a Desktop OAuth client, then:

gcloud auth application-default login \
  --scopes=https://www.googleapis.com/auth/analytics.readonly,\
https://www.googleapis.com/auth/cloud-platform \
  --client-id-file=YOUR_CLIENT.json

claude mcp add analytics-mcp --scope user \
  -e GOOGLE_APPLICATION_CREDENTIALS=PATH \
  -e GOOGLE_PROJECT_ID=PROJECT_ID \
  -- pipx run analytics-mcp

The team workspace. Every client build in progress: <client>-website, <client>-app, <client>-docs. Branches, PRs, previews.

Finished and live, linked to Vercel. When a build ships and is worth keeping, an admin transfers the repo here from crue-projects and relinks the Vercel project. Fisnik writes on the live sites he looks after.

crue-os: the skills and standards; the team reads, admins merge. crue-clients: one Client Core per client under clients/<slug>/; the team writes by lock to client. crue-house: pricing, proof and crue’s own memory; admins only.

1. Generate something in the client Project: a colour, a voice, a style lock-in, a reference pack, a decision.
2. Say “lock to client”. The skill shows a lock card (item, file, the change), checks it against what is already locked, logs the decision.
3. It commits to crue-clients/clients/<slug>/<file>.md through the GitHub write MCP. Never a force-push.
4. Sync the Project so the next chat reads the new state. The committed Core is the memory, not the chat.

1. Generate the Core (admin). In crue · House run initialize-project: pick or create the client in Bexio, it creates clients/<slug>/ from the latest template and commits it.
2. Create the Project named Client · <Name> and share it with the people on the work.
3. Mount the Core. Files → GitHub → crue-os/crue-clients → only clients/<slug>/, read-only. Set the archetype in brand-pack.
4. Set the instructions. “This is the Client Core for <Name>. Always read brand-pack.md first. Stay within this brand. Never reference other clients or the crue House brand.”
5. Brief to tasks. clickup-brief puts one task in the right Projects list with an owner, dates and the Client, Claude Project and Github Client Brain fields. Size, never budget.
6. Work, then lock. The teammate runs the skill from the task, ends on the Roman Pass, says “lock to client”, hands in to review.