MCP Tools: Integrations ​

These tools appear in tools/list only when a matching integration is connected (get_calendar_events is native and always available).

list_integrations ​

Active integration connections. read · follower

No parameters. Response: { connections[], count } (type, categories, status, connected_at).

get_calendar_events ​

Native Liza calendar events (your own, attendances, accessible calendars). read · user

CRM ​

Tickets ​

Messaging ​

More ​

unified_api_call ​

Generic call to a connected integration (Unified.to) — for categories or object types that no specific tool covers. admin

Your own connectors ​

Five tools for self-built connectors — see Connectors. They require the Pro plan, and the feature must be released for the environment; otherwise they answer with feature_not_released or upgrade_required.

A definition is JSON, not code: field mappings, templates, and request descriptions. Outgoing calls go through a guarded fetch layer (no access to private addresses, size and time limits).

Order ​

The tools are designed for this sequence:

1. list_connectors — is there already one for this service?
2. test_connector with definition and sample_payload — which entry from inbound.events matches, and which block would come out? A definition that passes validation can still point at the wrong fields.
3. create_connector — creates it as a draft. Use activate: true only when explicitly asked: an active connector receives events immediately.

call_connector_action ​

For anything that changes state or costs money, show a dry_run first and have it confirmed.