MCP Server
Last updated 1 day ago
MCP Server
The Liza MCP server (Model Context Protocol) exposes your Liza data as tools for AI clients like Claude Code — via JSON-RPC 2.0 over a single HTTP endpoint.
Endpoint
Base URL: https://api.eu.liza.app
The POST /api/mcp endpoint accepts both single JSON-RPC requests and batch arrays.
Always up to date
The complete, authoritative list of tools is provided live by the server via tools/list. This documentation covers setup and concepts — not every individual signature. Valid field values (status, priority, scope) are provided by the get_metadata tool.
Areas
- Lists — list, read, create, update, delete, statistics.
- Tasks (list items) — filter (
state,compact,assigned_to_me, due date,sort), check off (individually & in bulk), assign, split, attach files, "my open tasks", recently changed, search, item chat. - Users & teams — including workload and invitations.
- Notifications — personal inbox (unread + recently read).
- Scheduled tasks — plan, reschedule, pause and cancel reminders and autonomous AI runs.
- AI memory — store and recall durable facts (personal + team-wide), org overview.
- Assistance tools — search the Liza docs, file support/feedback, render chat widgets (charts, forms, actions).
- Integrations — CRM, calendar, tickets, messaging, storage, tasks (only when connected).
- Providers — GitHub, LiveKit, web search/fetch.
Not every tool is always visible
Two mechanisms determine what tools/list returns:
- Role — every tool requires a minimum role (
owner > admin > user > follower > guest). - Connected integrations — CRM/ticket/messaging tools only appear with a matching connection.
On top of that there are profiles: a client can request a curated, small tool set and load the rest on demand. See Tools & annotations.
Full tool reference
All tools with their parameters: Users · Teams · Lists · List Items · Notifications · Scheduled tasks · AI memory · Assistance · Integrations · Providers.
Next: Connect Claude Code.