Cast spells from your coding agent.
We're building an MCP (Model Context Protocol) server that connects Spellsuite to Claude Code and Codex: write the brief in your terminal, and the suite drafts into the same review queue as always. Status: in development — not yet available. The dashboard is and remains the product; the CLI is another wand pointed at it.
The idea
Your agent briefs. Your dashboard decides.
If you already run your day inside Claude Code or Codex, marketing shouldn't require leaving it. The connector adds Spellsuite as a set of MCP tools your agent can call.
Brief from the terminal
Ask your agent to launch a campaign the way you'd ask it to fix a bug. It passes the brief to Spellsuite as a spell.
Same queue, same guardrails
Everything the connector triggers lands in the dashboard review queue with the same caps and approval rules. The terminal gets no shortcut around you.
Status readable by agents
Your agent can ask what shipped, what's waiting, and what the ad spend did this week — and get answers it can reason about.
Launch-context aware
Shipping a feature from your repo? The agent can brief the campaign from the same context — release notes in, launch content out.
Concept preview
What a session could look like.
Illustrative only — the interface will evolve as we build. Email us to shape it: the beta list doubles as the design-partner list.
~ claude
> we ship dark mode on friday. cast a launch: blog, 6 posts, CHF 300 ads cap
✶ spellsuite.cast_spell(brief, cap=300)
✶ Drafted: 1 post, 6 social drafts, 2 ad variants
→ waiting for approval in the queue
Concept preview — in development
In development
Want to cast from the terminal first?
Tell us which agent you use and we'll bring you in as the connector ships.
Join the beta listno spam — one email when it's ready