How do I find my HelpCrunch API Key?

Log in to your HelpCrunch dashboard, navigate to **Settings > Developers > Public API**. You will be able to generate and copy your unique Bearer token from there.

Can I reassign a chat to another team member?

Yes! Use the `update_chat_assignee` tool. You must provide the `chat_id` and the numeric `assignee_id` of the team member you wish to assign the conversation to.

How can I filter chats by status?

Use the `search_chats` tool and provide a JSON filter string. For example, to find open chats, pass `{"status": "open"}` in the `filter_json` parameter.

Is it possible to tag customers through this integration?

Yes, you can use the `add_customer_tag` tool. Provide the `customer_id` and the name of the tag you want to add to their profile.

HelpCrunch MCP Server for CrewAI 11 tools — connect in under 2 minutes

Name: HelpCrunch
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to HelpCrunch through Vinkius, pass the Edge URL in the `mcps` parameter and every HelpCrunch tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="HelpCrunch Specialist",
    goal="Help users interact with HelpCrunch effectively",
    backstory=(
        "You are an expert at leveraging HelpCrunch tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in HelpCrunch "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About HelpCrunch MCP Server

Connect your HelpCrunch account to any AI agent and take full control of your customer communication and support workflows through natural conversation.

When paired with CrewAI, HelpCrunch becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call HelpCrunch tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Chat Oversight — List all active and past conversations, retrieve full transcripts, and monitor response times.
Customer Management — Access detailed customer profiles, add descriptive tags, and track user interaction history.
Team Coordination — Reassign chats to specific team members or departments to ensure the right person handles every query.
Proactive Support — Search through chats using complex filters to identify trends or urgent customer issues.
Workflow Automation — Update chat statuses (closed, open, snoozed) directly from the chat interface.
Operational Efficiency — List support departments and monitor the overall health of your customer service operations.

The HelpCrunch MCP Server exposes 11 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect HelpCrunch to CrewAI via MCP

Follow these steps to integrate the HelpCrunch MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 11 tools from HelpCrunch

Why Use CrewAI with the HelpCrunch MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with HelpCrunch through the Model Context Protocol.

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 `mcps` parameter 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

HelpCrunch + CrewAI Use Cases

Practical scenarios where CrewAI combined with the HelpCrunch MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries HelpCrunch for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries HelpCrunch, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain HelpCrunch tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries HelpCrunch against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

HelpCrunch MCP Tools for CrewAI (11)

These 11 tools become available when you connect HelpCrunch to CrewAI via MCP:

add_customer_tag

Add a label/tag to a customer profile

get_chat_details

Get detailed information about a specific chat

get_customer_details

Get detailed profile information for a specific customer

list_chat_messages

Useful for understanding context or historical interactions. List all messages within a specific chat

list_chats

Each chat includes basic metadata and status. List all conversations (chats) in HelpCrunch

list_customers

List all customers (contacts) in HelpCrunch

list_departments

List all support departments

search_chats

Pass filter criteria as a JSON string in "filter_json" (e.g., {"status": "open"}). Search for chats using filters

send_message

Pass the payload as a JSON string in "body_json" (e.g., {"chat": 123, "text": "Hello"}). Send a message to a chat

update_chat_assignee

Assign a chat to a specific team member

update_chat_status

Update the status of a chat (e.g., closed, open)

Example Prompts for HelpCrunch in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with HelpCrunch immediately.

"List all open chats and show the last message for each."

"Search for all chats from the customer with email 'john.doe@example.com'."

"Tag customer ID 5592 with 'VIP' and 'Priority Support'."

Troubleshooting HelpCrunch MCP Server with CrewAI

Common issues when connecting HelpCrunch to CrewAI through the Vinkius, and how to resolve them.

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.

HelpCrunch + CrewAI FAQ

Common questions about integrating HelpCrunch MCP Server with CrewAI.

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.