The connector

Your studio, inside every AI tool you build with.

While you work in Claude, Codex, Cursor or anything else, your agent notices what’s worth showing: a finished screen, a demo, a launch. It works out which of your brands the project is, asks you once, and files the material into that brand’s vault. The studio drafts from it later. You still approve every post.

One address, every tool

https://slushie.studio/api/mcp

It finds the brand

From the git remote, the folder or the package name. Not sure? It asks you, then remembers in every tool.

It asks first

One line: “Add the new checkout screens to Purple Wallet’s vault?” Say yes, or tell it to stop asking for that project.

It files, never posts

The studio reads each file, captions it and sorts it into folders. Drafting, approving and posting stay with you.

Add it

Add it once for every project:

claude mcp add --transport http --scope user slushie https://slushie.studio/api/mcp

Then run /mcp in Claude Code, pick slushie and sign in.

Optional: the skill that tells it when to reach for Slushie.

mkdir -p ~/.claude/skills/slushie && curl -fsSL https://slushie.studio/connector/SKILL.md -o ~/.claude/skills/slushie/SKILL.md

With a personal key instead of signing in:

claude mcp add --transport http --scope user slushie https://slushie.studio/api/mcp --header "Authorization: Bearer $SLUSHIE_KEY"

What it can do

match_brand · remember_project · forget_project

Which brand this project is, remembered across tools until you forget it.

list_brands

Your brands, how full each vault is, the projects linked to each.

vault_add

Small photos and clips, inline.

vault_upload_start · finish

Big files and videos, straight to storage (photos to 45 MB, videos to 50 MB and 5 minutes).

tell_news

A line of what’s new, read the next time the studio drafts for that brand.

never

Draft, approve, schedule, post, or read your drafts and accounts.

Try asking

“Which of my Slushie brands is this project?”
“Add the new onboarding screens to this brand’s vault.”
“Put the demo video I just recorded in the vault, with a note on what it shows.”
“Tell Slushie we shipped Apple Pay at checkout today.”
“What’s in each of my brands’ vaults?”

What it sends

Only what your AI tool sends on your behalf: the files you add, a note on each, a line of news, and the details it uses to recognise a project (its git address, folder, package name or website).

Files go to the brand’s private vault. Slushie reads a small preview of each to caption it and sort it. Nothing is posted: drafts, approvals and publishing stay in Slushie, with you.

Sign-ins and keys are stored only as one-way hashes. Sign a tool out, remove a key or forget a project below at any time. More in the privacy policy; questions to team@slushie.studio.

Yours

…