Bring Shared Inbox
to CrewAI
Learn how to connect Helpwise to CrewAI and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Helpwise MCP Server?
Connect your Helpwise account to any AI agent and manage your shared inboxes through natural conversation.
What you can do
- Mailbox Management — List all shared mailboxes (email, SMS, WhatsApp, social) with status and configuration
- Conversation Tracking — Browse conversations in any mailbox and inspect individual threads with full message history
- Contact Management — List all contacts and create new customer profiles with email and name
- Email Sending — Send outgoing emails or replies through any connected mailbox
- Team Overview — List all agents and team members linked to your account
How it works
1. Subscribe to this server
2. Enter your Helpwise API Key and API Secret from account settings
3. Start managing your inbox from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Customer Support Teams — review conversations, reply to customers, and manage contacts without switching to the Helpwise dashboard
- Team Leads — monitor inbox activity, track response times, and oversee team workloads
- Operations Managers — audit communication history and manage contact databases through AI
Built-in capabilities (7)
Create a new contact
Get details for a specific conversation
List Helpwise contacts
List conversations in a mailbox
List Helpwise shared inboxes
List team users
Send an outgoing email
Why CrewAI?
When paired with CrewAI, Helpwise becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Helpwise 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
Helpwise in CrewAI
Helpwise and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Helpwise 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 Helpwise in CrewAI
The Helpwise 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 7 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
Helpwise for CrewAI
Every tool call from CrewAI to the Helpwise MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I send emails through my shared inbox using the AI agent?
Yes. The send_email tool sends an outgoing email through any connected mailbox. Provide the mailbox ID, recipient email, subject, and body (HTML or plain text). Use list_mailboxes to see all available shared inboxes and their IDs.
Can I view the full conversation history for a customer thread?
Yes. Use list_conversations with a mailbox ID to browse all threads, then call get_conversation_details with the conversation ID to retrieve the complete message history including sender, timestamp, and content for each message.
Does Helpwise require two separate credentials?
Yes. Helpwise uses HTTP Basic Authentication with an API Key and an API Secret. Both are generated in your Helpwise account under Settings > API. The credentials are Base64-encoded and sent in the Authorization header as Basic base64(apiKey:apiSecret).
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.