Can my agent perform filtered searches using specific product attributes?

Yes. Use the 'search_filtered' tool. You can specify the 'filter_name' (e.g., 'brand', 'color') and the 'filter_value'. The agent will analyze the global bounds and return results restricted strictly to those custom limits.

How do I monitor the click-through rate (CTR) of my search engine via chat?

Use the 'get_stats' tool. Your agent will pull raw status configurations and capture exact CTR, total clicks, and query velocity numbers for your search engine, helping you track performance without manual dashboard checks.

Can I check which search engines and indices are active in my account?

Absolutely. The 'get_search_engines' and 'get_indices' tools allow your agent to dump all isolated tenant indexes mapping explicit hash strings, giving you a full view of your Doofinder infrastructure.

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

Name: Doofinder
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Connect your Doofinder account to any AI agent and take full control of your e-commerce search and discovery workflows through natural conversation.

When paired with CrewAI, Doofinder becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Doofinder 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

AI-Powered Keyword Search — Identify bounded routing spaces inside the headless Doofinder platform and extract explicitly attached REST arrays targeting specific search queries
Advanced Filtering — Perform structural extraction of properties driving active Account logic by applying facet filters like brand, color, or price range
Predictive Suggestions — Enumerate explicitly attached structured rules to extract fast predictive nodes directly tracking search limits for partial queries
Smart Sorting — Provision highly-available JSON payloads to generate hard customer bindings with custom sort directions like 'price:asc' or 'relevance:desc'
Search Engine Oversight — Command automated validation checks routing explicit gateway history to dump all isolated tenant indexes mapping explicit hash strings
Index & Item Auditing — Inspect deep internal arrays to sync un-cached raw catalog limits and verify the exact data structures defining your product graph
Performance Analytics — Identify precise active arrays spanning native hold parsing to capture exact CTR, click limits, and query velocity numbers

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

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

Why Use CrewAI with the Doofinder MCP Server

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

Doofinder + CrewAI Use Cases

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

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

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

Doofinder MCP Tools for CrewAI (10)

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

get_indices

Identify precise active arrays spanning native Gateway auth

get_items

Inspect deep internal arrays mitigating specific Plan Math

get_search_engines

Dispatch an automated validation check routing explicit Gateway history

get_stats

Identify precise active arrays spanning native Hold parsing

search_custom

Irreversibly vaporize explicit validations extracting rich Churn flags

search_filtered

]` bounding exactly custom limits cutting off unrelated SKU branches. Perform structural extraction of properties driving active Account logic

search_keyword

Identify bounded CRM records inside the Headless Doofinder Platform

search_pagination

Retrieve explicit Cloud logging tracing explicit Vault limits

search_sorted

Provision a highly-available JSON Payload generating hard Customer bindings

suggest

Enumerate explicitly attached structured rules exporting active Billing

Example Prompts for Doofinder in CrewAI

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

"Search for 'summer shoes' in Doofinder"

"Show me the search stats for the last 7 days"

"Get suggestions for partial query 'iph'"

Troubleshooting Doofinder MCP Server with CrewAI

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

Doofinder + CrewAI FAQ

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