How do I get my Meta Ads API credentials?

1. Go to **developers.facebook.com** and log in. 2. Click **My Apps** → **Create App**. 3. Select **Business** as the app type. 4. Fill in the app name and connect it to your Business Manager. 5. Add the **Marketing API** product to your app. 6. Go to **Settings → Basic** and copy your **App ID** and **App Secret**. 7. Generate a **System User Access Token** in Business Manager (Business Settings → System Users → Generate Token). 8. Paste all values below. 💡 For production use, submit your app

Can I manage both Facebook and Instagram ads?

Yes. Meta Ads Manager unifies Facebook and Instagram advertising. Your AI agent manages campaigns across both platforms through the same API — including placements in Feed, Stories, Reels, and Messenger.

Can I create lookalike audiences?

Yes. Your AI agent can create lookalike audiences from customer lists, website visitors, or app users — with configurable similarity percentages (1% being most similar, 10% broadest reach).

What conversion metrics can I track?

Track purchases, add-to-cart, initiate checkout, lead submissions, app installs, registrations, page views, and custom conversion events — with attribution windows of 1-day click, 7-day click, and 1-day view.

Meta Ads MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Meta Ads
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Meta Ads through the Vinkius — pass the Edge URL in the `mcps` parameter and every Meta Ads tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Meta Ads Specialist",
    goal="Help users interact with Meta Ads effectively",
    backstory=(
        "You are an expert at leveraging Meta Ads tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Meta Ads "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Meta Ads MCP Server

Connect Meta Ads to your AI agent and manage Facebook and Instagram advertising conversationally.

When paired with CrewAI, Meta Ads becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Meta Ads tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Campaign Management — List, create, update, and pause campaigns, ad sets, and ads across Facebook and Instagram.
Performance Analytics — Pull impressions, reach, clicks, CTR, CPC, CPM, conversions, ROAS, and frequency metrics.
Audience Management — Create custom audiences, lookalikes, and saved audiences with demographic and interest targeting.
Creative Insights — Compare ad creative performance, view thumbnail engagement, and identify winning variants.

The Meta Ads MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Meta Ads to CrewAI via MCP

Follow these steps to integrate the Meta Ads MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 10 tools from Meta Ads

Why Use CrewAI with the Meta Ads MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Meta Ads through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Meta Ads + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Meta Ads MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Meta Ads for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Meta Ads, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Meta Ads tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Meta Ads against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Meta Ads MCP Tools for CrewAI (10)

These 10 tools become available when you connect Meta Ads to CrewAI via MCP:

activate_campaign

Activate a paused campaign

get_account_info

Get ad account details

get_account_insights

Get account-level performance

get_campaign_insights

Get campaign performance metrics

list_ad_sets

List ad sets in a campaign

list_ads

List ads in an ad set

list_audiences

List custom audiences

list_campaigns

List all Meta ad campaigns

list_creatives

List ad creatives

pause_campaign

Can be reactivated later. Pause a campaign

Example Prompts for Meta Ads in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Meta Ads immediately.

"What's my Meta ad spend and ROAS this month?"

"Which ad creatives are performing best?"

"Create a lookalike audience from my top 1000 customers."

Troubleshooting Meta Ads MCP Server with CrewAI

Common issues when connecting Meta Ads to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Meta Ads + CrewAI FAQ

Common questions about integrating Meta Ads MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.