Bïrch MCP brings your rule setup, execution logs, and account structure to the AI tools you work with
Claude.ai
On Pro and Max, go to Customize → Connectors. On Team and Enterprise, go to Organization settings → Connectors.
Click + → Add custom connector. Name it Bïrch and paste the URL: https://mcp.bir.ch/mcp. Click Connect.
Sign in with your Bïrch account.
In ChatGPT Web, open Settings → Plugins and switch on Developer mode.
Go to Plugins and create a new one. Name it Bïrch and paste the URL: https://mcp.bir.ch/mcp. Choose OAuth, click Create.
Sign in with your Bïrch account.
Add Bïrch as a remote MCP server. No API key or bearer token needed.
In an interactive session, run /mcp, select birch, and choose Authenticate.
Add Bïrch as a remote MCP server. No API key or bearer token needed.
The login command opens the Bïrch authorization flow. Sign in, approve access, then start a new Codex session.
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.
2 tools · Read-only
List the workspaces the connected user can access, then the ad accounts under a workspace for a given platform.
1 tool · 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).
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.
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.
Rules & logs
list_automation_rules
Lists rules on an ad account — ID, name, level, enabled, check interval, folder. Filterable by folder
Rules & logs
get_rule_details
Full rule logic: tasks (action + condition as prose), schedule, filters, targeted entities
Rules & logs
list_rule_logs
Execution log summaries — when the rule ran, entities evaluated/acted on/errored
Rules & logs
get_rule_log
Detailed per-entity outcomes — actions applied, status changes, condition results, errors. Filterable
Rules & logs
list_rule_folders
Folder tree for automation rules — ID, name, parent_id for subfolders
Workspace & accounts
list_workspaces
Lists all workspaces the user can access, with IDs and currency
Workspace & accounts
list_ad_accounts
Lists ad accounts in a workspace — Birch ID, name, currency, timezone, access status
Stage
list_stage_tasks
Stage tasks — status, progress counts, error messages. Filterable by status and task type
Stage
list_stage_uploads
Creative files uploaded by a Stage task — file name and platform media ID
Stage
list_stage_created_ads
Ads created by a Stage task — ad name, platform ad/adset IDs, creation time
Metrics catalog
search_metrics
Natural-language search of Bïrch's metric catalog — metric ID, label, platform, feature
Help
search_help
Keyword search across Bïrch Help Center articles
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.
A breakdown across six workflows — auditing rules, reading logs, building automation, benchmarking, and more.

Ask your AI to adjust a threshold, update a condition, or disable a stale rule — and approve the change before it takes effect

Ask your AI to upload creatives and create ads across Meta, TikTok, and Snapchat using Stage.
MCP stands for Model Context Protocol — an open standard that lets AI tools connect to external systems and work with their data. Birch MCP uses it to give AI clients read access to your automation rules, execution logs, and account structure.
Anywhere that supports the MCP standard. Claude is the most common client, but any MCP-compatible tool can connect. You add Birch MCP as a connector in your tool's settings, sign in, and it becomes available in that conversation — no need to pick a specific AI client to use it.
They read different things. Meta MCP reads campaign data and reporting from Meta directly. It also has access to Meta Ads library and Meta Help Center. Birch MCP reads your automation rules — the logic that governs how those campaigns are managed inside Birch. You can use both in the same conversation for different stages of your workflow.
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.
Currently it's read-only. Your AI client 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, folder structure, and Stage task metadata. It doesn't see your creative content, billing information, or personal data beyond what's already visible in your Birch workspace.
Birch AI works inside the Birch product. Birch MCP works inside your own AI client — where you might already be talking to your analytics, your project tracker, or your team chat. If your daily workflow lives outside Birch, the MCP brings your automation context to where you already are. They're complementary.
Pressure-test your automation, diagnose what happened overnight, and find the gaps — all from one conversation.