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

Name: HaloPSA
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to HaloPSA through the Vinkius — pass the Edge URL in the `mcps` parameter and every HaloPSA tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

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.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="HaloPSA Specialist",
    goal="Help users interact with HaloPSA effectively",
    backstory=(
        "You are an expert at leveraging HaloPSA tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in HaloPSA "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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.

When paired with CrewAI, HaloPSA becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call HaloPSA tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

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 CrewAI 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 CrewAI via MCP

Follow these steps to integrate the HaloPSA MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 11 tools from HaloPSA

Why Use CrewAI with the HaloPSA MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with HaloPSA through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

HaloPSA + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries HaloPSA for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries HaloPSA, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain HaloPSA tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries HaloPSA against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

HaloPSA MCP Tools for CrewAI (11)

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

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

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

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

HaloPSA + CrewAI FAQ

Common questions about integrating HaloPSA MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.