Use Reeve in Claude
Access your Reeve marketing workspace from inside Claude via the Reeve MCP server.
Use Reeve in Claude
Connect Reeve to Claude and talk to your marketing workspace without leaving your Claude conversation. Ask Reeve to draft copy, pull CRM contacts, check ad performance, browse render presets, or run campaigns — all through natural conversation.
What this gives you
Once connected, Claude gets two ways to work with Reeve: the brain (chat) for orchestrated, creative work, and a growing set of direct tools for fast, deterministic reads — CRM, credits, commerce, connections, ads, video, and knowledge.
| What you can do | How |
|---|---|
| Draft copy, emails, and ad creatives | Ask Claude; it sends the request to Reeve's chat |
| Look up CRM contacts, ad performance, credit balance, render status | Claude calls a direct tool (e.g. crm_list_contacts, ads_list_insights) |
| Discover what else is possible | Claude calls list_tools/describe_tools to browse and inspect tools it hasn't used yet |
| Scope a conversation to a specific brand | Claude calls get_context to list your brands, then passes the id |
| Launch paid spend or publish content | Reeve returns a gate — you approve it before anything happens |
Gates: spending and publishing require your approval
Reeve never spends your budget or publishes content without explicit approval. When a write action is triggered, Reeve returns a gate — a pending action (pending_approval with a gate_id) that requires your sign-off. Claude will surface the gate details and ask you to confirm before calling resolve_gate to approve it. Reads (looking things up) never gate — they run immediately.
This mirrors how Reeve works in the web app: every significant action asks for your approval before it commits.
Works with your brands
If you manage multiple brands in Reeve, you can scope any conversation to a specific brand. Claude calls get_context to fetch your brand list, then passes the brand's id to chat. Without a brand_id, Reeve defaults to your primary workspace.
Existing connector? If you connected Reeve to Claude before this surface shipped, your connection keeps working unchanged at the legacy /mcp/claude endpoint — see Connect Reeve to Claude for the distinction. New connections should use /mcp.