Integration
Connect Cursor and HelpCrunch
When Agent Pull Request Created fires in Cursor, your agent runs Add Customer Event in HelpCrunch, or Chat Assignee Updated in HelpCrunch to Add Followup Instruction to Agent in Cursor. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Cursor and HelpCrunch to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Cursor and HelpCrunch can do together
From Cursor to HelpCrunch
When Agent Pull Request Created in Cursor
then Add Customer Event in HelpCrunch
From HelpCrunch to Cursor
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Cursor and HelpCrunch
Triggers and actions 11 triggers · 30 actions
- Agent Pull Request Created
Triggers when the selected Cursor cloud agent opens a new GitHub pull request.
- Agent Status Equals
Triggers when a run on the chosen Cursor agent reaches the status you select, such as Finished or Error.
- New Agent
Triggered when a new Cursor cloud agent is created.
- Add Followup Instruction to Agent
Sends a follow-up instruction to an existing Cursor cloud agent, either starting a new run or steering the run in progress. Returns the new run or how the steer was delivered.
- Cancel run
Cancels the active run of a Cursor cloud agent. The run ends in the Cancelled state; start a new run to continue the conversation.
- Delete Agent
Permanently deletes a Cursor cloud agent. This cannot be undone. Returns the ID of the deleted agent.
- Find Agent Status
Looks up a Cursor cloud agent by its ID and returns its status, name, repositories, latest run and link.
- Get run
Returns the status, timestamps, duration, final reply and pushed branches for one run of a Cursor cloud agent.
- Launch Agent
Creates a Cursor cloud agent and immediately starts its first run on the task you describe. Returns the new agent and its run.
- List agents
Returns the Cursor cloud agents for the connected user, newest first, optionally filtered by pull request URL.
- List artifacts
Returns the files a Cursor cloud agent has produced, with each file's path, size and last modified time. Returns at most 100 artifacts.
- List models
Returns the recommended Cursor models you can choose from when creating an agent, including their names, aliases, parameters and variants.
- List repositories
Returns the GitHub repositories the connected Cursor user can access through Cursor's GitHub App installation.
- List runs
Returns the runs of a Cursor cloud agent, newest first, including each run's status, duration, and final reply.
- Chat Assignee Updated
Triggers when a HelpCrunch chat is assigned to a different agent.
- Chat Closed
Triggers when a HelpCrunch chat is closed.
- Chat Status Updated
Triggers when a HelpCrunch chat's status changes.
- Customer Email Updated
Triggers when a HelpCrunch customer's email changes.
- Customer Tags Updated
Triggers when a HelpCrunch customer's tags change.
- Customer Unsubscribed
Triggers when a HelpCrunch customer unsubscribes.
- New Chat Created
Triggers when a new chat is created in HelpCrunch.
- New Customer Created
Triggers when a new customer is created in HelpCrunch.
- Add Customer Event
Records a custom event against a HelpCrunch customer.
- Assign Chat
Assigns a HelpCrunch chat to an agent.
- Create Chat
Creates a HelpCrunch chat with a customer.
- Delete Customer
Deletes a HelpCrunch customer.
- Find Chats
Finds HelpCrunch chats whose field matches a value, such as the customer email or status.
- Find Customer
Finds HelpCrunch customers whose field matches a value, such as by email.
- Get Chat
Returns one HelpCrunch chat by ID.
- Get Customer
Returns one HelpCrunch customer by ID.
- Get Organization
Returns the HelpCrunch organization and whether the team is online.
- List Agents
Returns the agents in the HelpCrunch account.
- List Applications
Returns the HelpCrunch applications (website widget, mobile apps and messenger channels).
- List Chat Messages
Returns the messages of a HelpCrunch chat, newest first.
- List Departments
Returns the HelpCrunch departments and their agents.
- Send Message
Posts a message or private note into a HelpCrunch chat.
- Snooze Chat
Snoozes a HelpCrunch chat until a time.
- Tag Customer
Adds tags to a HelpCrunch customer; unknown tags are created.
- Untag Customer
Removes tags from a HelpCrunch customer.
- Update Chat Department
Moves a HelpCrunch chat to a department.
- Update Chat Status
Changes a HelpCrunch chat's status, such as closing it.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Cursor
Cursor to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cursor to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cursor to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cursor to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Cursor to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cursor to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into HelpCrunch
Google Drive to HelpCrunchGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to HelpCrunchActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to HelpCrunchOrganize anything with Airtable, a modern database created for everyone.
Questions
Cursor and HelpCrunch, answered
What can start an automation from Cursor?
Any of Cursor's 3 triggers in the catalog, including Agent Pull Request Created, New Agent and Agent Status Equals. Describe the moment in plain language and your agent picks the right one.
What can your agent do in HelpCrunch when something happens in Cursor?
Any of HelpCrunch's 19 actions, including Create Chat, Send Message, Update Chat Department and Update Chat Status. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from HelpCrunch to Cursor?
Yes. When something happens in HelpCrunch, your agent can act in Cursor too. This page covers both directions: HelpCrunch's triggers and Cursor's actions are listed here as well.
Do I have to build a connector for Cursor or HelpCrunch?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Cursor and HelpCrunch without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.