MCP
MCP Server Configuration for Multiple Ad Accounts — Complete 2026 Setup Guide
MCP server configuration for multiple ad accounts lets Claude AI manage 5-50+ Google and Meta advertising accounts simultaneously. Configure once, switch between accounts instantly, and run cross-account analysis from a single interface.
Contents
Autonomous Marketing
Grow your business faster with AI agents
- ✓Automates Google, Meta + 5 more platforms
- ✓Handles your SEO end to end
- ✓Upgrades your website to convert better
What is multi-account MCP server configuration?
Multi-account MCP server configuration for multiple ad accounts is the process of connecting Claude AI to 5-50+ Google Ads and Meta Ads accounts through a single Model Context Protocol (MCP) connection. Instead of configuring separate Claude instances for each client or brand, agencies and enterprises set up one MCP server that authenticates with multiple advertising accounts, then switch between them using simple commands like "switch to Account A" or "analyze all accounts."
The traditional approach requires separate MCP configurations for each account, separate Claude conversations, and manual context switching. With multi-account MCP configuration, you authenticate once, maintain a single conversation thread, and run cross-account analysis like "compare ROAS across all 12 e-commerce clients" or "find the top creative from any account this month." Digital agencies managing 20+ client accounts save 4-6 hours per week on account switching and data aggregation alone.
This works through OAuth delegation and account mapping. The MCP server maintains authentication tokens for each connected account, maps them to friendly names you define ("ClientA_Google", "ClientB_Meta"), and routes Claude's API requests to the correct account based on your current context. Claude remembers which account you are working on and automatically pulls data from the right source until you explicitly switch.
1,000+ Marketers Use Ryze
Automating hundreds of agencies
★★★★★4.9/5
How many ad accounts can you connect to one MCP server?
The practical limit depends on your setup method and API rate limits. Google Ads allows 15,000 API calls per day per developer token, with each account query consuming 1-5 operations. Meta Marketing API limits vary by business verification level but typically allow 200-500 requests per hour per app. Most agencies comfortably manage 25-50 ad accounts through a single MCP configuration without hitting rate limits during normal analysis workflows.
| Setup Method | Max Accounts | Rate Limit | Best For |
|---|---|---|---|
| Ryze MCP Connector | 100+ accounts | Shared enterprise pool | Large agencies, managed service |
| Self-hosted MCP | 25-50 accounts | Your developer token | Mid-size agencies, full control |
| OpenClaw Multi-Client | 10-20 accounts | Standard API limits | Small agencies, open source |
Beyond API limits, performance becomes the constraint. Each additional account adds 50-200ms to cross-account queries as the MCP server must authenticate and fetch data from multiple sources. With 50+ accounts, a query like "show top performers across all accounts" might take 10-20 seconds. Most agencies find 25-30 accounts hits the sweet spot between comprehensive coverage and reasonable response times.
What are the 3 methods for multi-account MCP setup?
Each approach has different tradeoffs between setup complexity, account limits, and ongoing maintenance requirements. The right choice depends on your technical resources and scale requirements.
Method 01
Ryze MCP Connector (Managed)
The managed approach handles all authentication, token refresh, and API optimization automatically. Sign up at get-ryze.ai/mcp, connect each account through OAuth flows, assign friendly names, and get a single MCP configuration that accesses all accounts. Supports 100+ accounts through enterprise API pools with 99.9% uptime SLA. Zero maintenance required.
Best for: Agencies managing 20+ accounts who want zero-maintenance setup. Cost: included in Ryze AI subscription.
Method 02
Self-Hosted MCP Server
Build your own MCP server using Google Ads API and Meta Marketing API SDKs. Configure OAuth2 for each account, store refresh tokens securely, implement account switching logic, and handle rate limiting. Requires Node.js development skills and ongoing server maintenance. Full control over data routing and API usage patterns.
Best for: Technical teams who need custom functionality or data retention controls. Cost: development time + server hosting.
Method 03
OpenClaw Multi-Client
Open-source agent that supports multiple account configurations through JSON config files. Each account needs separate API credentials and authentication setup. Limited to 10-20 accounts due to single-threaded architecture. Good for small agencies who want free solution and don't mind technical setup. See the OpenClaw Google Ads Setup Guide for configuration details.
Best for: Small agencies with 5-15 accounts and technical resources for maintenance. Cost: free (open source).
7-step multi-account MCP configuration guide
This walkthrough uses the Ryze MCP Connector method for fastest setup. For self-hosted setup, see Claude Skills for Google Ads for the technical implementation details. Total time: 15-30 minutes depending on number of accounts.
Step 01
Create Ryze AI account and enable multi-account mode
Sign up at get-ryze.ai/mcp and select "Agency Plan" during onboarding. This enables multi-account features including account switching, cross-account analysis, and bulk operations. Single-account plans don't support the multi-account MCP configuration.
Step 02
Connect your first ad account
In the Ryze dashboard, click "Add Account" > "Google Ads" or "Meta Ads". Complete OAuth authentication and grant read access to campaigns and insights. The system automatically detects all accessible accounts under your login. For Google Ads Manager Accounts, you'll see all sub-accounts listed individually.
Step 03
Assign account names and organize by client
Replace auto-generated names like "123-456-7890" with meaningful labels like "ClientA_Google", "ClientA_Meta", "ClientB_Google". Use consistent naming conventions across accounts. Group related accounts using tags ("Ecommerce", "B2B", "Local") for easier bulk operations later.
Step 04
Add additional accounts
Repeat step 2 for each client account. You can authenticate with different Google/Facebook logins if you have access to accounts under multiple business managers. The MCP server handles token management for all connected accounts automatically, including refresh tokens and permission updates.
Step 05
Configure Claude Desktop with multi-account MCP server
Open Claude Desktop > Settings > MCP Servers. Add the multi-account configuration from your Ryze dashboard:
Step 06
Test account switching
Open a new Claude conversation and test the connection: "List all connected ad accounts." Claude should return your account names, platforms, and connection status. Then test switching: "Switch to ClientA_Google" followed by "Show campaign performance last 7 days."
Step 07
Set up cross-account analysis templates
Create saved prompts for common multi-account workflows: "Weekly performance across all accounts", "Find top creative by ROAS from any account", "Budget allocation recommendations by client". Save these in Claude Projects for quick access. Test with a small subset first before running full cross-account queries.
Ryze AI — Autonomous Marketing
Connect 100+ ad accounts through one MCP configuration
- ✓Automates Google, Meta + 5 more platforms
- ✓Handles your SEO end to end
- ✓Upgrades your website to convert better
2,000+
Marketers
$500M+
Ad spend
23
Countries
How to switch between ad accounts using Claude commands?
Once your multi-account MCP server is configured, Claude maintains context about your current active account and switches seamlessly using natural language commands. The MCP server handles authentication, account validation, and data routing automatically. All subsequent queries pull from the active account until you explicitly switch again.
Basic Account Switching Commands
Switches context to the Google Ads account named "ClientA_Google". All subsequent queries analyze this account.
Displays which account is currently active, platform type, and last data refresh timestamp.
Returns all connected accounts with names, platforms, and connection status.
Advanced Switching Patterns
Claude analyzes performance across accounts and automatically switches to the highest ROAS account.
Combines account switching with immediate analysis in a single command.
If you tagged accounts with "ecommerce", Claude switches through each one and provides summary data.
What cross-account analysis workflows can you automate?
Multi-account MCP configuration unlocks agency-level workflows that are impossible with single-account setups. These queries aggregate data across 5-50+ accounts, identify patterns, and surface insights that individual account analysis misses. The examples below assume you've configured account names and tags as recommended in the setup guide.
Cross-Account Workflow 01
Portfolio Performance Ranking
Rank all connected accounts by ROAS, CPA, and total conversion volume over any time period. Identify which clients are hitting their targets and which need immediate attention. Most agencies run this weekly to prioritize account review time and identify success patterns to replicate across the portfolio.
Cross-Account Workflow 02
Best Creative Discovery
Find the highest-performing creative assets across all accounts, regardless of client or vertical. Extract winning headlines, image concepts, and copy frameworks to test in underperforming accounts. This workflow typically uncovers 2-3 winning creative patterns per month that can be adapted across multiple clients.
Cross-Account Workflow 03
Budget Reallocation Analysis
Identify accounts with excess budget capacity (low impression share, budget-limited campaigns) and accounts that need more investment (high ROAS but limited by budget). Calculate optimal budget shifts across the entire portfolio to maximize total conversions within client constraints.
Cross-Account Workflow 04
Seasonal Pattern Detection
Aggregate performance data across all accounts to identify seasonal trends that might not be visible in individual account data. Detect when CPMs typically spike, which months drive highest conversion rates, and how different verticals respond to seasonal changes. Crucial for annual budget planning and campaign timing.
Sarah K.
Paid Media Manager
E-commerce Agency
Managing 30+ client accounts used to take our team 20 hours per week just for reporting. Now Claude gives us portfolio insights in minutes, and we spend that time on strategy instead of data pulling.”
30+
Accounts managed
20hrs
Weekly time saved
Minutes
For full portfolio insights
Common multi-account MCP configuration issues and fixes
Issue 1: "Account not found" errors during switching. This happens when account names don't match exactly. Account names are case-sensitive and must match exactly as configured. Run "List all accounts" to see correct names, then use exact spelling including underscores and capitalization.
Issue 2: Authentication failures after 7 days. OAuth tokens expire and need refresh. Managed MCP connectors handle this automatically. For self-hosted setups, implement automatic token refresh or manually re-authenticate through your OAuth flow. Log files typically show "401 Unauthorized" errors when tokens expire.
Issue 3: Slow cross-account queries. Queries touching 20+ accounts can take 15-30 seconds. This is normal due to API rate limiting. Speed up by: using account tags to query subsets, running queries during off-peak hours (early morning), or upgrading to enterprise API access with higher rate limits.
Issue 4: Data inconsistencies between accounts. Google Ads and Meta Ads use different attribution models and conversion counting methods. Always specify the reporting platform when making cross-account comparisons: "Compare Google Ads ROAS across all accounts" rather than generic "ROAS comparison."
Issue 5: MCP server memory issues with 50+ accounts. Large account portfolios consume significant memory for token management and data caching. For self-hosted setups, allocate at least 2GB RAM and implement data pagination for large queries. Managed services handle scaling automatically.
Issue 6: Permission errors for Manager Account sub-accounts. Google Ads Manager Accounts require explicit permission grants to each sub-account. In Google Ads, go to Settings > Sub-account access and ensure your user has "Read" access to all accounts you want to connect. Re-authenticate after permission changes.
Frequently asked questions
Q: Can Claude switch between Google Ads and Meta Ads accounts?
Yes. Multi-account MCP configuration supports both platforms simultaneously. You can switch from "ClientA_Google" to "ClientA_Meta" and Claude maintains separate authentication for each platform type.
Q: How many ad accounts can one MCP server handle?
Managed services support 100+ accounts. Self-hosted setups typically handle 25-50 accounts before hitting API rate limits. OpenClaw works well with 10-20 accounts.
Q: Does multi-account configuration cost extra?
Ryze MCP connector includes multi-account features in agency plans. Self-hosted is free but requires development time. Claude Pro subscription ($20/month) works with any MCP configuration.
Q: Can I run reports across all accounts at once?
Yes. Use prompts like "Weekly performance across all accounts" or "Top creatives from any account this month." Cross-account queries take longer but provide portfolio-level insights impossible with single-account setups.
Q: What happens if one account authentication fails?
Claude can still access other connected accounts. The failed account shows "Authentication Error" status and needs re-connection. Cross-account queries exclude failed accounts and show which accounts were included in results.
Q: Can team members share the same multi-account MCP setup?
Yes, but each team member needs their own Claude Pro subscription and MCP configuration. For true team collaboration with shared account access, Ryze AI offers enterprise team features with role-based permissions.
Ryze AI — Autonomous Marketing
Skip the MCP setup — get multi-account management out-of-the-box
- ✓Automates Google, Meta + 5 more platforms
- ✓Handles your SEO end to end
- ✓Upgrades your website to convert better
2,000+
Marketers
$500M+
Ad spend
23
Countries
