Claude Desktop and claude.ai

No config file. Claude walks the OAuth flow itself.

#Connect

1. Settings → Connectors → Add custom connector.

2. Paste the endpoint:

   https://marketing-api.keyescode.com/mcp

3. Claude opens the consent screen. Pick the organization, optionally narrow it to a single business, and choose Read only or Read and propose changes.

That is the whole setup. The tools appear in the next conversation.

#An API key instead

Claude Desktop's connector UI has no header field, so OAuth is the path here. If you need a static credential — a shared agent, a server — use a client that accepts headers, such as Claude Code or Cursor.

#Add the skills

Connecting gives Claude the tools; the skills pack teaches it what good looks like. Build the per-skill ZIPs with sh skills/scripts/build-zips.sh and upload them under Settings → Capabilities → Skills.

#First prompts

• "List my businesses and tell me which one is furthest from its target CPA."
• "Audit last month's paid performance and tell me the three things you would change."

#If something goes wrong

"Sign in to Marketing OS first" during consent — the consent screen reads your normal Marketing OS session. Open the app, sign in, press Continue. The rest is in troubleshooting.