WACM Connect MCP Server

A Model Context Protocol (MCP) server for the Wasabi WACM Connect API. Provides 18 read-only tools out of the box, with 12 opt-in write tools behind tiered access controls. Designed for Managed Service Providers (MSPs) who need to manage their Wasabi account hierarchy, storage usage, and billing data through Claude.

[!WARNING] This MCP server has write access to your Wasabi account management infrastructure.

>

This tool can create, modify, and delete sub-accounts, members, channel accounts, and other resources in your live WACM environment. Actions taken through this MCP are real and may be irreversible.

Disclaimer

This is an independent, community-maintained project. It is not affiliated with, endorsed by, or supported by Wasabi Technologies. "Wasabi" and "WACM" are trademarks of Wasabi Technologies, Inc. Wasabi Technologies is not responsible for unintended changes made through this integration.

AI-Specific Risks

This server is designed to be operated by an AI assistant (LLM). AI models can and do make mistakes — they may misinterpret instructions, hallucinate parameter values, or take actions you did not intend. In the context of account management, this means an AI could accidentally:

• Create unwanted accounts with incorrect configurations or storage quotas
• Modify existing accounts by changing settings, roles, or permissions you didn't ask to change
• Delete accounts, members, or channel accounts that were not meant to be removed
• Perform bulk operations across multiple resources when you intended a single change
• Act on the wrong resource by confusing similarly named accounts or IDs

These are real API calls against your real Wasabi infrastructure unless you are using a dedicated test account. There is no sandbox, staging layer, or undo button between the AI and your environment.

Before Use

• Understand your API credentials — the API key's permission scope determines what the AI can reach
• Test in a non-production environment if possible before enabling write access on production accounts
• Start read-only — write tools are disabled by default; only enable the minimum tier you need
• Use dry-run mode — every write tool supports dryRun: true to preview the exact HTTP request before execution
• Review all AI-suggested actions before confirming, especially bulk operations or deletions
• Prefer the operation allowlist over broad tier access to limit exposure to only the tools you actually need

Liability

Use at your own risk. The authors assume no liability for data loss, service disruption, unintended account modifications, or other damages resulting from use of this software — whether caused by AI error, misconfiguration, or any other reason. See the Apache 2.0 license for full terms.

Prerequisites

• Node.js 24+ (uses native fetch)
• WACM Connect API credentials — generate an API key in WACM under My Profile > WACM Connect (Wasabi docs)

Installation

git clone https://github.com/myst3k/wasabi-wacm-connect-mcp.git
cd wasabi-wacm-connect-mcp
pnpm install
pnpm build

Configuration

Claude Code (.mcp.json)

Read-only (default):

{
  "mcpServers": {
    "wasabi-wacm-connect-mcp": {
      "command": "node",
      "args": ["/path/to/wasabi-wacm-connect-mcp/dist/index.js"],
      "env": {
        "WACM_USERNAME": "your-username",
        "WACM_API_KEY": "your-api-key"
      }
    }
  }
}

With write access (create + update):

{
  "mcpServers": {
    "wasabi-wacm-connect-mcp": {
      "command": "node",
      "args": ["/path/to/wasabi-wacm-connect-mcp/dist/index.js"],
      "env": {
        "WACM_USERNAME": "your-username",
        "WACM_API_KEY": "your-api-key",
        "WACM_WRITE_ACCESS": "true",
        "WACM_WRITE_LEVEL": "manage"
      }
    }
  }
}

With specific write operations only:

{
  "mcpServers": {
    "wasabi-wacm-connect-mcp": {
      "command": "node",
      "args": ["/path/to/wasabi-wacm-connect-mcp/dist/index.js"],
      "env": {
        "WACM_USERNAME": "your-username",
        "WACM_API_KEY": "your-api-key",
        "WACM_WRITE_ACCESS": "true",
        "WACM_WRITE_ALLOWED_OPERATIONS": "create_sub_account,delete_member"
      }
    }
  }
}

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "wasabi-wacm-connect-mcp": {
      "command": "node",
      "args": ["/path/to/wasabi-wacm-connect-mcp/dist/index.js"],
      "env": {
        "WACM_USERNAME": "your-username",
        "WACM_API_KEY": "your-api-key",
        "WACM_WRITE_ACCESS": "true",
        "WACM_WRITE_LEVEL": "full"
      }
    }
  }
}

Environment Variables

CLI flags --username and --api-key override environment variables.

Write Access Tiers

Write operations are disabled by default. To enable them, you must set WACM_WRITE_ACCESS=true and at least one of WACM_WRITE_LEVEL or WACM_WRITE_ALLOWED_OPERATIONS. The kill switch (WACM_WRITE_ACCESS) must be explicitly set — without it, no write tools are registered regardless of other settings.

When both env vars are set, the resolved operations are the union of both:

• WACM_WRITE_LEVEL=manage + WACM_WRITE_ALLOWED_OPERATIONS=delete_member → 9 write tools
• WACM_WRITE_ALLOWED_OPERATIONS=create_sub_account,delete_member (no level) → just those 2

Unknown level values or operation names are logged as warnings and ignored.

Valid Operation Names

create_sub_account, update_sub_account, delete_sub_account, create_member, update_member, delete_member, create_channel_account, update_channel_account, delete_channel_account, create_channel_account_user, delete_channel_account_user, create_standalone_account

Available Tools (up to 30)

Control Accounts (read-only)

Sub-Accounts

Channel Accounts

Channel Account Users

Members

Invoices (read-only)

Usages (read-only)

Standalone Accounts

Guardrails

Write operations are protected by multiple safety layers:

1. Kill switch — WACM_WRITE_ACCESS=true must be explicitly set to enable any write operations. Without this, all other write settings are ignored and the server is strictly read-only.

1. Tiered access control — WACM_WRITE_LEVEL controls which categories of write tools are registered. Unregistered tools are completely invisible to the LLM.

1. Operation allowlist — WACM_WRITE_ALLOWED_OPERATIONS provides fine-grained control over exactly which write tools are available, independent of or combined with tier levels.

1. MCP tool annotations — Each write tool carries metadata hints for the LLM:

• Create (POST): readOnlyHint: false
• Update (PUT): readOnlyHint: false, idempotentHint: true
• Delete (DELETE): readOnlyHint: false, destructiveHint: true

1. Dry-run mode — Every write tool accepts a dryRun boolean parameter (default: false). When true, the tool returns a preview of the HTTP request (method, URL, headers, body) without executing it. Auth credentials are redacted in the preview.

Available Resources (4)

Available Prompts (5)

Example Conversations

Check Storage Across All Accounts

"Show me a summary of storage usage across all my control accounts"

Claude will use the storage-summary prompt to call list_control_accounts and list_sub_accounts, then present a table comparing active storage against quotas.

Investigate Monthly Costs

"What were my top costs last month? Break it down by sub-account."

Claude will call list_invoices with the previous month's date range, group by sub-account, and identify the highest-cost accounts and categories.

Security Audit

"Audit my account hierarchy for any security concerns"

Claude will use the account-audit prompt to enumerate all accounts and members, checking for missing MFA, deactivated accounts, and misconfigured quotas.

Create a Sub-Account with Dry Run

"Create a new sub-account called 'Acme Corp' under control account 5 — but show me the request first"

Claude will call create_sub_account with dryRun: true and show the full HTTP request preview. After you confirm, it will execute the actual request.

Troubleshooting

Authentication Errors

• Verify your credentials: curl -u "$WACM_USERNAME:$WACM_API_KEY" https://api.wacm.wasabisys.com/api/v1/control-accounts
• API keys are shown only once at generation time — regenerate if lost
• Check that you're using the correct key type (Account API Key vs Personal API Key)

Rate Limiting

• The API allows 5 GET requests per second per API key
• The client automatically retries once on HTTP 429 responses
• For bulk operations, expect automatic throttling by the built-in rate limiter

Missing Data

• Check your user permissions — visibility depends on your tier in the account hierarchy
• Governance users see all accounts; Control Account users see only their own
• Use includeDeleted: true to see deleted sub-accounts

Write Tools Not Appearing

• Verify WACM_WRITE_LEVEL or WACM_WRITE_ALLOWED_OPERATIONS is set in your MCP config
• Check stderr for warning messages about unknown level values or operation names
• Restart the MCP server after changing environment variables

Security

• Credentials are stored in memory only — never written to disk or logs
• Sensitive fields hidden by default — includeKeys and includeApiKey default to false
• Write tools are opt-in — no write operations are available unless explicitly enabled via env vars
• Dry-run previews redact credentials — buildRequestPreview replaces the auth header with Basic [REDACTED]
• CLI arg visibility — --api-key via CLI is visible in ps output; prefer environment variables for production
• Cloud LLM considerations — data retrieved through this server may be processed by cloud AI services; review your organization's data handling policies
• Key rotation — regenerate API keys periodically in WACM under My Profile > WACM Connect

Development

pnpm install
pnpm dev             # Run with tsx (auto-reload)
pnpm build           # Compile TypeScript
pnpm test            # Run tests
pnpm lint            # Lint code
pnpm format          # Format code
pnpm check           # Type-check without emitting

License

Apache-2.0