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 VS Code Copilot 11 tools — connect in under 2 minutes

Name: HaloPSA
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 11 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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": {
      "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.

GitHub Copilot Agent mode brings HaloPSA data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 11 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the HaloPSA MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using HaloPSA

Ask Copilot: "Using HaloPSA, help me..." — 11 tools available

Why Use VS Code Copilot with the HaloPSA MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with HaloPSA through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

HaloPSA + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the HaloPSA MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

HaloPSA MCP Tools for VS Code Copilot (11)

These 11 tools become available when you connect HaloPSA to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting HaloPSA to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

HaloPSA + VS Code Copilot FAQ

Common questions about integrating HaloPSA MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.