Compatible with every major AI agent and IDE
What is the OpenPanel MCP Server?
Connect your OpenPanel account to any AI agent and manage your product analytics and user profiles through natural conversation.
What you can do
- Event Tracking — Record user actions and events with custom properties to understand application usage.
- User Identification — Link events to specific individuals and maintain consistent user profiles across sessions.
- Property Management — Dynamically increment or decrement numeric properties on user profiles (e.g., credits, points, or login counts).
- Profile Enrichment — Set traits and custom metadata on user profiles to segment your audience effectively.
How it works
- Subscribe to this server
- Enter your OpenPanel API Key
- Start tracking events and managing users from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Product Managers — track feature adoption and user milestones without writing code.
- Developers — integrate analytics tracking into workflows and verify event payloads instantly.
- Growth Hackers — update user traits and manage reward points or usage limits via simple commands.
Built-in capabilities (4)
Decrement a numeric property on a user profile
Identify a user in OpenPanel
Increment a numeric property on a user profile
Track an event in OpenPanel
Why CrewAI?
When paired with CrewAI, OpenPanel becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call OpenPanel 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
OpenPanel in CrewAI
OpenPanel and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect OpenPanel 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 | 4,000+ 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 OpenPanel in CrewAI
The OpenPanel 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 4 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
OpenPanel for CrewAI
Every tool call from CrewAI to the OpenPanel 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 track a specific user action like a button click?
Use the track_event tool. Provide the event name (e.g., 'Button Clicked') and optionally include a profile_id and custom properties to add context to the action.
Can I update user profile information or traits?
Yes! Use the identify_user tool with the user's profile_id. You can pass a JSON object of properties to set or update traits like email, name, or subscription status.
How do I manage numeric counters like 'points' or 'credits' for a user?
You can use increment_property to increase a value or decrement_property to decrease it. Just specify the profile_id, the property name, and the value to change.
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.
Explore More MCP Servers
View all →
ClickBid
10 toolsManage auction events, bidders, items, and donations directly via AI.

Centaur Analytics
12 toolsAccess AI-powered grain monitoring via Centaur — track CO2, moisture, temperature, predict spoilage, and forecast grain quality from any AI agent.

Datos.gob.es (Catálogo Nacional)
22 toolsAccess Spain's National Open Data Catalog — search datasets, filter by theme, publisher, or format, and retrieve public sector information directly.

NIH RePORTER (Research Funding)
2 toolsAccess the NIH RePORTER database to search for research projects, funding details, and associated publications.
