Integration

Collabin integration

Collabin is a leave management (HR) platform. Through its REST API an agent can list and look up the organization's users, teams and leave types, read leave requests (filter by employee, date range, status or last update for incremental syncs), read the calendar for a date range, create a leave request and approve or reject a pending one; each write says through notify whether Collabin notifies the people involved. Users, teams, leave requests and the calendar are personal data, and leave can include sick leave. Webhook subscriptions are managed in the Collabin dashboard and are not exposed. Authentication is an API key (clb_...) created by an administrator in Settings, API Keys, sent in the X-API-Key header; the external API needs the Pro plan, writes need a Read and Write key, and requests are limited to 120 per minute.

Connect Collabin How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Collabin.Built from the 11 Collabin tools below, on the connection you add once.

What you can do with Collabin

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Leave, 4 operations

create_leaveCreate leavePOSTAgents: ask firstCreates a leave request for an employee in PENDING status; with notify true Collabin notifies the approvers (in-app, and by email if they opted in). 422 QUOTA_EXCEEDED when a blocking quota would be exceeded. Needs a Read and Write key.
get_leaveGet leaveGETAgents: ask firstReturns one leave request by numeric id with its employee, leave type, dates, half-day flag and status (such as PENDING, APPROVED or REJECTED). Returns personal data.
list_leavesList leavesGETAgents: ask firstLists leave requests, page by page, filtered by employee, overlapping date range, status or last update time (updated_since, for incremental syncs). Returns personal data (absences, which can include sick leave).
list_user_leavesList user leavesGETAgents: ask firstLists the leave requests of one employee, page by page, optionally only those with a given status. Returns personal data (absences, which can include sick leave).

Team, 2 operations

get_teamGet teamGETAgents: ask firstReturns one team by numeric id (from list_teams), including its leaders and members. Returns personal data (the people in the team).
list_teamsList teamsGETAgents: ask firstLists the teams of the organization, page by page. Each team is returned whole, as Collabin sends it, with its leaders and members (the vendor does not document the field names). Returns personal data (the people in each team).

User, 2 operations

get_userGet userGETAgents: ask firstReturns one user of the organization by numeric id (from list_users). Returns personal data (name and email).
list_usersList usersGETAgents: ask firstLists the users of the organization the API key belongs to (id, name, email), page by page; filter by a partial name or email. Returns personal data.

Calendar, 1 operation

get_calendarGet calendarGETAgents: ask firstReturns Collabin's calendar for a date range of at most 366 days, which the vendor describes as the workday and holiday calendar with the approved leaves. Returns personal data (who is absent when).

Leave type, 1 operation

list_leave_typesList leave typesGETAgents: ask firstLists the organization's leave types (such as Vacation or Home office) with their quota rules (period, default quota, blocking, deducting types) and minimum notice. Use an id as leave_type_id in create_leave.

Status, 1 operation

update_leave_statusUpdate leave statusPUTAgents: ask firstApproves or rejects a PENDING leave request (409 if it is not pending); with notify true Collabin tells the employee (in-app, and by email if they opted in; the email names your API key). Needs a Read and Write key.

Use Collabin from Claude Code, Cursor or Codex

Connect Collabin in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Collabin operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Collabin

Create your workspace
Sign up free. Nothing to install.
Connect Collabin once
Add your Collabin connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.