alga-psa-api-patternslisted
Install: claude install-skill WYRE-AI/msp-claude-plugins
# Alga PSA API Patterns
## Overview
Alga PSA is Nine Minds' open-source PSA. Every MSP runs its own instance, so the
connection carries that instance's URL as well as an API key. The Conduit connector
(`alga-psa`, sidecar `alga-psa-mcp`) exposes 42 hand-written tools, every one a `GET`
against `{instance}/api/v1`.
## Read-only surface
- No tool creates, updates or deletes anything. The sidecar's HTTP client can only send
`GET`, and its only tool tier is `read`.
- Conduit's catalog marks all 42 tools as plain reads. **None is admin-gated**, and
there is no write or destructive tier an operator could enable.
- When a workflow needs a change in Alga (close a ticket, approve a time sheet, reassign
work), say it can't be done through this connector, draft the exact change, and leave
it for a person to make in the Alga UI.
## Connection and authentication
The fields are entered once in the Conduit web UI (`/connect/alga-psa`). Conduit stores
them and injects the headers below on every request; nothing is set on the client, and
Conduit drops any `X-Alga-*` header a client sends.
| Conduit field | Header | Required | Notes |
|---|---|---|---|
| Alga Instance URL | `X-Alga-Instance-Url` | Yes | Public `https://` origin, no path (an `/api/v1` suffix is accepted and dropped) |
| API Key | `X-Alga-Api-Key` | Yes | Sent upstream as `x-api-key` by the sidecar |
| Tenant ID | `X-Alga-Tenant-Id` | No | A UUID, only when Alga support supplies one; a wrong value fails every call