Avoma Admin

Avoma Admin lists organization members (email, status, and role) through Avoma's public API (GET /v1/users/).

The public API cannot deactivate or remove a member. Admins deactivate people in Settings → Members. This connector is read-only on purpose.

This is a dedicated built-in connector. It is not the registry HTTP MCP at mcp.avoma.com.

Authentication Types

Avoma Admin supports 1 authentication method:

• API key — sent as Authorization: Bearer. Created by an Admin under Settings → Organization → Developer.
  • Pros: Matches the public API
  • Cons: Select plans only; 60 requests per minute; user-scoped keys do not return the full org directory

Setting up an API key

1. Confirm the plan includes API access and that you are an Admin.
2. In Avoma go to Settings → Organization → Developer.
3. Click Add API Key, name it, and choose a Scope. For a full member list use Organization – limited access. User-scoped keys only return that one person's data.
4. Copy the full key string (CLIENT_KEY:CLIENT_SECRET) into Willow.

See Avoma's scoped API keys and API reference.

Available Tools

• List Users — GET /v1/users/. Returns uuid, email, status / active, role, admin flag, and teams.
• Get User — GET /v1/users/{uuid}/. Id comes from List Users.

There is no deactivate tool. Use Settings → Members → Actions → Deactivate in Avoma to free a license.

Troubleshooting

401 or key rejected

Cause: The secret is incomplete, revoked, or the user on a user-scoped key was deactivated.

Solution: Create a new key under Settings → Organization → Developer. Paste the full CLIENT_KEY:CLIENT_SECRET string.

Directory looks incomplete

Cause: The key is User – limited or User – full and only sees that one person.

Solution: Create an Organization – limited access key if you need the org directory.

Cannot deactivate from Willow

Cause: Avoma does not document a public deactivate or remove-member API.

Solution: Deactivate the member in the Avoma UI.