Integration

Leexi integration

Leexi is an AI notetaker and conversation intelligence platform for sales and support teams. Read calls and meetings with their transcript, summary, chapters, tasks and topics, read and translate call notes, schedule meeting events and send the meeting assistant to join them, and manage the workspace's users and teams. Reseller accounts can also manage client companies, their subscriptions, teams and users, but only with a dedicated reseller key (it holds only read_clients and write_clients and cannot call the other routes, and a regular key cannot call the reseller ones), so connect it as a separate credential. Creating a call from a recording is not exposed: it needs an upload to a presigned storage URL this integration cannot send. Authentication is HTTP basic auth with the API key ID as username and the key secret as password; each route needs a matching permission scope on the key (read_calls, write_users and so on).

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Leexi

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.

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

Team, 10 operations

  • create_client_teamCreate client teamPOSTCreates a team in a client company; the name must be unique there. Reseller accounts only; needs the write_clients scope.
  • create_teamCreate teamPOSTCreates a team in your workspace; the name must be unique there. The team inherits your company settings. Needs the write_teams scope.
  • delete_client_teamDelete client teamDELETEDeletes a client team that has no users and no calls (otherwise 422: deactivate it with update_client_team). Reseller accounts only; needs the write_clients scope.
  • delete_teamDelete teamDELETEDeletes a team that has no users and no calls (otherwise 422: deactivate it with update_team instead). Needs the write_teams scope.
  • get_client_teamGet client teamGETReturns one team of a client company. Reseller accounts only; needs the read_clients scope.
  • get_teamGet teamGETReturns one team of your workspace by uuid (from list_teams). Needs the read_teams scope.
  • list_client_teamsList client teamsGETLists the teams of one client company. Reseller accounts only; needs the read_clients scope.
  • list_teamsList teamsGETLists the teams of your workspace, page by page. Needs the read_teams scope.
  • update_client_teamUpdate client teamPATCHRenames a client team or (de)activates it; only the fields you send change. Deactivation needs the team to have no active users. Reseller accounts only; needs the write_clients scope.
  • update_teamUpdate teamPATCHRenames a team or (de)activates it; only the fields you send change. A team can be deactivated only once it has no active users. Needs the write_teams scope.

User, 10 operations

  • create_client_userCreate client userPOSTCreates a user in a team of a client company; any role may be assigned. Set send_welcome_email to choose whether Leexi emails them. Reseller accounts only; needs the write_clients scope.
  • create_userCreate userPOSTCreates a user in a team of your workspace; set send_welcome_email to choose whether Leexi emails them. Privileged roles cannot be granted through the API. Needs the write_users scope.
  • deactivate_client_userDeactivate client userDELETEDeactivates a client user (never deleted): history kept, sessions revoked, license freed. Reactivate with update_client_user. Reseller accounts only; needs the write_clients scope.
  • deactivate_userDeactivate userDELETEDeactivates a user (never deleted): their calls and history are kept, sessions revoked, license freed. Reactivate with update_user (active true). Needs the write_users scope.
  • get_client_userGet client userGETReturns one user of a client company. Reseller accounts only; needs the read_clients scope.
  • get_userGet userGETReturns one user of your workspace by uuid (from list_users). Needs the read_users scope.
  • list_client_usersList client usersGETLists the users of one client company. Reseller accounts only; needs the read_clients scope.
  • list_usersList usersGETLists the users of your workspace (uuid, name, email, team, roles, license, active), page by page. Needs the read_users scope.
  • update_client_userUpdate client userPATCHChanges only the fields you send on a client user; sending roles replaces all of them, active true reactivates. Reseller accounts only; needs the write_clients scope.
  • update_userUpdate userPATCHChanges only the fields you send on a user of your workspace (name, email, team, roles, license, active). Sending roles replaces all of them; active true reactivates. Needs the write_users scope.

Call note, 4 operations

  • delete_call_noteDelete call noteDELETEDeletes a call note. Needs the write_calls scope.
  • get_call_noteGet call noteGETReturns one call note with its prompt and translations. Needs the read_calls scope.
  • list_call_notesList call notesGETLists the notes Leexi wrote for one call (call_uuid, from list_calls), optionally for one prompt only. Needs the read_calls scope.
  • update_call_note_translationUpdate call note translationPATCHReplaces the translated text of a call note for one locale; the source note text is not changed. Needs the write_calls scope.

Company, 4 operations

  • create_client_companyCreate client companyPOSTCreates a client company on a Leexi trial until trial_end (a past date creates it with the trial ended). name, trial_end and company_setting.license_category are required. Reseller accounts only; needs the write_clients scope.
  • deactivate_client_companyDeactivate client companyDELETEDeactivates a client company: cancels its subscription and deactivates every user. Reactivating later restores neither. Reseller accounts only; needs the write_clients scope.
  • list_client_companiesList client companiesGETLists your client companies with their subscription state (active, status, trial_end, billed seats); filter by reseller_external_id. Reseller accounts only; needs the read_clients scope.
  • update_client_companyUpdate client companyPATCHChanges only the fields you send on a client company (plan, trial_end, name, settings). A future trial_end restarts the trial; active false deactivates it. Reseller accounts only; needs the write_clients scope.

Meeting event, 4 operations

  • create_meeting_eventCreate meeting eventPOSTCreates a meeting event for a Leexi user from a Zoom, Teams or Google Meet link. owned, internal and to_record must be sent explicitly. Needs the write_meeting_events scope.
  • delete_meeting_eventDelete meeting eventDELETEDeletes a meeting event. Needs the write_meeting_events scope.
  • get_meeting_eventGet meeting eventGETReturns one meeting event with its meeting assistant runs and the calls recorded from it. Needs the read_meeting_events scope.
  • list_meeting_eventsList meeting eventsGETLists meeting events (calendar, manual or API), filterable by origin and a start or end time window. Needs the read_meeting_events scope.

Call, 2 operations

  • get_callGet callGETReturns one call or meeting with everything list_calls gives plus topics and the transcript (simple_transcript by paragraph, transcript by word). 404 outside the key's access. Needs the read_calls scope.
  • list_callsList callsGETLists calls and meetings the key can access (summary, participants, owner, tags), filterable by date, source, owner or customer. Use get_call for the transcript. Needs the read_calls scope.

Subscription, 2 operations

  • cancel_client_subscriptionCancel client subscriptionDELETEEnds a client's Leexi trial now, or cancels its open paid subscription with proration (independent resellers). Does not deactivate the company or its users. Reseller accounts only; needs the write_clients scope.
  • start_client_subscriptionStart client subscriptionPOSTEnds a client's trial and starts its paid Stripe subscription on the plan currently set on the company (independent resellers only; 409 if one is open). Reseller accounts only; needs the write_clients scope.

Launch bot, 1 operation

  • launch_meeting_assistantLaunch meeting assistantPOSTLaunches Leexi's meeting assistant (its recording bot) on a meeting event, or stops the running one with stop_task true. Needs the write_meeting_events scope.

Use Leexi from Claude Code, Cursor or Codex

Connect Leexi in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Leexi 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 Leexi

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Leexi once

    Add your Leexi connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

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

Leexi integration FAQ

What can you do with the Leexi integration?

LiveContext exposes 37 operations on Leexi, covering team, user, call note and company.

Popular integrations

Browse the whole catalog