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

Parameter	Type	Default	Description
from	string (ISO)	–	Start of the time range
to	string (ISO)	–	End of the time range
query	string	–	Search in the title
limit	number (max 50)	20	Number of results

CRM

Tool	Role	Parameters
search_crm_contacts	user	query?, limit?=20
get_crm_contact	user	contactId (required)
list_crm_deals	user	query?, limit?=20
list_crm_companies	user	query?, limit?=20

Tickets

Tool	Role	Parameters
list_tickets	user	query?, limit?=20
get_ticket	user	ticketId (required)

Messaging

Tool	Role	Parameters
list_messaging_channels	user	limit?=50
list_messaging_messages	user	limit?=20

More

Tool	Role	Parameters
search_files (Storage)	user	query?, limit?=20
list_external_tasks	user	query?, limit?=20

unified_api_call

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

Parameter	Type	Default	Description
integration_type	string (required)	–	e.g. hubspot, salesforce
category	string (required)	–	crm, ticketing, calendar, messaging, storage, task, …
object_type	string (required)	–	contact, company, deal, ticket, …
method	enum get|post|put|patch|delete	get	HTTP method
path	string	""	Additional path (e.g. /{id})
data	object	–	Body or query parameters

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).

Tool	Role	Purpose
list_connectors	user	List your own connectors with their definitions
test_connector	user	Run a sample payload through, without storing or sending anything
create_connector	admin	Create a connector
update_connector	admin	Replace the definition completely
call_connector_action	user	Run one of the connector's actions

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.

update_connector replaces, it does not merge

Fetch the current state with list_connectors, change it, and send it back in full. Sending only the changed field deletes the rest of the definition.

call_connector_action

Parameter	Type	Description
connector	string (required)	The connector's slug, e.g. statuspage
action	string (required)	The action's key from definition.actions
input	object	Values for the placeholders, matching the action's input_schema
dry_run	boolean	true shows the request without sending it

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