How do I get a Drift Auth Token?

Log in to your Drift account, navigate to **Settings > App Settings**, and create a new app or use an existing one to generate a **Personal Access Token**. Ensure the app has the necessary scopes for conversations and contacts.

Can the agent reply to Drift conversations?

This integration currently focuses on listing and auditing conversations, contacts, and agents. Sending active replies should be managed via the Drift agent application or web interface.

Does the integration show live agent presence?

Yes, you can use the list_drift_agents or quick_agent_availability_audit tools to retrieve real-time availability and presence statuses for your support and sales teams.

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

Name: Drift
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Integrate Drift, the leading conversational marketing and sales platform, directly into your AI workflow. Manage your customer conversations and transcripts, track identified contacts and their profile attributes, monitor agent availability and roles, and oversee your conversational playbooks using natural language.

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

Conversation Oversight — List and retrieve detailed information and full transcripts for all your Drift customer interactions.
Contact Intelligence — Monitor identified contacts, their email addresses, custom profile attributes, and organizational accounts.
Agent Management — Track real-time agent availability statuses, presence, and organizational roles across your team.
Playbook Monitoring — List all configured conversational playbooks (bots) and identify their current activation statuses.

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

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

Why Use CrewAI with the Drift MCP Server

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

Drift + CrewAI Use Cases

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

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

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

Drift MCP Tools for CrewAI (10)

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

get_contact_profile

Get full profile data and interaction history for a specific contact

get_conversation_details

Get detailed information and full transcript for a specific conversation

get_drift_platform_metadata

Retrieve metadata for the current authenticated Drift account

list_drift_agents

List all registered agents and users in your Drift organization

list_drift_contacts

List all contacts synchronized or identified in your Drift account

list_drift_conversations

List all active and recent customer conversations in Drift

list_drift_playbooks

List all configured conversational playbooks (bots)

list_latest_customer_interactions

Identify the most recently updated customer conversations

quick_agent_availability_audit

Retrieve a high-level summary of active agent availability statuses

search_contacts_by_email

Search for a contact using their email address

Example Prompts for Drift in CrewAI

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

"List all active Drift conversations."

"Show me the contact profile for 'robert.brown@example.org'."

"Who is currently available to take chats in Drift?"

Troubleshooting Drift MCP Server with CrewAI

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

Drift + CrewAI FAQ

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