How do I get a DataDive API Key?

Log in to your DataDive account and navigate to the Account Settings or API section to generate a new API Key for integrations.

Rank Radar is a DataDive feature that tracks the position of your products (ASINs) for specific keywords in both organic and paid (PPC) search results.

Can I see my Amazon profits in the chat?

Yes, the agent can retrieve high-level summaries of your sales profits and financial performance if you have the Profits tool connected in your DataDive account.

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

Name: DataDive
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to DataDive through Vinkius, pass the Edge URL in the `mcps` parameter and every DataDive 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="DataDive Specialist",
    goal="Help users interact with DataDive effectively",
    backstory=(
        "You are an expert at leveraging DataDive 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 DataDive "
        "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 DataDive MCP Server

Integrate DataDive, the advanced toolset for Amazon sellers, directly into your AI workflow. Monitor product niches, track keyword rankings with Rank Radar, and analyze your sales profits and inventory levels using natural language.

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

What you can do

Niche Analysis — List and retrieve detailed metrics for product niches you are tracking.
Keyword Tracking — Monitor organic and PPC rankings for any ASIN using Rank Radar data.
Profit Oversight — Retrieve a high-level summary of your Amazon sales and financial performance.
Inventory Management — Check current stock levels and get restock recommendations via chat.

The DataDive 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 DataDive to CrewAI via MCP

Follow these steps to integrate the DataDive 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 DataDive

Why Use CrewAI with the DataDive MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with DataDive 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

DataDive + CrewAI Use Cases

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

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

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

DataDive MCP Tools for CrewAI (10)

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

get_account_details

Returns metadata such as account tier, connected marketplace integrations, and subscription status. Retrieve metadata for your DataDive account

get_high_volume_keywords

Returns keywords with significant search volume and favorable competition metrics for ranking priority. List top performing keywords based on search volume and competition

get_inventory_status

Returns units in stock, inbound shipments, and daily sell-through rates to provide restock lead-time alerts. Check current inventory levels and restock recommendations

get_niche_details

Resolves high-level metrics such as average price, total niche volume, and competition score based on aggregated Amazon data. Get detailed analytics and metrics for a specific niche

get_profits_summary

Aggregates sales data, fees, and advertising spend to return net profit margins and ROI for the connected seller account. Retrieve a high-level financial summary of your Amazon sales

get_rank_radar

Returns real-time organic and sponsored positions across tracked keywords, enabling competitive visibility analysis. Get keyword ranking data (organic and PPC) for a specific ASIN

list_competitor_asins

Includes product titles, brand names, and baseline performance data. List all ASINs (competitors) tracked within a niche

list_niche_keywords

Returns search volume, relevancy scores, and priority indicators for product ranking and SEO optimization. List all keywords and search volumes for a specific niche

list_product_niches

Returns a collection of niche objects including name, marketplace (e.g., Amazon US), and tracking status. List all product niches tracked in your DataDive account

search_all_keywords

Matches against the global keyword repository in the user's account to find occurrences and metrics across multiple categories. Search for keywords across all your tracked niches

Example Prompts for DataDive in CrewAI

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

"Show me the ranking data for ASIN 'B08S9DF7' using Rank Radar."

"List all product niches I'm currently tracking in DataDive."

"What is my profit summary for the last 30 days?"

Troubleshooting DataDive MCP Server with CrewAI

Common issues when connecting DataDive 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.

DataDive + CrewAI FAQ

Common questions about integrating DataDive 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.