Integration

Mojo Helpdesk integration

Mojo Helpdesk is a ticketing and IT asset management help desk. An agent can list, search, create, update and delete tickets, post public comments and internal staff notes, upload and download ticket attachments, tag tickets and manage ticket tasks; manage end users and agents, groups (companies), ticket queues, ticket types, tags and agent or group queue access rights; read ticket forms, teams and the event log; manage IT assets with their types, statuses, locations, departments and files; and search, create and update knowledge base articles. Custom fields (custom_field_<key> body keys) are not exposed as parameters. Authentication: a per-agent API key from My profile, Dev settings, API keys in the agent portal, sent in the X-API-KEY header; a read-only key can only call read tools, and every key has the permissions of the agent who owns it (several tools require the Manager role).

Connect Mojo Helpdesk How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Mojo Helpdesk.Built from the 103 Mojo Helpdesk tools below, on the connection you add once.

What you can do with Mojo Helpdesk

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Group, 6 operations

create_groupCreate groupPOSTCreate a new group (formerly called company).
delete_groupDelete groupDELETEDelete a group. This action cannot be undone.
get_groupGet groupGETRetrieve a single group (formerly called company) by ID, including any enabled custom group fields.
list_all_group_access_rightsList all group access rightsGETLists every group (company) with the ticket queues it can access. Use list_group_access_rights for one group.
list_groupsList groupsGETRetrieve a list of groups (formerly called companies). This endpoint supports pagination.
update_groupUpdate groupPUTUpdates an existing group and returns it. Partial update: only the fields you send change; leave a field out to keep its current value.

Asset, 5 operations

create_assetCreate assetPOSTCreate a new asset.
delete_assetDelete assetDELETEDelete an asset. This action cannot be undone. On success the deleted asset's JSON is returned (HTTP 200).
get_assetGet assetGETRetrieve details of a specific asset.
list_assetsList assetsGETRetrieve a list of assets.
update_assetUpdate assetPUTUpdates an existing asset and returns it. Partial update: only the fields you send change; leave a field out to keep its current value.

Asset status, 5 operations

create_asset_statusCreate asset statusPOSTCreate a new asset status
delete_asset_statusDelete asset statusDELETEDelete an asset status by ID. Assets currently using this status are reassigned: pass `move_to_status_id` to move them to another status, or omit it to clear their status.
get_asset_statusGet asset statusGETRetrieve a specific asset status by ID
list_asset_statusesList asset statusesGETRetrieve a list of asset statuses. Supports paging with optional parameters per_page and page. If per_page is missing, by default it will return 30 items per page.
update_asset_statusUpdate asset statusPUTUpdates an existing asset status and returns it. Partial update: only the fields you send change; leave a field out to keep its current value.

Asset type, 5 operations

create_asset_typeCreate asset typePOSTCreate a new asset type
delete_asset_typeDelete asset typeDELETEDelete an asset type by ID. On success the deleted asset type's JSON is returned (HTTP 200).
get_asset_typeGet asset typeGETRetrieve a specific asset type by ID
list_asset_typesList asset typesGETRetrieve a list of asset types
update_asset_typeUpdate asset typePUTUpdates an existing asset type and returns it. Partial update: only the fields you send change; leave a field out to keep its current value.

Department, 5 operations

create_departmentCreate departmentPOSTCreate a new department
delete_departmentDelete departmentDELETEDelete a department by ID. On success the deleted department's JSON is returned (HTTP 200).
get_departmentGet departmentGETRetrieve a specific department by ID
list_departmentsList departmentsGETRetrieve a list of departments
update_departmentUpdate departmentPUTUpdates an existing department and returns it. Partial update: only the fields you send change; leave a field out to keep its current value.

Location, 5 operations

create_locationCreate locationPOSTCreate a new location
delete_locationDelete locationDELETEDelete a location by ID. On success the deleted location's JSON is returned (HTTP 200).
get_locationGet locationGETRetrieve a specific location by ID
list_locationsList locationsGETRetrieve a list of locations
update_locationUpdate locationPUTUpdates an existing location and returns it. Partial update: only the fields you send change; leave a field out to keep its current value.

Tag, 5 operations

create_tagCreate tagPOSTCreate a new ticket tag.
delete_tagDelete tagDELETEDelete a tag. This action cannot be undone.
get_tagGet tagGETRetrieve details of a specific tag.
list_tagsList tagsGETRetrieve all ticket tags for the account. This endpoint does NOT paginate - it returns the full list. Results can be ordered with `sort_by` and `sort_order`.
update_tagUpdate tagPUTUpdates an existing tag and returns it. Partial update: only the fields you send change; leave a field out to keep its current value.

Ticket, 5 operations

create_ticketCreate ticketPOSTCreates a ticket in a ticket queue (title and ticket_queue_id required; get queue ids from list_ticket_queues) and returns it. Give the requester with user_id, or with user {"email": ...}.
delete_ticketDelete ticketDELETEPermanently delete a ticket from the system. This action cannot be undone. The ticket and all its associated data (comments, attachments, etc.) will be removed.
get_ticketGet ticketGETReturns one ticket by id: title, description, status_id, priority_id, queue, type, form, requester (user_id), assignee, dates and related data.
list_ticketsList ticketsGETRetrieve a list of tickets from your helpdesk. This endpoint supports pagination and sorting.
update_ticketUpdate ticketPUTUpdates a ticket and returns it. Partial update: only the fields you send change (status_id, priority_id, assigned_to_id, ticket_queue_id, title and so on); leave a field out to keep its current value.

Ticket queue, 5 operations

create_ticket_queueCreate ticket queuePOSTCreate a new ticket queue.
delete_ticket_queueDelete ticket queueDELETEDelete a ticket queue. This action cannot be undone.
get_ticket_queueGet ticket queueGETRetrieve details of a specific ticket queue.
list_ticket_queuesList ticket queuesGETRetrieve a list of ticket queues. This endpoint supports pagination.
update_ticket_queueUpdate ticket queuePUTUpdates an existing ticket queue and returns it. Partial update: only the fields you send change; leave a field out to keep its current value.

Ticket type, 5 operations

create_ticket_typeCreate ticket typePOSTCreate a new ticket type.
delete_ticket_typeDelete ticket typeDELETEDelete a ticket type. This action cannot be undone.
get_ticket_typeGet ticket typeGETRetrieve details of a specific ticket type.
list_ticket_typesList ticket typesGETRetrieve a list of ticket types.
update_ticket_typeUpdate ticket typePUTUpdates an existing ticket type and returns it. Partial update: only the fields you send change; leave a field out to keep its current value.

User, 5 operations

create_userCreate userPOSTCreates a user (an end user by default, or an agent with role_id) and returns it. send_welcome_email is required: 1 emails the new user an invitation, 0 creates the user silently.
delete_userDelete userDELETEDelete a user. This action cannot be undone.
get_userGet userGETRetrieve details of a specific user.
list_usersList usersGETRetrieve a list of users. This endpoint supports pagination.
update_userUpdate userPUTUpdates a user and returns it. Partial update: only the fields you send change. The email address cannot be changed here.

Access right, 4 operations

list_agent_queue_access_rightsList agent queue access rightsGETRetrieve the access rights for a specific restricted agent. Shows which ticket queues the agent has access to.
list_group_access_rightsList group access rightsGETRetrieve the access rights for a specific group. Shows which ticket queues the group has access to.
set_agent_access_rightSet agent access rightPOSTSet the access right for a restricted agent on a specific ticket queue. This allows or denies the agent access to tickets in that queue.
set_group_access_rightSet group access rightPOSTSet access rights for a group. This can be used to grant access to a single queue, multiple queues, or all queues depending on the parameters provided.

Attachment, 4 operations

delete_attachmentDelete attachmentDELETEDelete a specific attachment by its ID.
get_attachment_download_urlGet attachment download urlGETReturns a temporary, signed download URL (location) for one attachment by id (from list_ticket_attachments). It does not return the file itself: download it from that URL, before it expires.
list_ticket_attachmentsList ticket attachmentsGETRetrieve all attachments associated with a specific ticket.
upload_ticket_attachmentUpload ticket attachmentPOSTUploads a file to a ticket and returns the attachment. By default it shows with the ticket's original message; pass comment_id or staff_note_id (precedence comment_id, staff_note_id, staff_only) to put it under a reply or note.

Task, 4 operations

create_ticket_taskCreate ticket taskPOSTCreate a new task for a specific ticket.
delete_ticket_taskDelete ticket taskDELETEDelete a task from a specific ticket. This action cannot be undone.
list_ticket_tasksList ticket tasksGETRetrieve a list of tasks associated with a specific ticket.
update_ticket_taskUpdate ticket taskPUTUpdates an existing ticket task and returns it. Partial update: only the fields you send change; leave a field out to keep its current value.

Article, 3 operations

create_articleCreate articlePOSTCreate a new knowledge base article. Requires manager-level access. The account must be subscribed to a plan that supports the knowledge base.
get_articleGet articleGETRetrieve details of a specific knowledge base article. Requires manager-level access.
update_articleUpdate articlePUTUpdate an existing knowledge base article. Requires manager-level access. Only fields included in the request body are modified.

Event, 3 operations

get_eventGet eventGETRetrieve a single event log entry by its ID. Requires the Manager role.
list_eventsList eventsGETLists event log entries for the account, newest first (at most 30 per page); pass ticket_id to keep only one ticket's entries.
list_ticket_eventsList ticket eventsGETLists the event log entries of one ticket: creation, status changes, assignments, comments and other actions on it.

Group access, 3 operations

get_user_group_accessGet user group accessGETRetrieve the ticket access permission for a specific user and group.
list_user_group_accessList user group accessGETRetrieve all group ticket access permissions for a specific user.
set_user_group_accessSet user group accessPOSTSet the ticket access permission for a specific user and group.

Search, 3 operations

search_articlesSearch articlesGETSearches knowledge base articles visible to the caller and returns only each article's id and title (use get_article for the body). Any logged-in user may call it.
search_assetsSearch assetsGETSearches assets with an ElasticSearch query string (query), for example location.id:123 or display_name:*laptop*. Returns assets, 10 to 100 per page.
search_ticketsSearch ticketsGETSearches tickets with an ElasticSearch query string (query), for example status.id:\(\<50\) for open tickets. Returns tickets, at least 10 per page.

Tree, 3 operations

list_asset_types_treeList asset types treeGETRetrieve a list of asset types organized in tree structure
list_departments_treeList departments treeGETRetrieve a list of departments organized in tree structure
list_locations_treeList locations treeGETRetrieve a list of locations organized in tree structure

Comment, 2 operations

create_ticket_commentCreate ticket commentPOSTAdd a new comment to a specific ticket. Comments can be public (visible to ticket submitter) or internal notes (visible only to agents).
list_ticket_commentsList ticket commentsGETRetrieve a list of comments for a specific ticket. Comments include user-submitted responses and internal notes associated with the ticket.

File, 2 operations

delete_asset_fileDelete asset fileDELETERemoves one file from an asset (blob_id is the file id from the asset's file list) and returns the remaining files. Requires an Asset Manager (or Manager) with access to the asset's location.
upload_asset_filesUpload asset filesPOSTUploads one file (photo, document, invoice) to an asset and returns the asset's full file list. At most 10 files per asset. Requires an Asset Manager (or Manager) with access to the asset's location.

Set, 2 operations

set_agent_access_rights_bulkSet agent access rights bulkPOSTSet access rights for a restricted agent on multiple ticket queues at once. This allows or denies the agent access to multiple queues in a single request.
set_group_access_rights_bulkSet group access rights bulkPOSTSet access rights for a group on multiple ticket queues at once. This allows or denies the group access to multiple queues in a single request.

Staff note, 2 operations

create_ticket_staff_noteCreate ticket staff notePOSTAdd a new staff note to a specific ticket. Staff notes are internal comments visible only to agents and managers, not to the ticket submitter.
list_ticket_staff_notesList ticket staff notesGETRetrieve a list of staff notes for a specific ticket. Staff notes are internal comments visible only to agents and managers, not to the ticket submitter.

Team, 2 operations

get_teamGet teamGETRetrieve details of a specific team. Requires the caller's role to be Agent or above.
list_teamsList teamsGETRetrieve a list of teams in the account. This endpoint supports pagination. Requires the caller's role to be Agent or above.

Ticket form, 2 operations

get_ticket_formGet ticket formGETReturns one ticket form by id, with its settings. Requires the Manager role.
list_ticket_formsList ticket formsGETLists the ticket forms of the account. Requires the Manager role (unlike queue and type reads).

Add tag, 1 operation

add_ticket_tagAdd ticket tagPOSTAdd a tag to a specific ticket. You can specify the tag either by its ID or by its label. If a tag with the specified label doesn't exist, it will be created.

Agent, 1 operation

list_agent_access_rightsList agent access rightsGETLists every active agent with their ticket queue access rights (agents restricted to some queues and agents with access to all queues). Requires a Manager-level key.

Delete completed, 1 operation

delete_completed_ticket_tasksDelete completed ticket tasksPOSTDelete all completed tasks on a ticket. Returns the ticket's remaining (uncompleted) tasks.

Get by email, 1 operation

get_user_by_emailGet user by emailGETReturns the user whose email address matches email (an error when none does). Use it to find a requester's user id before creating a ticket. Requires an Agent role or above.

Merge, 1 operation

merge_tagMerge tagPOSTMerge this tag into another tag. All tickets carrying this tag are re-tagged with the target tag (`with_tag_id`) and this tag is removed.

Remove tag, 1 operation

remove_ticket_tagRemove ticket tagPOSTRemove a tag from a specific ticket. You can specify the tag either by its ID or by its label. The tag will be removed from the ticket if it exists.

Reorder, 1 operation

reorder_ticket_tasksReorder ticket tasksPOSTSets the display order of a ticket's tasks: keys lists every task id in the wanted order, and each task's position becomes its index. Returns the tasks.

Tech, 1 operation

list_agentsList agentsGETLists the agents (technicians, managers, administrators and the owner) of the account, as user records.

Use Mojo Helpdesk from Claude Code, Cursor or Codex

Connect Mojo Helpdesk in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Mojo Helpdesk operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Mojo Helpdesk

Create your workspace
Sign up free. Nothing to install.
Connect Mojo Helpdesk once
Add your Mojo Helpdesk connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.