# Avanan MSP (Legacy SmartAPI) [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/wyre-technology/avanan-legacy-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/avanan-msp-legacy-smartapi-2

## Description
MCP server for the Avanan MSP SmartAPI — manage child MSPs, users, tenants, licenses, and usage.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "avanan-msp-legacy-smartapi": {
    "url": "https://smart-api-production-1-us.avanan.net"
  }
}
```

## Documentation & README

# avanan-legacy-mcp

MCP server for the **Avanan MSP SmartAPI** (the "legacy" Avanan MSP tenant management
API — distinct from `avanan-mcp`, which targets the Checkpoint Harmony Email & Collaboration
HEC API).

Implements the Jan 2024 Avanan MSP SmartAPI Reference Guide:

| Group | Tools |
| --- | --- |
| Child MSPs | `avanan_list_msp_partners`, `avanan_create_msp_partner`, `avanan_delete_msp_partner` |
| MSP users | `avanan_list_msp_users`, `avanan_get_msp_user`, `avanan_create_msp_user`, `avanan_update_msp_user`, `avanan_delete_msp_user` |
| Customer tenants | `avanan_list_tenants`, `avanan_get_tenant`, `avanan_create_tenant`, `avanan_delete_tenant` |
| Licenses | `avanan_list_licenses`, `avanan_list_addons`, `avanan_assign_license` |
| Usage | `avanan_get_monthly_usage`, `avanan_get_daily_usage` |

## Features

- **Interactive tenant card (MCP Apps, SEP-1865)**: `avanan_get_tenant` renders as an
  interactive card in MCP Apps hosts (Claude Desktop/web) showing domain, status,
  deployment mode, license package, protected users, PoC dates, and add-ons. The card is
  read-only, neutral by default, and brandable via `window.__BRAND__` injection or
  `MCP_BRAND_*` env vars (`MCP_BRAND_NAME`, `MCP_BRAND_LOGO_URL`, `MCP_BRAND_PRIMARY_COLOR`,
  `MCP_BRAND_ACCENT_COLOR`, `MCP_BRAND_BG`, `MCP_BRAND_TEXT`). Plain-JSON behavior is
  unchanged in other hosts. Rebuild the embedded card HTML after editing `ui/` with
  `npm run build:ui`.

## Configuration

| Env var | Required | Description |
| --- | --- | --- |
| `AVANAN_APP_ID` | yes | Application ID provided by Avanan Support (`x-av-app-id`). |
| `AVANAN_TOKEN` | yes | Token from the Avanan auth handshake (`x-av-token`). |
| `AVANAN_SECRET` | yes | Shared secret used to compute the `x-av-sig` HMAC. |
| `AVANAN_REGION` | no | `us` \| `eu` \| `ca` \| `ap`. Defaults to JWT region claim, then `us`. |
| `MCP_TRANSPORT` | no | `stdio` (default) or `http`. |
| `MCP_HTTP_PORT` | no | HTTP transport port (default 8080). |
| `LOG_LEVEL` | no | `debug` \| `info` \| `warn` \| `error` (default `info`). |

In **gateway mode**, credentials are taken per-request from headers:
`X-Avanan-App-Id`, `X-Avanan-Token`, `X-Avanan-Secret`, optionally `X-Avanan-Region`.

## Status

> [!IMPORTANT]
> The `x-av-sig` signing algorithm is implemented as a **best-guess HMAC-SHA256**
> because the MSP SmartAPI guide defers signing details to the parent Avanan API
> Reference Guide. Replace the body of `signRequest()` in
> [`src/utils/client.ts`](https://github.com/wyre-technology/avanan-legacy-mcp/blob/HEAD/src/utils/client.ts) with the exact algorithm before
> production use. The function is isolated so no other code needs to change.

## Build

```bash
npm install
npm run build
npm start
```

## Regional endpoints

| Region | Base |
| --- | --- |
| US | `https://smart-api-production-1-us.avanan.net` |
| EU | `https://smart-api-production-1-eu.avanan.net` |
| CA | `https://smart-api-production-1-ca.avanan.net` |
| AP | `https://smart-api-production-5-ap.avanan.net` |

All endpoints sit under `/v1.0/msp/...`.