HaloPSA vs Git
A side-by-side look at the HaloPSA and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose HaloPSA for support & service management work as a local process; choose Git for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose HaloPSA when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET, HALOPSA_TENANT, HALOPSA_BASE_URL.
Choose Git when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Version Control |
| Quality signal | 41/100 · Fair | 81/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | HALOPSA_CLIENT_IDHALOPSA_CLIENT_SECRETHALOPSA_TENANTHALOPSA_BASE_URL | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 3 | 91,526 |
| Directory activity | 3 views 0 installs 0 upvotes | 51 views 0 installs 0 upvotes |
| Tools | Not listed | 16 |
| Full listing | View HaloPSA | View Git |
Tools & capabilities
HaloPSA tools
No tool names declared yet. Check the project README from the listing page.
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
HaloPSA
{
"mcpServers": {
"halopsa-2": {
"command": "npx",
"args": [
"-y",
"@wyre-ai/halopsa-mcp"
],
"env": {
"HALOPSA_CLIENT_ID": "YOUR_HALOPSA_CLIENT_ID_HERE",
"HALOPSA_CLIENT_SECRET": "YOUR_HALOPSA_CLIENT_SECRET_HERE",
"HALOPSA_TENANT": "YOUR_HALOPSA_TENANT_HERE",
"HALOPSA_BASE_URL": "YOUR_HALOPSA_BASE_URL_HERE"
}
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Frequently asked questions
HaloPSA is categorized under Support & Service Management and uses a local stdio subprocess. Git belongs to Version Control and uses a local stdio subprocess. Pick HaloPSA for support & service management work and Git for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
HaloPSA has no declared pricing — check the project's own site. Git is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add halopsa-2 and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, HaloPSA has a quality signal of 41/100 (Fair) with 3 views, 0 installs and 3 GitHub stars. Git has 81/100 (Excellent) with 51 views, 0 installs and 91,526 GitHub stars.