Toffu

Toffu connects Claude to a company's marketing stack: ad accounts (Google Ads, Meta Ads, LinkedIn Ads and others), analytics, content channels and marketing memory.

Read-only tools: get_account_context, query_campaign_performance, list_entities, list_campaigns / list_ad_sets / list_ads, api_request (reads only, writes are refused), creative_report, account_health, get_task_result.

Tools that can make changes, and how each is confirmed:

• propose_* tools (propose_change, propose_create_campaign, propose_update_ad_set, propose_write, ...) store the change and return a preview. Nothing reaches the ad account.
• apply_change and apply_write run one stored proposal. The apply call is the confirmation: the client makes it after showing the user the preview, and the server runs nothing it was not asked to apply. undo_change reverts an applied change within 24 hours.
• All writes are off until a workspace owner or admin turns on MCP write access in Toffu, and server-side budget limits apply to every apply.
• send_message hands a task to the Toffu agent for analysis, reports and drafts. It cannot change ad accounts, publish content, send messages or edit Toffu settings; it returns any proposed change as a draft for the user to apply with propose_* and apply_change.