HaloPSA vs Swifteq MCP Server for Zendesk
A side-by-side look at the HaloPSA and Swifteq MCP Server for Zendesk MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
Swifteq MCP Server for ZendeskSupport & Service Management · Remote HTTP/SSEConnect Claude, ChatGPT or any AI assistant to Zendesk tickets, CSAT, macros and Help Center.37FairAuth: not declaredVerdict: choose HaloPSA for support & service management work as a local process; choose Swifteq MCP Server for Zendesk for support & service management over a hosted endpoint. 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.
SChoose Swifteq MCP Server for Zendesk when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Swifteq MCP Server for Zendesk | |
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 41/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | HALOPSA_CLIENT_IDHALOPSA_CLIENT_SECRETHALOPSA_TENANTHALOPSA_BASE_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | — |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View HaloPSA | View Swifteq MCP Server for Zendesk |
Tools & capabilities
HaloPSA tools
No tool names declared yet. Check the project README from the listing page.
Swifteq MCP Server for Zendesk tools
No tool names declared yet. Check the project README from 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"
}
}
}
}
Swifteq MCP Server for Zendesk
{
"mcpServers": {
"swifteq-mcp-server-for-zendesk": {
"command": "npx",
"args": [
"-y",
"swifteq-mcp-server-for-zendesk"
]
}
}
}
Frequently asked questions
HaloPSA is categorized under Support & Service Management and uses a local stdio subprocess. Swifteq MCP Server for Zendesk belongs to Support & Service Management and uses a remote HTTP/SSE transport. Pick HaloPSA for support & service management work and Swifteq MCP Server for Zendesk for support & service management.
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. Swifteq MCP Server for Zendesk has no declared pricing — check the project's own site. 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 swifteq-mcp-server-for-zendesk 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 2 views, 0 installs and 3 GitHub stars. Swifteq MCP Server for Zendesk has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.