How do I find my AppsFlyer API Token V2?

Log in to AppsFlyer as an Admin, go to **Security Center** from the account menu, and navigate to **AppsFlyer API tokens**. There you can manage and copy your V2 token (JWT).

The `appId` is the unique identifier for your app in the store. For iOS, it's usually `id` followed by numbers (e.g., `id123456789`). For Android, it's the package name (e.g., `com.example.app`).

Is there a limit on the number of rows returned?

Yes, AppsFlyer Pull API limits raw data reports to 200,000 rows. If your data exceeds this, try narrowing the date range of your request.

AppsFlyer (Pull API) MCP Server for CrewAI 7 tools — connect in under 2 minutes

Name: AppsFlyer (Pull API)
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 7 Tools Framework

Connect your CrewAI agents to AppsFlyer (Pull API) through Vinkius, pass the Edge URL in the `mcps` parameter and every AppsFlyer (Pull API) 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="AppsFlyer (Pull API) Specialist",
    goal="Help users interact with AppsFlyer (Pull API) effectively",
    backstory=(
        "You are an expert at leveraging AppsFlyer (Pull API) 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 AppsFlyer (Pull API) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 7 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 AppsFlyer (Pull API) MCP Server

The AppsFlyer Pull API MCP Server provides your AI agent with direct access to your mobile attribution and marketing analytics data. Effortlessly retrieve raw reports for installs and in-app events, or get aggregate performance metrics by day, geography, or media source using natural language.

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

Key Features

Raw Data Retrieval — Download non-organic installs, in-app events, and uninstalls reports for granular analysis.
Aggregate Reporting — Access high-level performance summaries by partner (media source), geography, or day.
Customizable Timeframes — Specify exact start and end dates for any report to focus on specific campaigns or periods.
CSV Output Support — Reports are delivered in structured CSV format, allowing for further data processing or direct review.
Security & Privacy — Uses AppsFlyer API Token V2 (JWT) for secure, authenticated access to your data.

The AppsFlyer (Pull API) MCP Server exposes 7 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 AppsFlyer (Pull API) to CrewAI via MCP

Follow these steps to integrate the AppsFlyer (Pull API) 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 7 tools from AppsFlyer (Pull API)

Why Use CrewAI with the AppsFlyer (Pull API) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with AppsFlyer (Pull API) 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 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

AppsFlyer (Pull API) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the AppsFlyer (Pull API) MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries AppsFlyer (Pull API) 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 AppsFlyer (Pull API), analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain AppsFlyer (Pull API) 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 AppsFlyer (Pull API) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

AppsFlyer (Pull API) MCP Tools for CrewAI (7)

These 7 tools become available when you connect AppsFlyer (Pull API) to CrewAI via MCP:

get_account_check

Verify AppsFlyer account connection

get_daily_report

Get aggregate daily performance report

get_geo_report

Get aggregate performance report by geography

get_in_app_events_report

Get in-app events raw data report

get_installs_report

Get non-organic installs raw data report

get_partners_report

Get aggregate performance report by media source

get_uninstalls_report

Get uninstalls raw data report

Example Prompts for AppsFlyer (Pull API) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with AppsFlyer (Pull API) immediately.

"Get the installs report for last week."

"Show me the aggregate daily performance for February 2024."

"Retrieve in-app events data for today."

Troubleshooting AppsFlyer (Pull API) MCP Server with CrewAI

Common issues when connecting AppsFlyer (Pull API) 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

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

AppsFlyer (Pull API) + CrewAI FAQ

Common questions about integrating AppsFlyer (Pull API) 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.