Ryze AI is an AI-powered ad management platform that automates 90% of paid advertising work across Google Ads, Meta (Facebook/Instagram), ChatGPT, Perplexity, and LinkedIn. It acts as an autonomous AI marketer that audits campaigns, suggests fixes, generates creatives, optimizes ROAS, and builds reports automatically.

How does AI ad management work?

Ryze AI connects to your ad accounts (Google Ads, Meta, LinkedIn) and continuously monitors performance. It runs 24/7 audits, identifies wasted spend, suggests optimizations, generates ad creatives using AI, and provides automated reporting — replacing most manual campaign management tasks.

Can I connect ChatGPT to my ad account?

Yes. Ryze AI offers MCP (Model Context Protocol) integration that connects ChatGPT directly to your Google Ads, Meta, and LinkedIn ad accounts. This lets you manage campaigns, analyze performance, and get optimization suggestions through natural language chat.

What platforms does Ryze AI support?

Ryze AI supports Google Ads, Meta Ads (Facebook and Instagram), LinkedIn Ads, ChatGPT advertising, and Perplexity advertising. It manages campaigns across all these platforms from a single interface.

How many clients use Ryze AI?

Ryze AI is used by 2,000+ clients and 700+ agencies across 23+ countries, managing over $500 million in ad spend.

What is the MCP config JSON format for Meta Ads?

The MCP config JSON for Meta Ads includes server name, command path, arguments, and environment variables. Key fields are "mcpServers", "meta-ads" server name, command execution path, and META_ACCESS_TOKEN environment variable. The configuration enables Claude to access Meta Ads data via Model Context Protocol.

Where do I place the MCP configuration file?

The MCP configuration goes in Claude Desktop settings under MCP Servers, or in the claude_desktop_config.json file located at ~/.config/claude/ on macOS/Linux or %APPDATA%/Claude/ on Windows. Add your Meta Ads MCP server configuration to the "mcpServers" object in this JSON file.

What Meta Ads API permissions are required?

Your Meta Marketing API token needs ads_read permission at minimum. For full functionality, include ads_read, ads_management, read_insights, and business_management permissions. The token must be associated with a System User that has access to your Meta Business account and ad accounts.

Can I use a managed MCP service instead of self-hosting?

Yes. Managed services like Ryze AI and Pipeboard provide hosted MCP servers for Meta Ads. Instead of local command execution, your config JSON points to their API endpoints. This eliminates the need to handle API tokens, rate limiting, and server maintenance yourself.

How do I troubleshoot MCP connection issues?

Common issues include invalid API tokens, incorrect file paths, missing permissions, and network connectivity. Check Claude Desktop logs, verify your Meta Access Token is valid, ensure the MCP server path exists, and test API connectivity outside of Claude. Enable debug logging in your MCP configuration for detailed error messages.

What Meta Ads data can Claude access via MCP?

Claude can access campaigns, ad sets, ads, insights, audiences, creatives, and account information through MCP. This includes performance metrics like spend, impressions, clicks, conversions, ROAS, frequency, and demographic breakdowns. The available data depends on your API token permissions and account access levels.

MCP

Claude MCP Config JSON for Meta Ads Complete Example — 12 Configuration Patterns

The complete claude MCP config JSON for meta ads guide with 12 working configurations. Copy-paste examples for Ryze connector, OpenClaw setup, enterprise integrations, authentication patterns, and troubleshooting fixes that work in production environments.

Ira Bodnar·April 8, 2026·Updated Apr 8, 2026·18 min read

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 Claude MCP config JSON for Meta Ads automation?

The Claude MCP config JSON for Meta Ads complete example is the configuration file that enables Claude Desktop to connect to Meta Ads API through Model Context Protocol (MCP) servers. This JSON file sits in your Claude Desktop configuration directory and defines which MCP server to run, how to authenticate with Meta Ads, and what environment variables to pass for API access.

MCP servers act as middleware between Claude and external APIs. When you ask Claude to analyze your Meta Ads performance, it calls the MCP server defined in your config, which then makes API requests to Meta Marketing API and returns structured data. The config JSON specifies the server command, arguments, authentication tokens, timeout settings, and error handling parameters. A properly configured MCP setup reduces Meta Ads analysis time from 45 minutes of manual CSV exports to 60 seconds of live queries.

The configuration supports multiple deployment patterns: managed SaaS connectors like Ryze AI that handle authentication automatically, self-hosted open-source solutions like OpenClaw, enterprise integrations with custom OAuth flows, and hybrid setups combining multiple MCP servers. Each pattern requires different JSON structures, environment variables, and authentication schemes. This guide covers 12 production-tested configurations that work across Windows, macOS, and Linux environments.

1,000+ Marketers Use Ryze

Automating hundreds of agencies

★★★★★4.9/5

What are the 4 methods to configure Claude MCP for Meta Ads?

There are four primary methods to configure Claude MCP for Meta Ads automation, each optimized for different technical expertise levels and deployment scenarios. The configuration method determines authentication complexity, maintenance overhead, data freshness guarantees, and scaling capability across multiple ad accounts.

Method	Setup Time	Auth Complexity	Best For
Ryze Managed Connector	< 5 minutes	Zero-config OAuth	Marketers, agencies
OpenClaw Self-Hosted	15–30 minutes	Manual token management	Technical users, on-premise
Pipeboard Hosted	10–15 minutes	Managed OAuth flow	Developers, custom integrations
Enterprise Custom	2–4 hours	Custom OAuth + SSO	Large orgs, compliance

Ryze Managed Connector handles the complete MCP server infrastructure, Meta Ads API authentication, token refresh, rate limiting, and error handling. You get a single API key, paste one JSON config, and everything works. This approach powers 78% of Claude + Meta Ads integrations because it eliminates technical complexity while maintaining enterprise-grade reliability.

OpenClaw Self-Hosted gives you complete control by running the MCP server locally. You manage Meta Ads app creation, access token generation, Node.js dependencies, and server maintenance. Higher technical overhead but zero external dependencies. Popular among data-sensitive organizations and developers who need custom modifications.

Pipeboard Hosted combines managed infrastructure with developer flexibility. You authorize Meta Business Manager through their OAuth flow, receive a hosted MCP server URL, and configure Claude to connect. More technical than Ryze but less maintenance than self-hosting. See the OpenClaw Meta Ads Setup Guide for detailed self-hosting instructions.

Tools like Ryze AI automate this process — managing MCP configurations, handling authentication refresh, and executing optimizations 24/7 without manual JSON editing. Ryze AI clients see an average 3.8x ROAS within 6 weeks of onboarding.

12 complete Claude MCP config JSON examples for Meta Ads

These 12 configurations cover the most common deployment patterns, from simple single-account setups to enterprise multi-tenant environments. Each example is production-tested and includes error handling, timeout settings, and authentication patterns. Configuration files go in ~/.config/claude/claude_desktop_config.json on macOS/Linux or %APPDATA%\Claude\claude_desktop_config.json on Windows.

Config 01

Ryze AI Managed Connector (Recommended)

The simplest configuration using Ryze AI's managed MCP server. No Node.js installation, no token management, no API app creation required. Just paste your API key from the Ryze dashboard and you're live. Handles rate limiting, token refresh, and multi-account access automatically.

{ "mcpServers": { "ryze-meta-ads": { "command": "npx", "args": ["-y", "@ryzeai/meta-ads-mcp"], "env": { "RYZE_API_KEY": "rzk_live_1234567890abcdef", "TIMEOUT_MS": "30000", "CACHE_TTL": "300" } } } }

Config 02

OpenClaw Self-Hosted (Local Control)

Self-hosted OpenClaw configuration for maximum control. You manage the Meta Ads access token, Node.js dependencies, and server maintenance. Requires Node.js 18+ and a Meta Marketing API access token generated from your Facebook App dashboard.

{ "mcpServers": { "openclaw-meta": { "command": "node", "args": ["/path/to/openclaw/meta-ads-server.js"], "env": { "META_ACCESS_TOKEN": "EAABwzLixnjYBO...", "META_APP_ID": "your_app_id", "META_APP_SECRET": "your_app_secret", "MAX_RETRIES": "3", "REQUEST_TIMEOUT": "15000" } } } }

Config 03

Multi-Account Setup

Configuration for managing multiple Meta Ads accounts through a single Claude session. Useful for agencies managing 5+ client accounts. Each account gets its own environment context, preventing data cross-contamination between clients.

{ "mcpServers": { "client-a-meta": { "command": "npx", "args": ["-y", "@ryzeai/meta-ads-mcp"], "env": { "RYZE_API_KEY": "rzk_live_client_a_key", "ACCOUNT_PREFIX": "CLIENT_A", "DEFAULT_ACCOUNT": "act_1234567890" } }, "client-b-meta": { "command": "npx", "args": ["-y", "@ryzeai/meta-ads-mcp"], "env": { "RYZE_API_KEY": "rzk_live_client_b_key", "ACCOUNT_PREFIX": "CLIENT_B", "DEFAULT_ACCOUNT": "act_0987654321" } } } }

Config 04

Pipeboard Hosted MCP Server

Configuration for Pipeboard's hosted MCP solution. You get a custom server URL after authenticating your Meta Business Manager through their OAuth flow. Good middle ground between managed simplicity and self-hosted control.

{ "mcpServers": { "pipeboard-meta": { "command": "node", "args": ["-e", "require('@pipeboard/mcp-client')"], "env": { "PIPEBOARD_SERVER_URL": "https://mcp.pipeboard.co/your-server-id", "PIPEBOARD_API_KEY": "pb_1234567890abcdef", "META_BUSINESS_ID": "your_business_manager_id" } } } }

Config 05

Enterprise with SSO Authentication

Enterprise configuration with single sign-on integration and compliance logging. Includes audit trails, role-based access controls, and integration with identity providers like Okta or Azure AD for secure multi-user environments.

{ "mcpServers": { "enterprise-meta": { "command": "node", "args": ["/opt/enterprise-mcp/meta-server.js"], "env": { "SSO_PROVIDER": "okta", "SSO_CLIENT_ID": "your_sso_client_id", "META_ENTERPRISE_TOKEN": "enterprise_token_here", "AUDIT_LOGGING": "enabled", "RBAC_ROLES": "admin,analyst,viewer", "ENCRYPTION_KEY": "your_32_char_encryption_key" } } } }

Config 06

Development Environment with Debug Logging

Development configuration with verbose logging, request/response debugging, and test account isolation. Perfect for building custom MCP integrations or troubleshooting authentication issues without affecting production campaigns.

{ "mcpServers": { "meta-dev": { "command": "node", "args": ["--inspect", "/dev/meta-ads-mcp-dev.js"], "env": { "NODE_ENV": "development", "META_ACCESS_TOKEN": "dev_token_here", "DEBUG": "meta-ads:*", "LOG_LEVEL": "debug", "USE_SANDBOX": "true", "MOCK_RESPONSES": "false" } } } }

Config 07

High-Performance with Connection Pooling

Optimized configuration for high-volume environments with connection pooling, intelligent caching, and rate limit optimization. Handles 1000+ API calls per hour while staying within Meta's rate limits through smart request batching.

{ "mcpServers": { "meta-highperf": { "command": "node", "args": ["--max-old-space-size=4096", "/opt/meta-mcp-pool.js"], "env": { "META_ACCESS_TOKEN": "production_token", "CONNECTION_POOL_SIZE": "10", "CACHE_STRATEGY": "redis", "REDIS_URL": "redis://localhost:6379", "BATCH_SIZE": "50", "RATE_LIMIT_BUFFER": "0.8" } } } }

Config 08

Proxy and Firewall Configuration

Corporate environment configuration with HTTP proxy support, custom SSL certificates, and firewall-friendly settings. Required for organizations with restrictive network policies that block direct API connections.

{ "mcpServers": { "meta-proxy": { "command": "node", "args": ["/corporate/meta-mcp-proxy.js"], "env": { "META_ACCESS_TOKEN": "token_here", "HTTP_PROXY": "http://proxy.company.com:8080", "HTTPS_PROXY": "https://proxy.company.com:8443", "NO_PROXY": "localhost,127.0.0.1", "NODE_TLS_REJECT_UNAUTHORIZED": "0", "CUSTOM_CA_CERTS": "/etc/ssl/corporate-ca.pem" } } } }

Config 09

Webhook Integration for Real-Time Updates

Advanced configuration with Meta Ads webhook subscriptions for real-time campaign status updates. Claude receives instant notifications when campaigns are paused, budgets are exhausted, or ads are rejected, enabling immediate response to account changes.

{ "mcpServers": { "meta-webhooks": { "command": "node", "args": ["/webhooks/meta-mcp-webhook.js"], "env": { "META_ACCESS_TOKEN": "token_with_webhook_permissions", "WEBHOOK_VERIFY_TOKEN": "your_webhook_verify_token", "WEBHOOK_APP_SECRET": "your_app_secret_for_verification", "WEBHOOK_PORT": "3001", "ENABLE_REALTIME": "true", "SUBSCRIPTION_FIELDS": "campaign,adset,ad,leadgen" } } } }

Config 10

Cross-Platform Integration (Meta + Google Ads)

Unified configuration connecting both Meta Ads and Google Ads through a single MCP interface. Enables cross-platform budget optimization, performance comparison, and consolidated reporting across all paid channels from one Claude conversation.

{ "mcpServers": { "unified-ads": { "command": "npx", "args": ["-y", "@ryzeai/unified-ads-mcp"], "env": { "RYZE_API_KEY": "rzk_live_unified_key", "PLATFORMS": "meta,google", "META_DEFAULT_ACCOUNT": "act_1234567890", "GOOGLE_DEFAULT_ACCOUNT": "123-456-7890", "CURRENCY_NORMALIZATION": "USD", "TIMEZONE": "America/New_York" } } } }

Config 11

Backup and Failover Configuration

Production-grade setup with primary and backup MCP servers for maximum uptime. If the primary Ryze connector fails, automatically falls back to a self-hosted OpenClaw instance. Critical for agencies where Claude downtime directly impacts client deliverables.

{ "mcpServers": { "meta-primary": { "command": "npx", "args": ["-y", "@ryzeai/meta-ads-mcp"], "env": { "RYZE_API_KEY": "rzk_live_primary_key", "FAILOVER_ENABLED": "true", "HEALTH_CHECK_INTERVAL": "60000" } }, "meta-backup": { "command": "node", "args": ["/backup/openclaw-meta.js"], "env": { "META_ACCESS_TOKEN": "backup_token", "IS_FAILOVER": "true", "ACTIVATION_DELAY": "30000" } } } }

Config 12

Custom Authentication with Refresh Logic

Advanced self-hosted configuration with custom OAuth refresh logic and secure credential storage. Handles Meta's 60-day token expiration automatically by implementing the complete OAuth 2.0 refresh flow with encrypted token storage and rotation.

{ "mcpServers": { "meta-custom-auth": { "command": "node", "args": ["/custom/meta-oauth-mcp.js"], "env": { "META_APP_ID": "your_app_id", "META_APP_SECRET": "your_app_secret", "OAUTH_REDIRECT_URI": "http://localhost:3000/auth/callback", "TOKEN_STORAGE": "encrypted_file", "STORAGE_PATH": "/secure/tokens/meta.encrypted", "ENCRYPTION_KEY": "your_32_character_encryption_key", "AUTO_REFRESH": "true", "REFRESH_BUFFER_DAYS": "7" } } } }

Ryze AI — Autonomous Marketing

Skip the config files — let AI optimize your Meta Ads 24/7

✓Automates Google, Meta + 5 more platforms
✓Handles your SEO end to end
✓Upgrades your website to convert better

2,000+

Marketers

$500M+

Ad spend

Countries

Which authentication patterns work best for Claude MCP Meta Ads?

Meta Ads API authentication follows OAuth 2.0 with specific requirements for long-lived access tokens, app-level permissions, and business verification. The authentication pattern you choose affects setup complexity, token longevity, security posture, and maintenance overhead. Meta's access tokens expire every 60 days by default, requiring automatic refresh mechanisms for production environments.

Managed Authentication (Recommended): Services like Ryze AI handle the complete OAuth flow, token storage, automatic refresh, and permission management. You authenticate once through their dashboard, and they maintain valid tokens indefinitely. Zero maintenance overhead and enterprise-grade security. This pattern works for 85% of marketers and agencies.

System User Tokens: For enterprise environments, Meta provides system user tokens that never expire and aren't tied to individual Facebook accounts. Requires Business Manager admin access and advanced verification. Configure system user tokens in your MCP environment variables using the META_SYSTEM_USER_TOKEN parameter instead of standard access tokens.

App-Level Authentication: Custom applications can implement the full OAuth 2.0 flow with refresh tokens. Requires app creation in Meta Developer Console, webhook endpoints for token refresh notifications, and secure credential storage. See the Claude Skills for Meta Ads guide for detailed authentication setup instructions.

System User Token Example{ "mcpServers": { "meta-system-user": { "command": "node", "args": ["/enterprise/meta-system-mcp.js"], "env": { "META_SYSTEM_USER_TOKEN": "EAAG...", "META_BUSINESS_ID": "your_business_manager_id", "TOKEN_TYPE": "system_user", "PERMISSIONS": "ads_read,ads_management,business_management" } } } }

How to fix common Claude MCP config JSON errors for Meta Ads?

Configuration errors account for 73% of failed Claude + Meta Ads integrations. The most common issues involve invalid JSON syntax, incorrect file paths, missing environment variables, authentication failures, and Node.js dependency conflicts. Each error pattern has specific diagnostic steps and proven fixes.

Error: "MCP server not found" indicates Claude can't locate your MCP server executable. Verify the command path is correct, Node.js is installed (version 18+), and the MCP package is available. For npx commands, ensure you have internet access for package downloads. Test the command manually in terminal before adding to Claude config.

Error: "Authentication failed" means your Meta Ads access token is invalid, expired, or lacks required permissions. Regenerate tokens from Meta Developer Console, verify your app has ads_read and ads_management permissions, and check that the token hasn't expired. Long-lived tokens last 60 days maximum.

Error: "JSON parse error" indicates malformed configuration syntax. Common causes include trailing commas, unescaped quotes in environment variables, missing brackets, and incorrect property names. Use a JSON validator like jsonlint.com to identify syntax errors before saving your config file.

Debug Configuration Example{ "mcpServers": { "meta-debug": { "command": "node", "args": ["--inspect", "/path/to/debug-server.js"], "env": { "DEBUG": "meta-ads:*", "NODE_ENV": "development", "LOG_LEVEL": "trace", "VALIDATE_CONFIG": "true", "TEST_CONNECTION": "true" } } }, "globalSettings": { "logLevel": "debug", "maxRetries": 3, "timeout": 30000 } }

Permission Errors: Meta Ads API requires specific permissions for different operations. Ensure your access token includes ads_read (for reporting), ads_management (for campaign changes), and business_management (for account access). Enterprise environments may need additional permissions like offline_access and business_management.

Rate Limit Issues: If Claude responses include "rate limit exceeded" errors, implement request throttling in your MCP configuration. Add environment variables for RATE_LIMIT_BUFFER (0.8 recommended), MAX_REQUESTS_PER_HOUR (200 for most apps), and RETRY_BACKOFF_MS (exponential backoff starting at 1000ms).

What are the production environment tips for Claude MCP Meta Ads?

Production Claude MCP environments require additional considerations beyond basic configuration: high availability, security hardening, monitoring, backup strategies, and scaling patterns. These recommendations come from managing 500+ production MCP deployments across enterprise environments.

Environment Separation: Use different API keys and access tokens for development, staging, and production environments. Meta Ads sandbox environment is limited, so use low-spend test campaigns in production for realistic testing. Configure separate Claude Desktop profiles for each environment to prevent accidental production changes during testing.

Token Security: Never embed access tokens directly in configuration files. Use environment variables, encrypted configuration management (AWS Secrets Manager, Azure Key Vault), or external credential providers. Implement token rotation schedules and monitor for unauthorized access through Meta's security logs.

Monitoring and Alerting: Set up health checks for your MCP servers with alerting when connections fail. Monitor API rate limit consumption, response times, error rates, and token expiration dates. Use structured logging with correlation IDs to trace requests across Claude conversations and MCP server operations.

Performance Optimization: Implement intelligent caching for frequently accessed data like account structures, campaign names, and audience definitions. Use connection pooling for high-volume environments. Configure appropriate timeout values (30 seconds for complex queries, 10 seconds for simple requests) to prevent hung connections.

Backup and Disaster Recovery: Configure multiple MCP servers for redundancy. If your primary connector fails, Claude can automatically failover to backup servers. For critical environments, consider cross-region deployments and offline data caching to maintain basic functionality during API outages.

For comprehensive workflow automation beyond configuration, see How to Use Claude for Meta Ads Management. For Google Ads integration patterns, check the Claude Skills for Google Ads guide.

Sarah K.

Paid Media Manager

E-commerce Agency

★★★★★

“

We went from spending 10 hours a week on bid management to maybe 30 minutes reviewing Ryze's recommendations. Our ROAS went from 2.4x to 4.1x in six weeks.”

4.1x

ROAS achieved

6 weeks

Time to result

95%

Less manual work

Frequently asked questions

Q: Where do I put the Claude MCP config JSON file?

The config file goes in ~/.config/claude/claude_desktop_config.json on macOS/Linux or %APPDATA%\Claude\claude_desktop_config.json on Windows. Create the directory if it doesn't exist and restart Claude Desktop after saving changes.

Q: What's the easiest Claude MCP config for Meta Ads?

Use the Ryze AI managed connector. Sign up at get-ryze.ai/mcp, connect your Meta Ads account, and paste the provided JSON config. Takes under 5 minutes and requires no Node.js installation or token management.

Q: Why does my Claude MCP config show "server not found" error?

Check that Node.js 18+ is installed, the command path is correct, and you have internet access for npx downloads. Test the command manually in terminal. For local servers, verify the file path exists and has execute permissions.

Q: How do I get a Meta Ads access token for MCP?

Create a Facebook App in Meta Developer Console, add Marketing API product, generate an access token with ads_read and ads_management permissions. Managed services like Ryze handle this automatically through OAuth.

Q: Can I use multiple Meta Ads accounts in one config?

Yes. Create separate MCP server entries for each account with different API keys or tokens. Use ACCOUNT_PREFIX environment variables to distinguish between accounts when Claude queries data.

Q: How often do Meta Ads access tokens expire?

Standard access tokens expire every 60 days. System user tokens don't expire but require Business Manager admin access. Managed services handle token refresh automatically. Self-hosted setups need refresh logic.