Bring Community Feedback
to CrewAI
Learn how to connect UserEcho to CrewAI and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the UserEcho MCP Server?
Connect your UserEcho account to any AI agent and simplify how you manage your community feedback, helpdesk tickets, and self-service content through natural conversation.
What you can do
- Helpdesk Management — List all support tickets and retrieve detailed conversation history and status for specific issues.
- Direct Ticketing — Programmatically create new support tickets directly from your agent to accelerate customer assistance.
- Knowledge Base Access — List and query all articles in your help center to verify self-service documentation.
- Forum Oversight — List and monitor feedback and support forums to understand community trends and suggestions.
- User Directory — List account users and team members to manage your support organization structure.
- Issue Tracking — Monitor the progress of client requests and verify resolution times via AI.
How it works
1. Subscribe to this server
2. Enter your UserEcho API Token and Subdomain (found in your developer settings)
3. Start managing your community feedback from Claude, Cursor, or any MCP client
Who is this for?
- Customer Support Managers — quickly retrieve ticket histories and monitor team activity via simple AI commands.
- Community Managers — monitor forum feedback and verify article availability directly from the workspace.
- Product Teams — coordinate bug reports and feature requests coming from UserEcho forums.
Built-in capabilities (6)
Add a new ticket
Get details for a specific ticket
List account users
List UserEcho forums
List knowledge base articles
List helpdesk tickets
Why CrewAI?
When paired with CrewAI, UserEcho becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call UserEcho 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
UserEcho in CrewAI
UserEcho and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect UserEcho 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 UserEcho in CrewAI
The UserEcho 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 6 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
UserEcho for CrewAI
Every tool call from CrewAI to the UserEcho MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see the full conversation history of a support ticket?
Yes! Use the get_ticket_details tool and provide the Ticket ID. Your agent will retrieve the complete metadata and all conversation threads for that specific issue.
How do I list all the help center articles in my account?
Run the list_kb_articles query. The agent will retrieve a complete list of all articles currently published in your UserEcho knowledge base.
Is it possible to create a new ticket via AI for a customer?
Absolutely. Use the create_support_ticket action. Provide a header and the detailed content, and the agent will instantly log the request in your UserEcho helpdesk.
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.