Bïrch automation pauses underperformers, scales winners, and controls budgets — now with AI recommendations that surface new opportunities. You stay in control of every decision
5 tools · Read-only
The core of the read surface. List a workspace's automation rules (with optional folder filtering) and their folder structure, pull one rule's full logic in prose (conditions, schedule, filters, targeted entities), then list its execution history and drill into one run to see exactly which entities matched, what fired, and any errors.
list_automation_rules
list_rule_folders
get_rule_details
list_rule_logs
get_rule_log
2 tools · Read-only
List the workspaces the connected user can access, then the ad accounts under a workspace for a given platform.
list_workspaces
list_ad_accounts
2 tools · Read-only
Resolve a metric by natural-language description to its canonical id, or list a workspace's custom metric formulas (with the underlying expression, not just the name).
search_metric
list_custom_metrics
3 tools · Read-only
Check Stage task status (upload vs. create, progress, failure reason), see which files a task uploaded and their platform media IDs, and list the ads a create task actually produced.
list_stage_tasks
list_stage_uploads
list_stage_created_ads
1 tool · Read-only
Keyword/semantic search over the Birch help center, so an AI client can answer product questions from real docs instead of guessing.
search_help
Assistant inside the Birch product. It reads your rules and account data and helps you work faster without leaving Birch.
Brings your real data to Claude and other AI clients. Use it when you’re already working in Claude — alongside your other connected tools. You don’t have to switch to Birch to understand what your automation did.
MCP stands for Model Context Protocol. It's an open standard that lets AI tools like Claude connect to external systems and work with their data. Birch MCP uses it to give Claude read access to your automation rules, execution logs, and account structure.
They read different things. Meta MCP reads campaign data and reporting. Birch MCP reads automation rules — the logic that governs how campaigns are managed. You can use both together in the same Claude conversation.
No. You add Birch MCP in your AI client's connector settings, sign in with your Birch account, and you're connected. No API keys, no code.
No. It's read-only. Your AI tool can see your automation setup and report on what it finds, but it cannot create, edit, or delete anything. When you want to make a change, you make it in Birch.
Your workspaces, ad accounts, rule configurations (conditions, thresholds, schedules, actions), execution logs, and folder structure. It does not see your ad creative, billing information, or personal data beyond what's visible in your Birch workspace.
Birch AI works inside the Birch product. Birch MCP works inside Claude and other AI clients. If you already use Claude alongside other tools for your daily workflow, the MCP keeps your automation context in the same place. They're complementary.
Pressure-test your automation, diagnose what happened overnight, and find the gaps — all from one conversation.

Choose from more than 20 actions and combine multiple actions in a single automation. Pause an ad, send a Slack notification, and adjust the budget, all from one rule triggered by one condition set.

Build sophisticated logic using AND/OR operators to group conditions. Target exactly the scenarios you care about, without creating a dozen separate rules to cover the same ground.
Create conditions based on an item's relative performance rather than absolute numbers. Protect your top performers or act on your weakest, automatically.
Compare any metric against another metric, not just against a static number. Measure this week's CPA against last week's, or compare an ad set's ROAS to the campaign average, across the same or different timeframes.
Define the exact performance windows you care about, beyond the presets native ad platforms offer.
Build your own metrics as calculated formulas or as static variables, and use them as thresholds in your automation rules.
Get alerts via email or Slack when automations fire. Every action is logged with full transparency, showing exactly why each item was or wasn't affected.
Connect external data sources — Google Sheets, Google Analytics, and attribution tools like Hyros, AppsFlyer, Adjust, and Wicked Reports — and use their data as a live input to your automation rules, enabling strategies that go beyond what in-platform data alone allows.