How do I find my Helpshift API Key?

Log in to your Helpshift dashboard, go to **Settings > API**, and you will find your **API Key** listed there. This key is used as the username for Basic Authentication.

What is the 'Domain' in the setup?

The domain is the unique identifier for your Helpshift instance (e.g., if you access it at `company.helpshift.com`, your domain is `company`).

Can I see the history of actions taken on an issue?

Yes! Use the `get_issue_audit_logs` tool (v2). It retrieves the action history, showing when status was changed, who was assigned, and which tags were added.

Is the integration secure for support data?

Absolutely. The integration uses industry-standard Basic Authentication over HTTPS. Your credentials are encrypted and stored securely within the Vinkius Cloud infrastructure.

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

Name: Helpshift
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to Helpshift through Vinkius, pass the Edge URL in the `mcps` parameter and every Helpshift 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="Helpshift Specialist",
    goal="Help users interact with Helpshift effectively",
    backstory=(
        "You are an expert at leveraging Helpshift 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 Helpshift "
        "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 Helpshift MCP Server

Connect your Helpshift platform to any AI agent and take full control of your customer support and user hub workflows through natural conversation.

When paired with CrewAI, Helpshift becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Helpshift 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

Issue Oversight — List all support issues, retrieve detailed metadata, and monitor audit logs for action history.
Response Management — Add messages to existing issues and update statuses (Resolved, Rejected) directly from the chat.
Content Insights — Browse your published FAQ articles and sections to ensure documentation is accurate.
User Hub Operations — Perform bulk user profile updates and creation tasks using the User Hub v2 API.
Application Visibility — List all registered apps in your Helpshift dashboard to ensure correct routing.
Operational Efficiency — Track the progress of bulk identity tasks and monitor support volume in real-time.

The Helpshift 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 Helpshift to CrewAI via MCP

Follow these steps to integrate the Helpshift 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 Helpshift

Why Use CrewAI with the Helpshift MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Helpshift 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

Helpshift + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Helpshift 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 Helpshift, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Helpshift 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 Helpshift against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Helpshift MCP Tools for CrewAI (11)

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

add_issue_message

Pass the message details as a JSON string in "body_json". Add a message to an existing issue

bulk_user_action

Pass the actions array as a JSON string in "body_json". Perform bulk profile operations (v2)

create_issue

Pass the payload as a JSON string in "body_json" (requires app_id, title, body). Create a new support issue

get_bulk_task_status

Check the status of a bulk profile operation

get_issue_audit_logs

Retrieve the action history for a specific issue

get_issue_details

Get detailed information about a specific issue

list_faq_sections

List FAQ categories/sections

list_faqs

List all published FAQ articles

list_issues

Useful for monitoring support volume and identifying urgent cases. List support issues/tickets in Helpshift

list_registered_apps

List all applications registered in your Helpshift dashboard

update_issue_status

Update the status of an issue (e.g., Resolved, Rejected)

Example Prompts for Helpshift in CrewAI

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

"List all active issues and show their audit logs."

"Add a reply to issue ID 5501: 'We are investigating the logs now'."

"Search for FAQ articles related to 'subscription renewal'."

Troubleshooting Helpshift MCP Server with CrewAI

Common issues when connecting Helpshift 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.

Helpshift + CrewAI FAQ

Common questions about integrating Helpshift 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.