How to connect HaloPSA to Claude

Connect Claude Web, Desktop and Cowork to HaloPSA MCP. Create high-priority ticket for vpn outage, list recent tickets for network support, and more using natural language, with authentication handled for you.

HaloPSA logoHaloPSA
Oauth2

HaloPSA is a service desk platform for managing IT support tickets, customers, assets, and service operations. It brings support workflows into one place so teams can resolve issues faster and keep work organized.

85 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your HaloPSA account to Claude via Composio Connect, enabling it to create high-priority ticket for VPN outage, list recent tickets for network support, find customer site and assigned HaloPSA agent, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate HaloPSA with

Connecting HaloPSA to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your HaloPSA account

Back in Claude, ask it to connect to HaloPSA or give it any HaloPSA-related task.

For example, ask Claude to:

  • "Create high-priority ticket for VPN outage"
  • "List recent tickets for network support"
  • "Find customer site and assigned HaloPSA agent"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your HaloPSA account is ready to use.

What is the HaloPSA Claude Connector, and what's possible with it?

The HaloPSA MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your HaloPSA account. It provides structured and secure access to tickets, customers, sites, agents, assets, and service records, so your agent can create, inspect, retrieve, and delete HaloPSA records on your behalf.

  • Ticket creation and management: Have your agent create HaloPSA tickets from a summary and optional details, retrieve ticket information, or delete tickets while recording a reason.
  • Customer and site lookups: Let the agent retrieve customer and site records, including related activity, permissions, setup details, and ticket-type context when available.
  • Service team and user records: Direct your agent to inspect current agents, individual agents, teams, end users, and ticket-routing records to understand who handles support work.
  • Asset and service record inspection: Instruct your agent to retrieve assets, inventory or service items, contracts, appointments, invoices, quotations, projects, and related operational details.
  • Record cleanup: Have your agent delete supported HaloPSA records such as assets, customers, sites, users, teams, agents, projects, invoices, and other service records when they are no longer needed.

Troubleshooting

1. Why does Claude not use the Composio connector for HaloPSA?

The connector can show as connected, but Claude must use it in each HaloPSA conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to HaloPSA again.

2. Why does Claude show an MCP server error before HaloPSA connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for HaloPSA.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect HaloPSA.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the HaloPSA authorization link not work?

The Composio connector is one server. Your HaloPSA account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the HaloPSA connection.
  • Composio creates a fresh HaloPSA authorization link.
  • Open that link in your browser and finish the HaloPSA sign-in.

4. Why do HaloPSA actions fail after they worked before?

The HaloPSA connection can expire or lose permission.

  • Ask Claude to inspect the HaloPSA connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the HaloPSA account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in HaloPSA.
  • If the action still fails with a permission error, check that the connected account has that permission in HaloPSA itself.

5. How do I switch to a different HaloPSA account?

Claude can manage the HaloPSA connection for you.

  • Ask Claude to disconnect or delete the current HaloPSA account.
  • Ask Claude to connect HaloPSA again.
  • Open the new Composio authorization link for HaloPSA.
  • Sign in with the other HaloPSA account in the browser.
  • After the account connects, ask Claude to retry the HaloPSA task.

6. Why is my HaloPSA connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your HaloPSA connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If HaloPSA tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect HaloPSA.
TOOLS

Supported Tools

Every HaloPSA action and event your agent gets out of the box.

Create Ticket

Create one HaloPSA ticket from a summary and optional details and routing IDs; sends the provider-required one-item array body.

Delete Agent

Request deletion of one HaloPSA agent by numeric ID.

Delete Appointment

Delete one HaloPSA appointment by numeric ID.

Delete Asset

Delete one HaloPSA asset by numeric ID.

Delete Attachment

Delete one HaloPSA attachment by numeric ID.

Delete Client Contract

Delete one HaloPSA client contract by numeric ID.

Delete Customer

Delete one HaloPSA customer by numeric ID.

Delete Invoice

Delete one HaloPSA invoice by numeric ID.

Delete Item

Delete one HaloPSA inventory or service item by numeric ID.

Delete Knowledge Base Article

Delete one HaloPSA knowledge-base article by numeric ID.

Delete Opportunity

Delete one HaloPSA sales opportunity by numeric ID.

Delete Project

Delete one HaloPSA project by numeric ID.

Delete Quotation

Delete one HaloPSA quotation by numeric ID.

Delete Report

Delete one HaloPSA report definition by numeric ID.

Delete Site

Delete one HaloPSA customer site by numeric ID.

Delete Status

Delete one HaloPSA ticket-status configuration record by numeric ID.

Delete Supplier

Delete one HaloPSA supplier by numeric ID.

Delete Team

Delete one HaloPSA team by numeric ID.

Delete Ticket

Delete one HaloPSA ticket by numeric ID, optionally recording a reason.

Delete Ticket Action

Delete one HaloPSA ticket action by numeric action ID and its parent ticket ID.

Delete Ticket Type

Delete one HaloPSA ticket-type configuration record by numeric ID.

Delete User

Delete one HaloPSA end user by numeric ID.

Get Agent

Return one HaloPSA agent by numeric ID.

Get Appointment

Return one HaloPSA appointment by numeric ID, optionally with extra detail objects.

Get Asset

Return one HaloPSA asset by numeric ID, optionally including activity, allowed statuses, details, diagram data, and hierarchy data.

Get Attachment

Download one HaloPSA attachment by numeric ID.

Get Client Contract

Return one HaloPSA client contract by numeric ID, with optional expanded billing, asset, user, schedule, and period details.

Get Current Agent

Return a compact identity for the HaloPSA agent authorized by the current connection, without claims or access-control records.

Get Customer

Return one HaloPSA customer by numeric ID, with optional expanded, activity, ticket-type, period, and pre-pay data.

Get Invoice

Return one HaloPSA invoice by numeric ID, optionally with extra detail objects.

Get Item

Return one HaloPSA inventory or service item by numeric ID, optionally with expanded details and tenant-specific accounting data; additional provider fields are preserved.

Get Knowledge Base Article

Return one HaloPSA knowledge-base article by numeric ID, optionally with expanded details and language or organisation context.

Get Opportunity

Return one HaloPSA sales opportunity by numeric ID, optionally with extra provider detail objects.

Get Project

Return one HaloPSA project by numeric ID, optionally with expanded details.

Get Quotation

Return one HaloPSA quotation by numeric ID, optionally with expanded details or portal-view context.

Get Report

Return one HaloPSA report definition by numeric ID.

Get Site

Return one HaloPSA customer site by numeric ID, with optional customer, permission, activity, detail, setup, and ticket-type context.

Get Status

Return one HaloPSA ticket-status configuration record by numeric ID, optionally including its detailed configuration.

Get Supplier

Return one HaloPSA supplier by numeric ID, optionally including expanded details; additional provider fields are preserved.

Get Team

Return one HaloPSA team by numeric ID, optionally including agent details and expanded team objects.

Get Ticket

Return one HaloPSA ticket by numeric ID, with core assignment and classification fields and optional expanded details and most recent action.

Get Ticket Action

Get one HaloPSA ticket action by numeric action ID, optionally providing its ticket ID and requesting expanded details.

Get Ticket Type

Return one HaloPSA ticket type by numeric ID.

Get User

Return one HaloPSA end user by numeric ID, with optional customer, site, ticket-type, opportunity, supplier, activity, billing, asset, and detail context.

List Agents

Return compact HaloPSA agent records for assignment lookup, optionally filtered by name, email address, telephone number, or team ID.

List Appointments

Return one page of HaloPSA appointments, optionally filtered by customer, ticket, date range, or search text.

List Assets

Return one page of HaloPSA assets, optionally filtered by customer, site, user, asset type, search text, and active state.

List Attachments

List HaloPSA attachment metadata, optionally for one ticket.

List Client Contracts

Return one page of HaloPSA client contracts, optionally filtered by customer, site, search text, and active state.

List Customers

Return one page of HaloPSA customers, optionally filtered by name and active state.

List Invoices

Return one page of HaloPSA invoices, optionally filtered by date, customer, site, ticket, user, or search text.

List Items

Return one page of HaloPSA inventory and service items with the provider's documented status, asset, supplier, accounting, stock, search, and ordering filters.

List Knowledge Base Articles

Return one page of HaloPSA knowledge-base articles using the provider's documented status, access, relationship, language, search, and ordering filters.

List Opportunities

Return one page of HaloPSA sales opportunities, optionally filtered by customer, assignment, status, date range, or search text.

List Priorities

Return HaloPSA policy-priority mappings used to classify tickets, optionally filtered by SLA policy ID.

List Projects

Return one page of HaloPSA projects.

List Quotations

Return HaloPSA quotations with customer, state, approval, processing, text, attachment, ordering, and page filters.

List Reports

Return one page of HaloPSA report definitions with the provider's documented access, chart, customer, publication, ordering, group, search, and type filters.

List Sites

Return one page of HaloPSA customer sites, optionally filtered by customer, name, and active state.

List Statuses

Return HaloPSA ticket statuses, optionally constrained to a ticket type or a specific ticket's valid context.

List Suppliers

Return one page of HaloPSA suppliers with the provider's documented status, integration, ordering, search, and top-level filters.

List Teams

Return HaloPSA teams available for ticket assignment, optionally limited to the current agent's teams or a department.

List Ticket Actions

List HaloPSA ticket actions, optionally filtering by occurrence date range and whether attachment details are included.

List Tickets

Return one page of HaloPSA tickets, optionally filtered by customer, site, user, status, assigned agent, or text search.

List Ticket Types

Return ticket types available for ticket classification, optionally limited to types that agents can create for a customer.

List Users

Return one page of HaloPSA end users, optionally filtered by customer, site, name, and active state.

Upsert Agent

Create or update HaloPSA agent profiles, team memberships, account enablement, administrator access, working hours, licensing, costs, notifications, and approval settings in one array request.

Upsert Appointment

Create or update HaloPSA appointments in one array request.

Upsert Asset

Create or update one or more HaloPSA assets.

Upsert Client Contract

Create or update one or more HaloPSA client contracts.

Upsert Customer

Create or update one or more HaloPSA customers in the endpoint's array body.

Upsert Invoice

Create or update HaloPSA invoice records and their typed line items.

Upsert Item

Create or update HaloPSA inventory and service items in one array request.

Upsert Knowledge Base Article

Create or update one or more HaloPSA knowledge-base articles through POST /KBArticle.

Upsert Opportunity

Upsert HaloPSA sales opportunities: each resource item with id updates that record, while each item with id omitted creates a record.

Upsert Project

Create or update HaloPSA project records, typed milestones, and tags.

Upsert Quotation

Create or update HaloPSA quotation records and typed quotation lines.

Upsert Report

Create or update HaloPSA report definitions in one array request.

Upsert Site

Create or update one or more HaloPSA customer sites.

Upsert Status

Create or update HaloPSA ticket statuses in one array request.

Upsert Supplier

Create or update one or more HaloPSA suppliers through POST /Supplier.

Upsert Team

Create or update HaloPSA teams in one array request.

Upsert Ticket Action

Create or update ticket notes and work-log actions, optionally recording time or applying a ticket status, without sending email.

Upsert Ticket Type

Create or update HaloPSA ticket types in one array request.

Upsert User

Create or update one or more HaloPSA end-user records without sending welcome email.

FAQ

Frequently asked questions

With a standalone HaloPSA MCP server, the agents and LLMs can only access a fixed set of HaloPSA tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from HaloPSA and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right HaloPSA tools.

Yes, absolutely. You can configure which HaloPSA scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your HaloPSA data and credentials are handled as safely as possible.

Start with HaloPSA.It takes 30 seconds.

Managed auth, hosted MCP servers, and every HaloPSA tool your agent needs.Free to start.

Start building