Bring Conversational Marketing
to CrewAI
Learn how to connect Dashly to CrewAI and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Dashly MCP Server?
Connect your Dashly account to any AI agent and take full control of your conversational marketing and user tracking workflows through natural conversation.
What you can do
- User Lifecycle Orchestration — List and manage your entire high-fidelity user database programmatically, retrieving detailed profile metadata and custom property updates
- Conversational Intelligence — Query active chat sessions, retrieve high-fidelity message history, and send instant replies directly through your agent
- Event Tracking Architecture — Programmatically record custom user actions (e.g., 'Pricing Viewed') to maintain a perfectly coordinated audit trail of customer behavior
- Channel Optimization — Access your complete directory of communication channels to coordinate your engagement strategy across multiple touchpoints
- Operational Monitoring — Verify account-level API connectivity and monitor user activity trends directly through your agent for instant performance reporting
How it works
1. Subscribe to this server
2. Retrieve your Auth Token from your Dashly dashboard (Settings > Integrations > API Keys)
3. Start orchestrating your customer engagement from Claude, Cursor, or any MCP client
No more manual toggling between chat tabs or missing critical user events. Your AI acts as your dedicated engagement coordinator and behavioral architect.
Who is this for?
- Customer Support Leads — instantly retrieve user history and reply to conversations using natural language commands
- Marketing Operations — track custom events and segment users without leaving your creative workspace
- Product Managers — monitor user property updates and engagement health through simple AI queries
Built-in capabilities (8)
Get details for a specific conversation
Get details for a specific user
List communication channels
List recent conversations
List all Dashly users
Send a reply to a conversation
Set custom properties for a user
Track a custom event for a user
Why CrewAI?
When paired with CrewAI, Dashly becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Dashly tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
Dashly in CrewAI
Dashly and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Dashly to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Dashly in CrewAI
The Dashly 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. All 8 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Dashly for CrewAI
Every tool call from CrewAI to the Dashly MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Dashly Auth Token?
Log in to your account, navigate to Settings > Integrations > API Keys, and copy your unique Auth Token.
Can I record custom user events via AI?
Yes! The track_event tool allows your agent to log specific user actions programmatically by providing the user ID and event name.
How do I check active chat sessions?
Use the list_conversations tool to retrieve a comprehensive directory of all current chat interactions and their high-fidelity metadata.
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.
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.