How to Use the Criteo Retail Media API MCP in CrewAI

Deploy autonomous CrewAI agents to monitor and analyze your Criteo ad campaigns.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Criteo Retail Media API MCP to CrewAI

Create your Vinkius account to connect Criteo Retail Media API to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Criteo Retail Media API with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous Criteo MCP Server Squads

This server gives your CrewAI teams direct access to live ad data. A designated monitoring agent can run `list_retail_campaigns` every hour to watch for unexpected drops in traffic. When an anomaly appears, the monitor passes the ID to an analyst agent. That second agent calls `get_retail_campaign_details` to inspect the targeting settings and figure out what went wrong.

Track Spend Across Accounts

Delegating financial oversight to an AI crew frees up your media buyers. You can assign a specific agent to execute `list_retail_budgets` and check pacing across all active accounts. Digging into the actual return on ad spend requires deeper data. The same agent triggers `get_retail_media_report` to compare those budget limits against actual sales performance.

Analyze Search Terms

Research agents can map out exactly how your products are being found using this MCP integration. They start by calling `list_line_items` to grab the ad groups, then run `list_line_item_keywords` to extract the exact search terms. Cross-referencing those terms with available inventory is critical for strategy. The crew uses `list_account_products` alongside `list_advertiser_accounts` to ensure you actually have the stock to support the targeted keywords.

Setup guide

Set up Criteo Retail Media API MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Criteo Retail Media API tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Criteo Retail Media API Analyst",
    goal="Access and analyze Criteo Retail Media API data via MCP.",
    backstory="Expert analyst with direct Criteo Retail Media API access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Criteo Retail Media API transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

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

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Criteo Retail Media API Analyst",
        goal="Access and analyze Criteo Retail Media API data via MCP.",
        backstory="Expert analyst with direct Criteo Retail Media API access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Criteo Retail Media API transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Criteo Retail Media. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Criteo Retail Media API now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Criteo Retail Media API MCP in CrewAI

Add your Vinkius endpoint URL to the mcps array in your agent definition. The framework automatically parses the available endpoints and gives the agent access.

Yes. You can expose the entire MCP Server to a single agent or use the HTTP class with a filter to restrict specific endpoints to designated roles.

Your research agent can execute the name search tool to find specific initiatives. It then shares those campaign IDs in memory for other agents to analyze.

The framework supports standard input/output, Server-Sent Events, and Streamable HTTP. Vinkius endpoints use HTTP for simple, token-based authentication.

We route all agent traffic through an isolated V8 sandbox. Your brand lists and retailer mappings never touch persistent storage and vanish completely between sessions.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript