How to Use the HaloPSA MCP in CrewAI

Q: Can I limit which HaloPSA tools a specific CrewAI agent can use?

Yes. You configure MCPServerHTTP with a toolfilter to restrict tools. For example, your research agent only gets listtickets, while your admin agent gets performticketaction.

Q: How does CrewAI handle complex HaloPSA team assignments?

Your agents query listteams and listusers to see who is available. The coordinator agent then uses this directory data to assign the ticket to the right person.

Q: How secure is my HaloPSA client and user directory data?

All calls to listclients and listusers run inside isolated, ephemeral execution environments. No data is cached or stored, ensuring your user directory remains strictly confidential.

Deploy a crew of specialized agents to manage your HaloPSA tickets, assets, and teams autonomously.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect HaloPSA MCP to CrewAI

Create your Vinkius account to connect HaloPSA to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup HaloPSA with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous service desk operations via CrewAI

This HaloPSA MCP Server exposes `list_tickets` and `perform_ticket_action` to your CrewAI agents. You set up a triaging crew where one agent categorizes incoming requests and another agent executes the assignments. The agents collaborate using shared memory. If the triager identifies an urgent server issue, the coordinator agent immediately updates the ticket priority and assigns it to the on-call team.

Multi-agent asset verification with CrewAI

The `list_assets` and `get_ticket` tools let your CrewAI agents audit hardware issues. A research agent pulls the asset history while an analysis agent checks the active ticket details. They work in parallel to diagnose the problem. The crew cross-references the asset model with known bugs, writes a summary, and logs a detailed note on the ticket.

Client and contract alignment using this MCP Server

Our MCP Server provides `list_clients` and `list_contracts` to let your CrewAI agents monitor service agreements. A billing agent reviews active contracts while an operations agent checks client tickets. This setup flags out-of-scope work automatically. If a client requests support without an active contract, the crew alerts your account manager and updates the ticket status.

Setup guide

Set up HaloPSA MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke HaloPSA tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="HaloPSA Analyst",
    goal="Access and analyze HaloPSA data via MCP.",
    backstory="Expert analyst with direct HaloPSA access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent HaloPSA transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

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

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="HaloPSA Analyst",
        goal="Access and analyze HaloPSA data via MCP.",
        backstory="Expert analyst with direct HaloPSA access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent HaloPSA transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by HaloPSA. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect HaloPSA now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about HaloPSA MCP in CrewAI

CrewAI agents use shared memory to pass outputs. A research agent calls `get_ticket`, and the resulting data is immediately available to the coordinator agent to perform the next action.

Yes. You configure `MCPServerHTTP` with a `tool_filter` to restrict tools. For example, your research agent only gets `list_tickets`, while your admin agent gets `perform_ticket_action`.

Your agents query `list_teams` and `list_users` to see who is available. The coordinator agent then uses this directory data to assign the ticket to the right person.

No. You only need the core package. The agents connect to the hosted Vinkius MCP Server, which provides all 11 tools out of the box.

All calls to `list_clients` and `list_users` run inside isolated, ephemeral execution environments. No data is cached or stored, ensuring your user directory remains strictly confidential.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript