Bring Helpdesk
to Cursor
Learn how to connect HelpCrunch to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the HelpCrunch MCP Server?
Connect your HelpCrunch account to any AI agent and take full control of your customer support and multi-channel communication workflows through natural conversation.
What you can do
- Unified Chat Management — List and manage all customer conversations and retrieve detailed chat metadata and history
- Proactive CRM — Create and update customer profiles programmatically to maintain a high-fidelity database of user attributes and activities
- Real-time Messaging — Send and receive messages within chats directly through your agent to provide instant customer assistance
- Support Orchestration — Update chat statuses (open, pending, closed) and monitor department workloads for efficient team routing
- Agent Visibility — Retrieve team agent directories and status to understand support capacity across your organization
How it works
1. Subscribe to this server
2. Retrieve your API Key from your HelpCrunch dashboard (Settings > Developers > Public API)
3. Start managing your customer communications from Claude, Cursor, or any MCP client
No more manual toggling between chat windows or searching for customer emails. Your AI acts as your dedicated support coordinator.
Who is this for?
- Support Teams — instantly triage chat queues and respond to high-priority queries using natural language
- Customer Success Managers — update user attributes and retrieve interaction history without leaving your workspace
- Sales Representatives — identify and manage new leads from live chat interactions through automated queries
Built-in capabilities (12)
Requires email and name. Create a new customer profile
Get details for a specific chat
Get details for a specific customer
List configured webhooks
List all customer chats
List all customers
List all departments
List messages from a specific chat
List all agents/team members
Search for customers using filters
Can be sent as an agent. Post a message to a chat
g., open, pending, closed). Change chat status
Why Cursor?
Cursor's Agent mode turns HelpCrunch into an in-editor superpower. Ask Cursor to generate code using live data from HelpCrunch and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
HelpCrunch in Cursor
HelpCrunch and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect HelpCrunch to Cursor 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 HelpCrunch in Cursor
The HelpCrunch 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 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor 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
HelpCrunch for Cursor
Every tool call from Cursor to the HelpCrunch MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I generate an API Key in HelpCrunch?
Log in to your HelpCrunch account, navigate to Settings > Developers > Public API, and click Generate New API Key to obtain your token.
Can the agent respond to customers directly?
Yes! Use the send_chat_message tool to post replies into any active chat thread. The message will appear as coming from your agent account.
How do I search for a customer by email?
The search_customers tool allows you to perform lookups using filters like email, name, or external ID to retrieve specific user profiles.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.