Authentication
All requests authenticate via a Bearer token in the Authorization header.
Authorization: Bearer liza_mcp_…Which data and tools are visible depends on your role (owner > admin > user > follower > guest) and your connected integrations (for example, CRM tools only appear when a CRM integration is connected).
TIP
You create the token in the Liza settings. Treat it like a password — it carries your permissions.
Role of a token
A token works with its owner's role in the organization — but at most with user. Admins and owners do not get admin rights through a token; followers stay followers.
- Guests of an organization get no token: a token whose owner is a guest there is rejected with
401. - If the owner is no longer active in the organization, the token stops working as well.
As a result, the following are not reachable with a token:
| Area | What |
|---|---|
MCP tools with minimum role admin | delete_list, delete_list_item, create_team, add_team_member, remove_team_member, unified_api_call, create_connector, update_connector, list_connectors, test_connector, github_merge_pull_request — they are missing from tools/list, and a direct call fails with "Insufficient permissions" |
| REST | POST /v1/users, PATCH /v1/users/{userId}, DELETE /v1/users/{userId} — response 403 (see Users) |
Admins do these tasks in the Liza app.
Auth cache
Tokens are cached briefly on the server side. Deleting, deactivating or reissuing a token in the settings clears that cache automatically, so a revoked token stops working immediately rather than when the cache expires.
If a token was changed directly in the database, you can clear the entry manually. The endpoint is authenticated and only clears the cache entry of the token you send:
curl -X POST https://api.eu.liza.app/api/mcp/clear-cache \
-H "Authorization: Bearer YOUR_TOKEN"