Bring Behavioral Analytics
to CrewAI
Learn how to connect Microsoft Clarity to CrewAI and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Microsoft Clarity MCP Server?
Connect your Microsoft Clarity account to any AI agent and unlock behavioral analytics insights through natural conversation.
What you can do
- Project Management — List all tracked websites and inspect individual project configurations and data retention settings
- Live Insights — Retrieve real-time active users, page views, and engagement metrics for any project
- Dashboard Analytics — Access aggregate metrics including sessions, pages per session, engagement scores, and bounce rates
- Heatmap Analysis — Browse page heatmaps showing click, scroll, and attention patterns, and inspect detailed interaction data
- Session Recordings — List session recordings with duration and pages visited, and inspect individual session timelines
- UX Friction Detection — Identify dead clicks (elements that don't respond) and rage clicks (repeated frustrated clicking) to locate broken UI elements
- Content Visibility — Analyze scroll depth data to understand how far users scroll and where content engagement drops off
- Page Ranking — View top-performing pages ranked by session count and engagement metrics
How it works
1. Subscribe to this server
2. Enter your Clarity API Key
3. Start analyzing user behavior from Claude, Cursor, or any MCP-compatible client
Who is this for?
- UX Designers — identify friction points, analyze click patterns, and validate design decisions with behavioral data
- Product Managers — monitor engagement metrics, track feature adoption through scroll depth, and prioritize UX improvements
- Growth Engineers — detect conversion blockers by analyzing rage clicks, dead clicks, and session replay data
Built-in capabilities (13)
Verify connectivity
Get dashboard metrics
Get heatmap data
Get live insights
Get project details
Get recording details
Get scroll depth
List dead clicks
List heatmaps
List projects
List rage clicks
List recordings
List top pages
Why CrewAI?
When paired with CrewAI, Microsoft Clarity becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Microsoft Clarity 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
Microsoft Clarity in CrewAI
Microsoft Clarity and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Microsoft Clarity 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 Microsoft Clarity in CrewAI
The Microsoft Clarity 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 13 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
Microsoft Clarity for CrewAI
Every tool call from CrewAI to the Microsoft Clarity MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I detect UX friction points like dead clicks and rage clicks?
Yes! Use list_dead_clicks to find page elements where users click without any response — signaling non-interactive elements that look clickable. Use list_rage_clicks to detect pages where users repeatedly click in frustration, indicating broken buttons, slow-loading elements, or confusing UI patterns.
Can I analyze how far users scroll on each page?
Yes. The get_scroll_depth tool returns scroll metrics for each page in your project, showing the percentage of users who reach each content section. This identifies exactly where engagement drops off — essential for optimizing content placement and CTA positioning.
Can I view real-time analytics while users are on my site?
Yes. The get_live_insights tool provides real-time data for any project, including active user count, current page views, and live engagement metrics. For historical aggregates, use get_dashboard to access sessions, pages per session, and engagement scores over time.
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.