Integration · Customer support

Connect Claude & ChatGPT to Mojo Helpdesk

Ask your AI which tickets are open, what happened on a ticket, or to draft a reply in Mojo Helpdesk. It can search tickets, read comments, staff notes and history, add replies, notes, tags and tasks, and look up users and agents. It also works with your asset list and knowledge base articles.

Connect Mojo Helpdesk free

Free plan, no credit card. Takes about a minute.

Try asking

“Which tickets were updated today?”
The AI lists tickets sorted by last update, with status, priority, requester and assignee.
“Summarize what has happened on ticket 18234.”
It reads the ticket, its public comments, staff notes and change history, and sums them up.
“Reply to the requester that the new laptop ships Friday.”
It adds a public comment to the ticket. The requester can see it and may get it by email.

What your AI can do

Tickets

Search and list tickets, read comments, staff notes and history, and add replies, private notes, tags and tasks.

Users and agents

Find users by email, read user details, and list agents, queues, ticket types and tags.

Assets and knowledge base

Search, create and update assets, and search, create and update knowledge base articles.

“Add a staff note that we are waiting on the vendor, and tag it vendor.”
It adds a private note only agents can see and puts the vendor tag on the ticket.
“Which laptop is assigned to [email protected]?”
It finds the user by email and searches assets to show the device, status and location.
“Turn this fix into a knowledge base article, saved as a draft.”
It creates the article with title, text and keywords as a draft, so it is not published yet.

99 tools for Mojo Helpdesk

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

add_staff_noteChanges dataAdd a private staff note to a ticket by ticket_id (body). Only agents can see it; anyone in cc is emailed.
add_ticket_commentChanges dataAdd a public comment to a ticket by ticket_id with the reply text in `body`, optional cc and time_spent. The reply is visible to the requester and may be emailed to them.
add_ticket_tagChanges dataAdd a tag to a ticket by ticket_id, using tag_id or tag_label (a new label creates the tag).
create_addressChanges dataCreate a new address. Required: name. API summary: Create location.
create_articleChanges dataCreate a knowledge base article with a title, article text (description) and optional keywords and topic_ids. It is published by default; set status 1 to save as a draft.
create_assetChanges dataCreate an asset with a display_name and optional asset_tag, serial_number, vendor, cost, location and user. Search first to avoid duplicates.
create_asset_documentChanges dataCreate a new document for a asset. API summary: Attach files to an asset.
create_asset_statusChanges dataCreate a new asset status. Required: name. API summary: Create asset status.
create_asset_typeChanges dataCreate a new asset type. Required: name. API summary: Create asset type.
create_departmentChanges dataCreate a new department. Required: name. API summary: Create department.
create_groupChanges dataCreate a new group. Required: name. API summary: Create group.
create_group_access_rightChanges dataCreate a new access right for a group. Required: body. API summary: Set access right for a group.
create_setChanges dataCreate a new set. Required: keys or has access. API summary: Set access right for a restricted agent on multiple queues.
create_set_postChanges dataCreate a new set. Required: keys or has access. API summary: Set access right for a group on multiple queues.
create_tagChanges dataCreate a new tag. Required: label or color. API summary: Create tag.
create_taskChanges dataCreate a new task. Required: keys. API summary: Reorder ticket tasks.
create_ticket_documentChanges dataCreate a new document for a ticket. API summary: Add attachment to a ticket, comment, or staff note.
create_ticket_queueChanges dataCreate a new ticket. Required: name. Search tickets first to avoid duplicates. API summary: Create ticket queue.
create_ticket_taskChanges dataAdd a task to a ticket by ticket_id with a title, optional notes and due date.
create_ticket_typeChanges dataCreate a new ticket. Required: name. Search tickets first to avoid duplicates. API summary: Create ticket type.
create_user_access_rightChanges dataCreate a new access right for a user. Required: ticket queue id or has access. API summary: Set access right for a restricted agent on a single queue.
delete_addressDeletesPermanently delete a address by address id. Destructive action; may require approval. API summary: Destroy location.
delete_assetDeletesPermanently delete a asset by asset id. Destructive action; may require approval. API summary: Destroy asset.
delete_asset_documentDeletesPermanently delete a document by blob id. Destructive action; may require approval. API summary: Delete an asset file.
delete_asset_statusDeletesPermanently delete a asset status by asset status id. Destructive action; may require approval. API summary: Destroy asset status.
delete_asset_typeDeletesPermanently delete a asset type by asset type id. Destructive action; may require approval. API summary: Destroy asset type.
delete_departmentDeletesPermanently delete a department by department id. Destructive action; may require approval. API summary: Destroy department.
delete_documentDeletesPermanently delete a document by document id. Destructive action; may require approval. API summary: Delete an attachment.
delete_groupDeletesPermanently delete a group by group id. Destructive action; may require approval. API summary: Destroy group.
delete_tagDeletesPermanently delete a tag by tag id. Destructive action; may require approval. API summary: Destroy tag.
delete_tasks_completedDeletesPermanently delete a task by ticket id. Destructive action; may require approval. API summary: Delete completed ticket tasks.
delete_ticketDeletesPermanently delete a ticket by ticket id. Destructive action; may require approval. API summary: Destroy ticket.
delete_ticket_2DeletesPermanently delete a ticket by ticket id. Destructive action; may require approval. API summary: Destroy ticket type.
delete_ticket_deleteDeletesPermanently delete a ticket by ticket id. Destructive action; may require approval. API summary: Destroy ticket queue.
delete_ticket_taskDeletesPermanently delete a task by task id. Destructive action; may require approval. API summary: Destroy ticket task.
delete_userDeletesPermanently delete a user by user id. Destructive action; may require approval. API summary: Destroy user.
find_user_by_emailFind a user by email address.
get_addressGet one address by address id. API summary: Show location.
get_articleGet one knowledge base article by ID, with its full content.
get_assetGet one asset by ID, with its type, status, location and assigned user.
get_asset_statusGet one asset status by asset status id. API summary: Show asset status.
get_asset_typeGet one asset type by asset type id. API summary: Show asset type.
get_departmentGet one department by department id. API summary: Show department.
get_documentGet one document by document id. API summary: Download an attachment.
get_eventGet one event by event id. API summary: Get an event log entry.
get_groupGet one group by group id. API summary: Show group.
get_tagGet one tag by tag id. API summary: Show tag.
get_teamGet one team by team id. API summary: Show team.
get_ticketGet one ticket by ticket_id, with title, description, status, priority, requester and assignee.
get_ticket_2Get one ticket by ticket id. API summary: Show ticket form.
get_ticket_3Get one ticket by ticket id. API summary: Show ticket type.
get_ticket_getGet one ticket by ticket id. API summary: Show ticket queue.
get_userGet one user by ID, with name, email, role and company.
get_user_group_accessGet one group access for a user by group id. API summary: Get single group tickets access for a user.
list_access_rights_for_all_agentsList agents. API summary: List access rights for all agents.
list_access_rights_for_groupsList groups. API summary: List access rights for groups.
list_addressesList addresses. API summary: List locations.
list_agentsList the agents (staff who work on tickets).
list_asset_statusesList asset statuses. Results are paginated.
list_asset_typesList asset types.
list_asset_types_in_tree_orderList trees. API summary: List asset types in tree order.
list_assetsList assets.
list_departmentsList departments.
list_departments_in_tree_orderList trees. API summary: List departments in tree order.
list_eventsList events. Optional filters: ticket id. Results are paginated. API summary: List event log entries.
list_group_access_rightsList access rights for a group. API summary: Show access rights for a group.
list_groupsList groups. Results are paginated.
list_queuesList the ticket queues (inboxes tickets are sorted into).
list_staff_notesList the private staff notes on a ticket by ticket_id.
list_tagsList the ticket tags in the help desk.
list_teamsList teams. Results are paginated.
list_ticket_commentsList the public comments (replies) on a ticket by ticket_id.
list_ticket_documentsList documents for a ticket. API summary: List attachments for a ticket.
list_ticket_formsList tickets. API summary: List ticket forms.
list_ticket_historyList the history of changes on a ticket by ticket_id (status changes, assignments and so on).
list_ticket_tasksList the to-do tasks on a ticket by ticket_id.
list_ticket_typesList the ticket types defined in the help desk.
list_ticketsList tickets, sorted by fields such as updated_on, created_on, status_id or priority_id. Results are paginated.
list_treesList trees. API summary: List locations in tree order.
list_user_access_rightsList access rights for a user. API summary: Show access rights for a restricted agent.
list_user_group_accessesList group accesses for a user. API summary: List all groups tickets access for a user.
list_usersList users (customers and staff). Results are paginated.
remove_ticket_tagDeletesRemove a tag from a ticket by ticket_id, using tag_id or tag_label.
search_articlesSearch knowledge base articles by text in `query`. Leave query empty to list all visible articles.
search_assetsSearch assets (equipment such as laptops or devices) by `query`. Results are paginated.
search_ticketsSearch tickets with the help desk's advanced search syntax in `query` (e.g. status, assignee or text), sorted by sf. Results are paginated.
submit_tagVisible to othersMerge a tag (tag id). Has effects visible outside this system. API summary: Merge tag.
update_addressChanges dataUpdate an existing address identified by address id. API summary: Update location.
update_articleChanges dataUpdate a knowledge base article by ID: title, text (description), keywords, topics, staff_only or status (1 draft, 99 published).
update_assetChanges dataUpdate an asset by asset_id, such as its notes, asset_status_id, location_id or used_by_id. Only the fields you pass change.
update_asset_statusChanges dataUpdate an existing asset status identified by asset status id. API summary: Update asset status.
update_asset_typeChanges dataUpdate an existing asset type identified by asset type id. API summary: Update asset type.
update_departmentChanges dataUpdate an existing department identified by department id. API summary: Update department.
update_groupChanges dataUpdate an existing group identified by group id. API summary: Update group.
update_tagChanges dataUpdate an existing tag identified by tag id. API summary: Update tag.
update_ticket_queueChanges dataUpdate an existing ticket identified by ticket id. API summary: Update ticket queue.
update_ticket_taskChanges dataUpdate a ticket task by ticket_id and task_id: title, notes, due date, or mark it completed.
update_ticket_typeChanges dataUpdate an existing ticket identified by ticket id. API summary: Update ticket type.
update_user_group_accessChanges dataUpdate an existing group access identified by group id. API summary: Set single group tickets access for a user.

Set up in three steps

1
Pick the app
Create a free HeyMyApps account and choose Mojo Helpdesk from the app list.
2
Paste your key
Paste your Mojo Helpdesk API key. In the agent portal open My profile > Dev settings > API keys and create a read-write key (or read-only for lookups). The key acts with your agent permissions, so use an admin account to see the whole help desk.
3
Add the link to your AI
You get a personal MCP link. Add it to Claude, ChatGPT or Cursor:
1. Click your name, then Settings › Connectors › Add custom connector.
2. Paste your link as the Remote MCP server URL.
3. Switch it on from the + menu in a chat.

Questions

What can the AI do in Mojo Helpdesk?

The AI can search and read tickets, comments, staff notes, history, tasks, users, agents, queues, ticket types, tags, assets and knowledge base articles. It can add public comments, staff notes, tags and tasks to tickets, remove tags, update tasks, and create and update assets and articles.

Does the AI see my Mojo Helpdesk API key?

No. Your Mojo Helpdesk API key is encrypted at rest and never shown to the AI. After you save it, it is not shown again, not even to you. The AI only sees the results of the tools it calls.

Can I control what the AI is allowed to do?

Yes. You choose which tools are switched on, so you can start with lookups only, or use a read-only API key. Public comments reach the requester and new articles are published by default, so those tools can require your approval before they run. Every tool call is logged.

Does it work with ChatGPT?

Yes. In ChatGPT go to Settings › Apps & Connectors › Advanced and turn on Developer mode, then add your HeyMyApps link. Developer mode needs a paid ChatGPT plan: Plus, Pro, Business or Enterprise. The same link also works in Claude (Settings › Connectors › Add custom connector), Cursor and other MCP clients.

What does it cost?

HeyMyApps has a free plan with no credit card required. Paid plans bill per completed task. You also need your own Mojo Helpdesk account.

What will the AI be able to see?

The API key acts with the permissions of the agent who created it. If that agent can only see some queues, the AI sees the same. Create the key from an admin account if the AI should work across the whole help desk.