HaloPSA MCP server Let your AI agent work your HaloPSA tickets.

ToolWhat it doesAccess

• list_tickets Tickets matching a search, status, client, team or agent. read

  Returns the tickets your Halo list shows, with ID, summary, client, ticket type, status, priority, assigned agent and team, and the response and resolution targets the SLA sets. Filters are optional and combine. Pass next_page back as page for the next page.

  MCP callhalopsa_read → list_tickets

  REST endpointGET https://cotlet.dev/api/v1/halopsa/tickets

  Parameters

  Parameters: list_tickets

  Name	Type	Description
  query string	string	Only tickets whose summary or details contain this text.
  status string	string	Status name exactly as your Halo shows it, for example "Open".
  client_id integer	integer	Client ID from list_clients.
  team string	string	Team name exactly as your Halo shows it.
  agent string	string	Agent name, or "unassigned" for tickets with no agent.
  open_only boolean	boolean	true skips closed tickets.
  limit integer	integer	How many tickets to return.
  page integer	integer	Page number from next_page.

  Example response

  {
    "tickets": [
      {
        "ticket_id": 4821,
        "summary": "Printer offline on floor 2",
        "client": "Northwind Logistics",
        "ticket_type": "Incident",
        "status": "Open",
        "priority": "High",
        "agent": null,
        "team": "Service Desk",
        "response_target": "met",
        "resolution_target": "2026-11-05T15:00:00Z"
      },
      {
        "ticket_id": 4822,
        "summary": "VPN drops every hour",
        "client": "Brightside Dental",
        "ticket_type": "Incident",
        "status": "Open",
        "priority": "Medium",
        "agent": "Lena Ortiz",
        "team": "Service Desk",
        "response_target": "met",
        "resolution_target": "2026-11-06T09:00:00Z"
      }
    ],
    "next_page": null
  }

• get_ticket One ticket with its details and every action on it. read

  Returns the ticket fields, the user who raised it, and its actions in the order Halo shows them: replies, private notes and logged time, each with who added it. Use it before replying or adding a note so the agent reads the whole history first.

  MCP callhalopsa_read → get_ticket

  REST endpointGET https://cotlet.dev/api/v1/halopsa/tickets/{ticket_id}

  Parameters

  Parameters: get_ticket

  Name	Type	Description
  ticket_id integer required	integer	Ticket ID from list_tickets.

  Example input

  {
    "ticket_id": 1
  }

  Example response

  {
    "ticket_id": 4821,
    "summary": "Printer offline on floor 2",
    "details": "The shared printer shows offline since this morning. Restarting it did not help.",
    "user": "Dana Whitfield",
    "client": "Northwind Logistics",
    "status": "Open",
    "priority": "High",
    "agent": null,
    "actions": [
      {
        "action_id": 1,
        "kind": "note",
        "by": "Dana Whitfield",
        "text": "Restarting it did not help.",
        "created_at": "2026-11-05T08:12:00Z"
      }
    ]
  }

• list_ticket_types Ticket types with ID and name. read

  Returns the ticket types set up under Configuration > Tickets > Ticket Types, and says which ones agents may log tickets of. Use the ticket_type_id with create_ticket.

  MCP callhalopsa_read → list_ticket_types

  REST endpointGET https://cotlet.dev/api/v1/halopsa/ticket-types

  Parameters

  No parameters.

  Example response

  {
    "ticket_types": [
      {
        "ticket_type_id": 1,
        "name": "Incident",
        "agents_can_log": true
      },
      {
        "ticket_type_id": 2,
        "name": "Service Request",
        "agents_can_log": true
      }
    ]
  }

• create_ticket Log a new ticket for a client and user. writeasks first

  Logs the ticket as you, with the ticket type, summary and details you give, and returns its ID and link. A ticket type that does not allow agents to log it is refused. Halo may email the user, depending on your notification settings. By default you confirm each call; you can switch that off for this tool.

  MCP callhalopsa_write → create_ticket

  REST endpointPOST https://cotlet.dev/api/v1/halopsa/clients/{client_id}/tickets

  Parameters

  Parameters: create_ticket

  Name	Type	Description
  client_id integer required	integer	Client ID from list_clients.
  user_email string	string	Email of the user who raised it, from get_client.
  ticket_type_id integer required	integer	Ticket type ID from list_ticket_types.
  summary string required	string	One-line title of the ticket.
  details string	string	Full description.
  priority string	string	Priority name exactly as your Halo shows it.

  Example input

  {
    "client_id": 1,
    "ticket_type_id": 1,
    "summary": "summary"
  }

  Example response

  {
    "ticket_id": 4830,
    "summary": "Laptop battery swells",
    "client": "Brightside Dental",
    "ticket_type": "Incident",
    "status": "New",
    "url": "https://yourcompany.halopsa.com/tickets?id=4830"
  }

• update_ticket Change the status, priority, team or agent of a ticket. writeasks first

  Changes only the fields you pass and returns the ticket as it is now. A status change moves the ticket on in its workflow, and Halo may notify the user or the agent, depending on your notification settings. A change Halo does not allow for that ticket comes back as an error. By default you confirm each call; you can switch that off for this tool.

  MCP callhalopsa_write → update_ticket

  REST endpointPATCH https://cotlet.dev/api/v1/halopsa/tickets/{ticket_id}

  Parameters

  Parameters: update_ticket

  Name	Type	Description
  ticket_id integer required	integer	Ticket ID from list_tickets.
  status string	string	Status name exactly as your Halo shows it.
  priority string	string	Priority name exactly as your Halo shows it.
  team string	string	Team name exactly as your Halo shows it.
  agent string	string	Agent name exactly as your Halo shows it.

  Example input

  {
    "ticket_id": 1
  }

  Example response

  {
    "ticket_id": 4821,
    "status": "Open",
    "priority": "High",
    "team": "Service Desk",
    "agent": "Lena Ortiz"
  }

ToolWhat it doesAccess

• add_note Add a private note to a ticket. writeasks first

  Adds a note only agents see, never the user, and returns its action ID. A note cannot be deleted through Cotlet. Halo may notify the agent on the ticket. By default you confirm each call; you can switch that off for this tool.

  MCP callhalopsa_write → add_note

  REST endpointPOST https://cotlet.dev/api/v1/halopsa/tickets/{ticket_id}/notes

  Parameters

  Parameters: add_note

  Name	Type	Description
  ticket_id integer required	integer	Ticket ID from list_tickets.
  note string required	string	Text of the note.

  Example input

  {
    "ticket_id": 1,
    "note": "note"
  }

  Example response

  {
    "ticket_id": 4821,
    "action_id": 2,
    "kind": "note",
    "created_at": "2026-11-05T08:40:00Z"
  }

• reply_to_user Send a reply on a ticket that the user sees. writeasks first

  Adds a reply the user can read and sends it by email as Halo does for any agent reply, then returns its action ID. The reply cannot be recalled once sent. By default you confirm each call; you can switch that off for this tool.

  MCP callhalopsa_write → reply_to_user

  REST endpointPOST https://cotlet.dev/api/v1/halopsa/tickets/{ticket_id}/user/replies

  Parameters

  Parameters: reply_to_user

  Name	Type	Description
  ticket_id integer required	integer	Ticket ID from list_tickets.
  message string required	string	Text of the reply.

  Example input

  {
    "ticket_id": 1,
    "message": "message"
  }

  Example response

  {
    "ticket_id": 4821,
    "action_id": 3,
    "kind": "reply",
    "sent_to": "dana@example.com",
    "created_at": "2026-11-05T08:45:00Z"
  }

ToolWhat it doesAccess

• search_knowledge_base Knowledge base articles that match a question. read

  Searches the Halo knowledge base and returns each match with its ID, title and the article text. Pass a ticket summary or the user's own words as the query. Use it to find steps for a reply or to link an article in a note.

  MCP callhalopsa_read → search_knowledge_base

  REST endpointGET https://cotlet.dev/api/v1/halopsa/knowledge-bases/search

  Parameters

  Parameters: search_knowledge_base

  Name	Type	Description
  query string required	string	Words to search for.
  limit integer	integer	How many articles to return.

  Example input

  {
    "query": "query"
  }

  Example response

  {
    "articles": [
      {
        "article_id": 311,
        "title": "Reconnect a network printer",
        "text": "1. Open Settings > Printers. 2. Remove the printer. 3. Add it again by its IP address."
      }
    ]
  }

ToolWhat it doesAccess

• list_clients Clients with ID, name and number of open tickets. read

  Lists the clients in your Halo, filtered by part of the name if you pass one. Use the client_id with list_tickets, create_ticket and list_assets. Counts are of tickets open now.

  MCP callhalopsa_read → list_clients

  REST endpointGET https://cotlet.dev/api/v1/halopsa/clients

  Parameters

  Parameters: list_clients

  Name	Type	Description
  query string	string	Only clients whose name contains this text.
  limit integer	integer	How many clients to return.

  Example response

  {
    "clients": [
      {
        "client_id": 12,
        "name": "Northwind Logistics",
        "open_tickets": 3
      },
      {
        "client_id": 15,
        "name": "Brightside Dental",
        "open_tickets": 1
      }
    ]
  }

• get_client One client with its sites and users. read

  Returns the client's details, its sites and its users, with the email of each user. Use it to pick the right user before create_ticket or reply_to_user.

  MCP callhalopsa_read → get_client

  REST endpointGET https://cotlet.dev/api/v1/halopsa/clients/{client_id}

  Parameters

  Parameters: get_client

  Name	Type	Description
  client_id integer required	integer	Client ID from list_clients.

  Example input

  {
    "client_id": 1
  }

  Example response

  {
    "client_id": 12,
    "name": "Northwind Logistics",
    "sites": [
      "Head office"
    ],
    "users": [
      {
        "name": "Dana Whitfield",
        "email": "dana@example.com"
      },
      {
        "name": "Jon Reyes",
        "email": "jon@example.com"
      }
    ]
  }

• list_assets Assets matching a search or a client. read

  Returns assets with ID, name, type, client and the user it is assigned to. Use it to name the right device in a ticket note.

  MCP callhalopsa_read → list_assets

  REST endpointGET https://cotlet.dev/api/v1/halopsa/assets

  Parameters

  Parameters: list_assets

  Name	Type	Description
  query string	string	Only assets whose name contains this text.
  client_id integer	integer	Client ID from list_clients.
  limit integer	integer	How many assets to return.

  Example response

  {
    "assets": [
      {
        "asset_id": 903,
        "name": "PRN-FLOOR2",
        "type": "Printer",
        "client": "Northwind Logistics",
        "user": "Dana Whitfield"
      }
    ]
  }

ToolWhat it doesAccess

• get_timesheet Time logged by an agent on one day. read

  Returns each action the agent logged that day, with the ticket, the time spent and whether it is billable, as the Time Tracking timesheet shows it. Without an agent it reads your own timesheet. Use it before log_time so time is not logged twice.

  MCP callhalopsa_read → get_timesheet

  REST endpointGET https://cotlet.dev/api/v1/halopsa/timesheet

  Parameters

  Parameters: get_timesheet

  Name	Type	Description
  date string required	string	Day as YYYY-MM-DD.
  agent string	string	Agent name. Default: you.

  Example input

  {
    "date": "date"
  }

  Example response

  {
    "date": "2026-11-05",
    "entries": [
      {
        "ticket_id": 4822,
        "note": "Checked VPN logs",
        "minutes": 20,
        "billable": true
      }
    ],
    "total_minutes": 20
  }

• log_time Log time spent on a ticket. writeasks first

  Adds a log time action to the ticket and to your timesheet, with the minutes and the note you give, and returns the action ID. The time can feed billing, so check the amount. To remove it, delete the action in Halo. By default you confirm each call; you can switch that off for this tool.

  MCP callhalopsa_write → log_time

  REST endpointPOST https://cotlet.dev/api/v1/halopsa/tickets/{ticket_id}/times

  Parameters

  Parameters: log_time

  Name	Type	Description
  ticket_id integer required	integer	Ticket ID from list_tickets.
  minutes integer required	integer	Time spent, in minutes.
  note string	string	What was done.
  billable boolean	boolean	true if the time is billable. Default: your Halo's default for the ticket.

  Example input

  {
    "ticket_id": 4821,
    "minutes": 30,
    "note": "Re-added the printer by IP address",
    "billable": true
  }

  Example response

  {
    "ticket_id": 4821,
    "action_id": 4,
    "minutes": 30,
    "billable": true,
    "created_at": "2026-11-05T09:10:00Z"
  }

• get_report_data The rows of a saved report. read

  Runs one saved report from the Reports area and returns its columns and rows. The report decides what is counted, so build the report in Halo first, then ask for it by name. Pass next_page back as page for more rows.

  MCP callhalopsa_read → get_report_data

  REST endpointGET https://cotlet.dev/api/v1/halopsa/report-data

  Parameters

  Parameters: get_report_data

  Name	Type	Description
  report string required	string	Report name exactly as your Halo shows it.
  page integer	integer	Page number from next_page.

  Example input

  {
    "report": "report"
  }

  Example response

  {
    "report": "Weekly tickets",
    "columns": [
      "Client",
      "Opened",
      "Closed"
    ],
    "rows": [
      [
        "Northwind Logistics",
        9,
        7
      ],
      [
        "Brightside Dental",
        4,
        4
      ]
    ],
    "next_page": null
  }