Claude Code

One command. Claude Code speaks Streamable HTTP and handles the OAuth flow itself.

#Connect over OAuth (recommended)

claude mcp add marketing-os --transport http --scope user https://marketing-api.keyescode.com/mcp

The first tool call opens your browser. The consent screen asks which organization — and, if you want, which single business — the connection may reach, and whether it may only read or also propose changes. See Scoping.

Check it landed:

claude mcp list

#Connect with an API key instead

For a machine that cannot open a browser. Mint the key under Settings → API Keys in Marketing OS; it is shown once.

claude mcp add marketing-os --transport http --scope user \
  --header "Authorization: Bearer mos_xxxxxxxx" \
  https://marketing-api.keyescode.com/mcp

#Install the skills too

The skills pack bundles this MCP server, so installing the plugin wires the connection for you — you can skip the claude mcp add above entirely:

/plugin marketplace add KeyesCode/marketing-os-skills
/plugin install marketing-os@marketing-os

#First prompts

• "Which of my campaigns is below break-even ROAS this month, and what would you do about it?"
• "Draft me a campaign for the spring promo and show me the plan before anything is created."
• "What does ChatGPT say when someone asks for a business like mine nearby?"

Anything that spends money or leaves Marketing OS comes back as AWAITING APPROVAL and waits in your approvals inbox. That is the design, not a failure — see risk tiers.

#If something goes wrong

The troubleshooting section covers the four things that actually happen: a read-only credential, an admin-only tool, a business-confined key, and a stale sign-in during consent.