wyre-ai/halopsa-mcp

开发工具

本页由 AI 翻译，技术细节请以原文为准。查看原文

3 stars 7 forks 质量 81 趋势 30Apache-2.0

Repository Install

HaloPSA的MCP服务器——机票、客户端、资产、合同和AI助手的报告工具

概览

一个用于与HalopSA互动的模型上下文协议(MCP)服务器,其特点是高效工具加载的决策树架构. 此服务器依赖于在 npm 注册簿上托管的 @ wyre- technology/ node-halopsa 。 GitHub套件没有匿名访问——尽管套件是公开的,但每个npm的安装都需要一个符号. 建云器为您运行 npm 安装, 因此您必须给它一个, 或安装失败 npm 错误 401 未经授权... npm.pkg.github.com 。 1. 创建有读取:packages范围(经典符号)的 GitHub。任何 GitHub 账户的作品——你确实需要成为 wyre-technology org 的成员来读取其公共软件包. 2. 在部署流程的推动下,将其添加为构建变量: --- 为您的 PAT 设定一个名为构建变量(工人 – 设置 – 构建 – 变量和密钥) 。 - 设置一个加密的 Env var, 命名范围为您的 PAT( . do/app. yaml 已经宣布了) .

概述（AI 翻译）

一个用于与HalopSA互动的模型上下文协议(MCP)服务器,其特点是高效工具加载的决策树架构.

□一克部署

[有价值]

** 在点击前:** 此服务器取决于@wyre-technology/node-halopsa,

挂载在** GitHub 包** npm 登记册上。 GitHub 软件包没有

匿名访问——尽管软件包是公开的,但每个npm install都需要一个标志。建云器为你跑 [T2],所以你必须给它一个,或者构建失败用 npm error 401 Unauthorized ... npm.pkg.github.com 。翻译:

创建 GitHub ** 个人访问托肯** 范围 (经典符号). 任何 GitHub 账户的作品 — 您需要** 成为该账户的成员 wyre-technology org读取其公共软件包。

受部署流量刺激时,将其添加为构建变量:

** 花旗工人**- 设置一个名为 ** [[T6] ** 的建构变量给您的 PAT (工人-设置-构建-变量和秘密).

** Digital Ocean App Platform** → 设置一个被命名为 ** [T7]的加密 Ev var. **

范围** 建造时间** 到您的 PAT (the .do/app.yaml) 已经宣布.

本页由 AI 翻译，技术细节请以原文为准。

README

以下为原文 README 节选，完整内容请查看原文。

HaloPSA MCP Server

A Model Context Protocol (MCP) server for interacting with HaloPSA, featuring a decision tree architecture for efficient tool loading.

One-Click Deployment

[!IMPORTANT] Before you click: this server depends on @wyre-technology/node-halopsa, which is hosted on the GitHub Packages npm registry. GitHub Packages has no anonymous access — even though the package is public, every npm install needs a token. The cloud builder runs npm install for you, so you must give it one, or the build fails with npm error 401 Unauthorized ... npm.pkg.github.com.

Create a GitHub Personal Access Token with the read:packages scope (classic token). Any GitHub account works — you do not need to be a member of the wyre-technology org to read its public packages.

Add it as a build variable when prompted by the deploy flow:

Cloudflare Workers → set a build variable named NODE_AUTH_TOKEN to your PAT (Workers → Settings → Build → Variables and Secrets).

DigitalOcean App Platform → set an encrypted env var named GITHUB_TOKEN with scope Build Time to your PAT (the .do/app.yaml already declares it).

[!NOTE] The DigitalOcean target builds the full Docker image and runs the complete MCP server over HTTP — this is the recommended path for operators. The Cloudflare Workers target is currently a thin entrypoint (the /mcp route returns 501 until the Workers transport adapter lands) and is best suited to gateway-style deployments; for a full self-hosted server prefer DigitalOcean or the prebuilt container image (ghcr.io/wyre-ai/halopsa-mcp).

Architecture

This MCP server uses a hierarchical tool loading approach instead of exposing all tools upfront:

Navigation Phase: Initially exposes only a navigation tool (halopsa_navigate)
Domain Selection: User selects a domain (tickets, clients, assets, agents, invoices, categories)
Domain Tools: Server exposes domain-specific tools after selection
Lazy Loading: Domain handlers and the HaloPSA client are loaded on-demand

This architecture provides:

Reduced cognitive load (fewer tools to choose from)
Faster initial load times
Better organization of related operations
Clear navigation state

Interactive Ticket Card (MCP Apps)

halopsa_tickets_get renders as an interactive card in MCP Apps hosts (Claude Desktop/web) with an in-card “Add note” round-trip via

在 GitHub 查看完整 README

安装

npx @wyre-ai/halopsa-mcp

新手？先看 mcpskill.org 教程 →

配置

{
  "mcpServers": {
    "halopsa": {
      "command": "npx",
      "args": ["@wyre-ai/halopsa-mcp"],
      "env": {
        "HALOPSA_CLIENT_ID": "your-client-id",
        "HALOPSA_CLIENT_SECRET": "your-client-secret",
        "HALOPSA_TENANT": "yourcompany"
      }
    }
  }
}