4,500+ servers built on MCP Fusion
Vinkius

HelpCrunch MCP. Manage customer chats and profiles directly from your AI agent.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

HelpCrunch MCP on Cursor AI Code Editor MCP Client HelpCrunch MCP on Claude Desktop App MCP Integration HelpCrunch MCP on OpenAI Agents SDK MCP Compatible HelpCrunch MCP on Visual Studio Code MCP Extension Client HelpCrunch MCP on GitHub Copilot AI Agent MCP Integration HelpCrunch MCP on Google Gemini AI MCP Integration HelpCrunch MCP on Lovable AI Development MCP Client HelpCrunch MCP on Mistral AI Agents MCP Compatible HelpCrunch MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

HelpCrunch MCP Server lets your AI agent manage customer support directly. It gives you tools to list all chats, find customer profiles, add tags, and reassign conversations.

You can track active issues, update statuses, and send messages—all from a single conversation flow without opening the HelpCrunch dashboard.

What your AI agents can do

Add customer tag

Applies a label or tag to a specific customer profile.

Get chat details

Retrieves full details about a single, specific chat conversation.

Get customer details

Fetches the complete profile and history for a given customer.

+ 8 more capabilities included
Retrieve Customer Records

Get detailed profile information for a specific customer using get_customer_details, or list all contacts with list_customers.

Manage Chat History

List all conversations (list_chats), search specific conversations (search_chats), or retrieve the full message transcript for any chat (list_chat_messages).

Update Chat Status and Ownership

Change a chat's status (e.g., closed, open) with update_chat_status, or hand off the chat to a specific team member with update_chat_assignee.

Tag and Organize Customers

Apply descriptive labels or tags to a customer's profile using add_customer_tag.

Communicate with Customers

Send a direct message into an active chat using send_message.

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

HelpCrunch MCP Server: 11 Tools for Customer Support

These 11 tools let your AI agent perform every core support function: listing, retrieving, updating, and communicating with customer data and chats.

add019d75af

add customer tag

Applies a label or tag to a specific customer profile.

get019d75af

get chat details

Retrieves full details about a single, specific chat conversation.

get019d75af

get customer details

Fetches the complete profile and history for a given customer.

list019d75af

list chat messages

Lists every message sent within a specific chat, useful for understanding the full context.

list019d75af

list chats

Lists basic metadata and status for all conversations in HelpCrunch.

list019d75af

list customers

Lists all customer contacts in the HelpCrunch system.

list019d75af

list departments

Lists all available support departments within the system.

search019d75af

search chats

Searches for conversations using specific criteria, like status or date range.

send019d75af

send message

Sends a message into a specific chat conversation.

update019d75af

update chat assignee

Changes the person assigned to a chat to a specific team member.

update019d75af

update chat status

Updates the current status of a chat, such as setting it to closed or open.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with HelpCrunch, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 4,700+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week

What you can do with this MCP connector

Your AI client takes over your support workflow. You'll manage customer conversations, update records, and track issues directly through natural conversation, never having to open the HelpCrunch dashboard. You'll use the server's tools to handle everything from listing chats to changing who's on the case.

Retrieving Customer Information

To get a full picture of a client, you can fetch their entire profile and history using get_customer_details, or you can see a list of every contact in the system with list_customers. You can also organize records by applying descriptive labels or tags to a customer's profile with add_customer_tag.

Handling Conversations

You can get a basic list of every conversation with list_chats, or narrow down your focus by searching chats using specific criteria like status or date range with search_chats. Need the full story? You can get specific details about a single chat with get_chat_details, and you can list every message sent within a chat to understand the complete context using list_chat_messages.

Team Coordination and Status Updates

You can change the person assigned to a chat using update_chat_assignee, or you can set the current status of a chat, like marking it open or closed, with update_chat_status. You'll also find a list of all available support departments in the system using list_departments.

Communicating with Customers

You can send a message directly into an active chat using send_message.

When you use these tools, your AI client handles the whole process. It calls the tool, the server runs the operation, and it feeds the data back to your agent for a clean, actionable response. You just tell your agent what you want done.

How HelpCrunch MCP Works

  1. 1 Connect your HelpCrunch API Key to the server and your AI client.
  2. 2 Tell your AI client what you need done using natural language (e.g., 'What are the open chats for VIP customers?').
  3. 3 The server runs the required tools (search_chats, list_customers, etc.) and sends the data back to your AI client for a summary.

The bottom line is, your AI agent acts as your support desk, running the necessary API calls for you in one conversation.

Who Is HelpCrunch MCP For?

Anyone managing customer support operations. Specifically, the Support Manager who's tired of clicking through dashboards to find a single customer's full history. Or the Customer Success Team member who needs to check a client's history and add a tag without leaving their workflow.

Support Manager

Retrieves summaries of team workloads, monitors open chats, and assigns chats to the right department using list_departments and update_chat_assignee.

Customer Success Manager

Checks a client's full interaction history using get_customer_details and adds context tags to their profile using add_customer_tag during a follow-up call.

Sales Development Rep

Monitors new inbound chats and qualifies leads by checking chat status and pulling key customer data from list_chats.

What Changes When You Connect

  • You instantly get a summary of open chats and team workloads using list_chats and search_chats. You don't have to navigate to the dashboard to see what's burning hot.
  • Every customer's history is immediately available. Use get_customer_details to check their full profile and interaction history before drafting a response.
  • You can coordinate the team automatically. Use update_chat_assignee to hand off a chat to the correct person or department, logging the action immediately.
  • Keep customer data clean and organized. Use add_customer_tag to apply 'VIP' or 'Billing Issue' tags to a customer profile, making it instantly searchable for the team.
  • You never lose context. Use list_chat_messages to pull the full transcript for a chat, ensuring your AI agent has every single detail for the next message using send_message.
  • You can control the lifecycle of the issue. Use update_chat_status to change a chat from 'Open' to 'Closed' right after resolution, documenting the workflow change.

Real-World Use Cases

01

Onboarding a New Lead

A Sales Rep needs to check if a lead has talked to support before. They ask their agent to run list_chats and filter by the lead's email. The agent finds two historical chats and confirms the last one was about billing, allowing the rep to skip basic qualification steps and jump straight to upselling.

02

Handling a Priority Escalation

A Support Manager gets an alert about an urgent issue. They ask their agent to run search_chats with the filter 'status: open' and 'tags: VIP'. The agent returns the top 3 chats, allowing the manager to immediately use update_chat_assignee to route the issue to the senior technical team.

03

Updating Customer Context During a Call

A CSM finishes a follow-up call. They ask their agent to first run get_customer_details to pull all past issues, then run add_customer_tag to mark them as 'Followup Complete'. This keeps the client record accurate without manual logging.

04

Closing Out a Billing Issue

A Support Agent solves a billing query. Instead of clicking through menus, they ask their agent to run update_chat_status (to 'Closed') and update_chat_assignee (to 'Team Lead'). The system confirms the status change and logs the resolution.

The Tradeoffs

Checking everything manually

The user opens the HelpCrunch dashboard, clicks 'Chats', finds the client, opens the profile, clicks 'History', and then copies the details into a notes document.

Tell your AI agent to 'Get the details for customer John Doe and list all his open chats.' The agent uses get_customer_details and list_chats in sequence, giving you all the data in one response.

Assuming the current status

The agent manually updates the status in the UI, but forgets to reassign the chat to the correct queue, leaving the ticket unowned and stuck.

Use update_chat_status followed by update_chat_assignee. This guarantees the chat is both correctly marked as 'Resolved' and routed to the 'Billing Department' using the tools.

Sending generic messages

The agent just types 'Hi, let me look into this' into the chat and waits, without first pulling the full context or confirming the issue type.

First, ask your agent to run get_chat_details to confirm the issue topic. Then, use send_message to send a targeted, informed response.

When It Fits, When It Doesn't

Use this if you need to manage the full lifecycle of a customer interaction—from initial inquiry to final status update. You need to read history, check profiles, assign ownership, and tag the customer based on data points. Don't use this if you only need to view a list of contacts. For simple listing, use a dedicated contact management tool. If your primary need is only drafting responses based on history, an LLM with RAG capabilities might suffice. But if you need to change the state of the customer record (tags, assignments, status), you need the HelpCrunch MCP Server.

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by HelpCrunch. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 11 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

add_customer_tag get_chat_details get_customer_details list_chat_messages list_chats list_customers list_departments search_chats send_message update_chat_assignee update_chat_status

Managing customer support history shouldn't involve clicking through five different dashboard tabs.

Today, you start in the chat view. You see the initial message. To know if this is a repeat issue, you have to switch tabs to the 'Customer' section. Then, you copy the customer ID over. Next, you open the 'History' report, filter by date, and cross-reference the data. It's a painful, multi-step process that loses time and context.

With this MCP Server, you just tell your AI agent: 'What is the full context for this chat?' The agent handles the required steps—calling `get_customer_details`, retrieving the full chat transcript via `list_chat_messages`, and checking if the customer has any 'VIP' tags using `add_customer_tag`. You get the full picture in one go.

HelpCrunch MCP Server: Control the entire support workflow.

Manual workflows require separate actions: First, you must assign the chat using the UI. Then, you must change the status to 'Snoozed' to pause work. Finally, you must manually log the reason for the handoff in a separate notes field.

Now, you just tell your AI agent to 'Send this chat to the Billing Department and mark it as snoozed.' The agent runs `update_chat_assignee` and `update_chat_status` in sequence, guaranteeing both the ownership and the status are correct. That's the difference.

Common Questions About HelpCrunch MCP

How do I check all open chats using the HelpCrunch MCP Server? +

You run search_chats and pass a filter for status 'open'. This tool filters all conversations to give you a list of active chats immediately.

Can I add tags to a customer profile using the HelpCrunch MCP Server? +

Yes, you use the add_customer_tag tool. Simply tell your agent the customer ID and the tags you want applied.

What is the best way to get the full history of a chat using the HelpCrunch MCP Server? +

Use list_chat_messages. This tool pulls every single message into a chronological list, giving you the complete context needed for accurate support.

Can I reassign a chat using the HelpCrunch MCP Server? +

Yes, use update_chat_assignee. You just need to specify the chat ID and the ID of the team member you want to hand the chat off to.

Does HelpCrunch MCP Server only list chats, or can it send messages? +

It can do both. You use list_chats to see the overview, and send_message to send a direct message into the conversation.

How do I list all departments using the HelpCrunch MCP Server? +

You call the list_departments tool. This action retrieves a full list of all support departments defined in your HelpCrunch account. This lets your agent know which teams are available to receive chats or manage specific workflows.

Can I search for chats by status using the HelpCrunch MCP Server? +

Yes, you use the search_chats tool. You pass a JSON string containing the filter criteria, like {"status": "open"}. This lets your agent filter chats quickly, finding only the conversations that match your needs.

What information does `get_customer_details` provide about a customer? +

The get_customer_details tool provides a complete profile view for a customer. This includes their interaction history, descriptive tags, and other core data points. Your agent uses this to build context before responding.

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.

More in this category

You might also like

Built & Managed by Vinkius 30s setup 11 tools

We've already built the connector for HelpCrunch. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 11 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.