How it works
Claude's intelligence.
Orbit's expertise.
Orbit is an MCP extension: a package of 63 specialist skills and 91tools that plug directly into Claude. You get all of Claude's reasoning, language, and context abilities, backed by deep lifecycle marketing knowledge that Claude doesn't have on its own.
When Claude returns a diagnosis, recommendation, or synthesis grounded in lifecycle methodology, that's Orbit Intelligence — the senior-operator layer Orbit gives Claude. It walks you through getting the right inputs before a tool runs, cites the specific guides that informed each answer, and closes every substantive response with a concrete next action.
What is an MCP extension?
Model Context Protocol (MCP) is an open standard created by Anthropic that lets Claude use external tools and data sources. Think of it as a plugin system, but instead of simple add-ons, MCP extensions can give Claude entirely new capabilities.
When you install Orbit, Claude Desktop gains access to specialist skills (structured expertise for lifecycle marketing tasks) and tools (functions that read data, build artifacts, and connect to platforms like Braze).
You don't need to learn a new interface. You talk to Claude exactly as you normally would. Orbit works behind the scenes. Claude knows when to use Orbit's skills and tools based on what you ask for.
What each layer does.
Layer 1
Claude: the reasoning engine
Claude handles the thinking, writing, and conversation. It understands your context, remembers what you've discussed, writes copy, analyzes data, and adapts to your tone. Orbit doesn't replace any of this. It builds on top of it.
Layer 2
Orbit Skills: structured expertise
63 specialist skill protocols that give Claude domain knowledge in lifecycle marketing. Each skill is a structured operating procedure. Not a prompt, but a framework with execution standards, diagnostic steps, and output formats.
Skills cover segmentation strategy, retention economics, experiment design, deliverability management, multichannel orchestration, and more. When you ask Claude to design a win-back program, Orbit loads the relevant skill and Claude follows its methodology.
Layer 3
Orbit Tools: actions and integrations
91 MCP tools that let Claude take action, not just advise. Build message plans, generate MJML email templates, compile HTML, create lifecycle diagrams, validate email markup, and export documentation. Tools produce real artifacts you can use immediately.
All 63 skills
Bring your own API keys. Here's what each one adds.
Orbit works out of the box with no configuration. Connect your own API keys and it stops being a strategy tool — it becomes an operations layer that reads, writes, and publishes to the platforms you already run on.
Braze API Key
Connect your Braze REST API key and endpoint, and Orbit becomes a native Braze intelligence layer. It can:
- Audit your entire Braze workspace: Canvases, campaigns, segments, content blocks, templates
- Read Canvas structures and reverse-map them into Orbit message plans
- Validate that custom events and attributes referenced in your programs actually exist
- Publish email templates and Content Blocks directly from Claude
- Upload images to Braze's media library
- Pull performance data: Canvas entries, campaign open/click rates, segment growth, MAU/DAU
- Check deliverability health: bounce rates, unsubscribe trends
Google AI (Gemini) API Key
Connect a Gemini API key and Orbit can generate brand-safe header images for your emails and lifecycle diagrams. It uses your brand kit (colours, logos, fonts, tone of voice) to produce on-brand visuals directly inside Claude. No design tool required.
Figma API Token
Connect a Figma token and Orbit can import structured email designs directly from your Figma files. It reads the design, infers reusable email components, maps them to its canonical taxonomy, and generates production MJML, translating your designer's work into code without manual handoff.
How to add API keys
- Open Claude Desktop.
- Go to Settings › Extensions › Orbit › Configure.
- Paste your keys into the relevant fields: Braze REST API key and endpoint (e.g. rest.iad-01.braze.com), Gemini API key, or Figma token.
- Save. No restart needed — Orbit picks up new keys on the next message.
All API keys are stored locally in your Claude Desktop settings. They never leave your machine. Orbit connects directly from your device to the platform APIs.
What the workflow looks like.
There's no new interface to learn. You talk to Claude. Orbit handles the rest.
You describe what you need
"Build me an onboarding sequence for new trial users on Braze." That's it. Natural language, not configuration.
Orbit runs structured discovery
Before building anything, Orbit captures objectives, KPIs, audience, data sources, and constraints. It grounds the work in your context.
Claude builds with Orbit's tools
Message plans, email templates, lifecycle diagrams, QA checklists. Real artifacts produced in your conversation, not mockups.
Orbit validates before deployment
Checks your data model, verifies Liquid fallbacks, validates email markup, confirms Content Block references. Catches errors before they reach users.
Publish directly to Braze
Email templates, Content Blocks, and images sync to your Braze workspace from Claude. No copy-pasting between tools.
Claude alone vs. Claude with Orbit.
Claude alone
- —Generic marketing advice
- —No structured discovery process
- —Can't connect to Braze
- —Can't build production email HTML
- —No lifecycle-specific frameworks
- —Outputs require manual translation
Claude + Orbit
- ✓Domain-expert lifecycle strategy
- ✓Discovery-first methodology
- ✓Native Braze read + write
- ✓Production MJML/HTML pipeline
- ✓63 specialist skill protocols
- ✓Ready-to-deploy artifacts