How do I set up my HaloPSA API credentials?

Log in as an Administrator, go to **Configuration > Integrations > Halo API**. In 'View Applications', create a new app with the 'Agent' login type and grant the necessary permissions. You will receive your Client ID and Client Secret there.

What are the Resource and Auth URLs?

The Resource URL is typically `https://your-tenant.halopsa.com/api` and the Auth URL is `https://your-tenant.halopsa.com/auth`. Replace 'your-tenant' with your actual HaloPSA instance name.

Can I perform actions on tickets, like changing status?

Yes! Use the `perform_ticket_action` tool by providing the ticket ID and the specific action ID configured in your Halo instance. You can also add an optional note.

Is the integration secure?

Yes, it uses industry-standard OAuth2 Client Credentials flow. Your credentials are encrypted and stored securely within the Vinkius Cloud infrastructure.

HaloPSA MCP Server for Claude Desktop 11 tools — connect in under 2 minutes

Name: HaloPSA
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 11 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install HaloPSA and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "halopsa": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About HaloPSA MCP Server

Connect your HaloPSA instance to any AI agent and take full control of your service desk and PSA workflows through natural conversation.

Claude Desktop is the definitive way to connect HaloPSA to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 11 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

Ticket Management — List all tickets, retrieve detailed information, and create new support requests effortlessly.
Client & User Oversight — Access lists of clients (customers) and users defined in your system to ensure data accuracy.
Asset Tracking — Monitor the hardware and software assets managed within HaloPSA.
Team Coordination — Browse your organizational teams and sites to facilitate better resource allocation.
Financial Insights — Retrieve lists of invoices and customer contracts for quick status checks.
Action Execution — Perform updates on tickets, add internal notes, or change statuses directly from the chat.

The HaloPSA MCP Server exposes 11 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect HaloPSA to Claude Desktop via MCP

Follow these steps to integrate the HaloPSA MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using HaloPSA

Look for the 🔌 icon in the chat — your 11 tools are now available

Why Use Claude Desktop with the HaloPSA MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with HaloPSA through the Model Context Protocol.

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

HaloPSA + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the HaloPSA MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

HaloPSA MCP Tools for Claude Desktop (11)

These 11 tools become available when you connect HaloPSA to Claude Desktop via MCP:

create_ticket

Create a new ticket in HaloPSA

get_ticket

Get detailed information about a specific ticket

list_assets

List all assets defined in HaloPSA

list_clients

List all clients (customers) in HaloPSA

list_contracts

List all customer contracts

list_invoices

List all invoices in HaloPSA

list_sites

List all sites/locations

list_teams

List all teams configured in the service desk

list_tickets

List all tickets in HaloPSA

list_users

List all users in the HaloPSA instance

perform_ticket_action

Perform an action on a ticket (e.g., add note, change status)

Example Prompts for HaloPSA in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with HaloPSA immediately.

"List all open tickets assigned to me."

"Add an internal note to ticket ID 1021: 'Waiting for vendor feedback'."

"Show me the asset list for Client 'Acme Corp'."

Troubleshooting HaloPSA MCP Server with Claude Desktop

Common issues when connecting HaloPSA to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

HaloPSA + Claude Desktop FAQ

Common questions about integrating HaloPSA MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.