Connect Claude to Kitchn.io once. Hand it a brief and a folder of creatives, get a filled launch sheet back. Ask a report for last week's ROAS. Ask why a rule failed. Every ad lands in a sheet you review first.
14 Tage kostenlos testenKeine Kreditkarte nötig
The Kitchn.io connector for Claude is an MCP server. Claude signs in as you. It works with the launch sheets, asset library, reports, rules and automations you see in Kitchn, with your permissions.
Kitchn stays the place where work is reviewed. Claude fills the sheet. You check the rows in the grid and decide what launches.
On claude.ai or in Claude Desktop, open Settings, then Connectors, and add a custom connector with the address https://api.kitchnware.io/mcp.
Claude sends you to the Kitchn sign-in page. Use your Kitchn login, with your two-factor code if you have one set up. No token to copy.
Approve the consent screen. Claude now works as you, with the launch sheets and ad accounts you can reach in Kitchn.
Paste a sheet link and a brief, or ask a question about your accounts. The prompts below are a good first test.
“Fill my Summer Sale sheet with these 12 hooks across the 4 videos in the library. One ad per hook and video.”
“Show me what is in the Summer Sale folder of my Drive and add every vertical video to the sheet, one ad each.”
“Launch the draft ads in the Summer Sale sheet paused and tell me when they are live.”
“Which 5 ads in the Creative Performance report had the best ROAS in the last 7 days, and what did each spend?”
“Which of my rules failed this week, and why?”
“Undo the ads you just added to the Summer Sale sheet.”
Every ad Claude adds is a draft row in a launch sheet you can open. It launches only when you ask, and paused. If the sheet's status default is active, Claude refuses unless you say live spend is intended.
A change to a report, rule or automation comes back as a preview first. Nothing is saved until you agree. Every batch of ads Claude adds can be undone with one request.
Claude cannot change sheet settings, delete sheets, edit live ads or connect ad accounts. Every call lands in your organization's audit log, with who made it and which tool ran.
Kitchn's permissions still apply. Claude reaches only the sheets and ad accounts the signed-in user can reach. Admins can connect. A team member needs the MCP right, which an admin grants under Settings → Users. Guests never connect.
Yes. Kitchn.io has an MCP connector for Claude. It works on claude.ai, Claude Desktop and Claude Code. On claude.ai and Claude Desktop you sign in with your Kitchn login. Claude Code uses an MCP token.
Yes, through a Kitchn launch sheet. Claude adds the ads to a Meta sheet as drafts, you review them in Kitchn, and on your request it launches them paused. The same works on every launch channel. Meta, TikTok, Google Demand Gen, Pinterest and Snapchat, plus LinkedIn, Spotify and AppLovin in beta.
What you can see. The launch sheets you can open, the asset library, your reports, rules and automations. Admins also get the organization's launch counts, adoption per ad account and team utilization. Saved credentials and secrets are never returned.
Admins can connect right away. A team member needs the MCP right, which an admin grants under Settings → Users in Kitchn. Removing the right cuts the connection on the next request. Guests can never connect.
With an MCP token. Generate one under Settings → MCP in Kitchn, then add https://api.kitchnware.io/mcp to your client with the header Authorization: Bearer and your token. Tokens expire on the date you pick and can be revoked at any time.
Yes, as a custom connector. Turn on developer mode in ChatGPT, add the connector address, choose OAuth and leave the client ID and secret empty. ChatGPT registers itself and sends you to the Kitchn sign-in.
The connector is in beta and switched on per organization. If you do not see Settings → MCP in Kitchn, ask your Kitchn contact to switch it on.
Geh mit uns die Workflows deines Teams durch.
14 Tage kostenlos testenKeine Kreditkarte nötig