# LiveHelpNow MCP connector

The LiveHelpNow connector brings chat analytics, operator stats, surveys, callbacks and attachments into Claude, ChatGPT, Cursor and Microsoft Copilot, so each person works their helpdesk inside their own LiveHelpNow access, with every call logged.

Source: https://elaichi.ai/connectors/livehelpnow/

## Facts

| | |
| --- | --- |
| Application | LiveHelpNow |
| Category | Helpdesk |
| AI tools | 64 |
| Authentication | App credentials |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once LiveHelpNow is connected

- Show yesterday's chat volume by hour for the billing department
- Which operators handled the most chats this week?
- Assign the oldest open callbacks to Maria and add a note

## Connect LiveHelpNow in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick LiveHelpNow.
2. Optionally set Share with, then press Connect.
3. Paste your LiveHelpNow app credentials. LiveHelpNow authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which LiveHelpNow tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## LiveHelpNow MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## LiveHelpNow MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## LiveHelpNow MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## LiveHelpNow MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## LiveHelpNow MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect LiveHelpNow to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a LiveHelpNow tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with LiveHelpNow through Elaichi

### Clear the callback queue before lunch

Support. Ask for the oldest open callbacks in LiveHelpNow, accept them, assign them to whoever is free, and add a comment so the next person knows what was said.

### See who handled what this week

Support leadership. Pull operator activity and stats from LiveHelpNow for the week and spot who is carrying the load, who is idle, and where the chats piled up.

### Staff the desk by the hour

Workforce planning. Read chat stats by hour and daily department statistics from LiveHelpNow, then set shifts around the hours when chats actually arrive.

### Find out why a survey came back low

Customer experience. List the latest chat and ticket surveys in LiveHelpNow, open the ones with poor scores, and read the detail before the weekly review.

### Check where the bot loses people

Marketing. Review LiveHelpNow bot funnels and the contact list to see which step visitors drop at and which conversations turned into a real contact.

### Attach the screenshot to the right case

Support. Upload a customer's screenshot or system log to LiveHelpNow and update an attachment on an existing record without leaving the conversation.

## Elaichi vs Zapier MCP vs Composio for LiveHelpNow

All three can connect LiveHelpNow to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over LiveHelpNow tools | Allow or restrict single LiveHelpNow tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per LiveHelpNow call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect LiveHelpNow to Claude?

Connect LiveHelpNow in Elaichi by entering your LiveHelpNow app credentials; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and LiveHelpNow is ready to use in Claude.

### Does LiveHelpNow work with ChatGPT and Cursor as well as Claude?

Yes. Once LiveHelpNow is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. Connect LiveHelpNow once and every client you use picks it up.

### What can an AI agent actually do with my LiveHelpNow data?

An agent can pull LiveHelpNow chat statistics by hour, by day or by department, read operator activity and stats, open chat and ticket surveys, and review bot funnels and contact lists. It can also look up a callback, accept or assign it, add a comment, and upload or update attachments. Short concrete asks, like 'show yesterday's chat volume by department', work better than long sentences.

### Does connecting LiveHelpNow give the AI access to every department and operator?

No. The agent only sees what the person who signed in can see in LiveHelpNow, because every call runs inside that person's own access. Elaichi can narrow that access further with restrictions, but it never widens it beyond what LiveHelpNow already allows that person.

### Can my team share one LiveHelpNow connection?

Yes. One person connects LiveHelpNow in Elaichi and shares it with the support team, and nobody else ever handles the app credentials. Each teammate still signs in as themselves, so the audit log names the person who assigned a callback or pulled an operator report.

### Can I stop an agent from assigning or changing things in LiveHelpNow?

Yes. In Elaichi you restrict actions one at a time, for a role or for one person, so an agent can read LiveHelpNow surveys and chat stats but not assign callbacks or update attachments. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a LiveHelpNow connection when someone leaves?

Offboarding a person in Elaichi ends their LiveHelpNow access at once, across every client. A shared LiveHelpNow connection keeps working for everyone else on the team. If you disconnect LiveHelpNow in Elaichi, it disappears from Claude, ChatGPT, Cursor and Microsoft Copilot in one step.

### Does the LiveHelpNow MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. LiveHelpNow is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for LiveHelpNow?

Yes. Both let Claude, ChatGPT or Cursor use LiveHelpNow. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every LiveHelpNow call.

### How is Elaichi different from Composio for LiveHelpNow?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to LiveHelpNow: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 64 LiveHelpNow tools

Every tool below is callable through https://api.elaichi.ai/mcp once LiveHelpNow is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all LiveHelpNow analytics bot funnels** (List). List LiveHelpNow chat bot funnel statistics for a date range. Returns: funnel, live_help_bot, path_hash, resulted_in_chat, times_taken. Required: date_from, date_to (both YYYY-MM-DD).
- **List all LiveHelpNow analytics chat info** (List). List LiveHelpNow chat info records for a date range. Returns each chat with chat_session_id, accepted_time, start_time, end_time, chat_tags, operator_email, and visitor_id. Required: date_from, date_to (both YYYY-MM-DD).
- **List all LiveHelpNow analytics chat stats by hour** (List). List LiveHelpNow hourly chat statistics — handled chats, dropped chats and offline requests broken down by hour of the day, one entry per department. Returns: chats_by_hour, dropped_chats_by_hour, offline_requests_by_hour. Required: date_from, date_to.
- **Get single LiveHelpNow analytics chat survey detail by ID** (Get). Get LiveHelpNow chat survey details for a specific survey by id. Returns the survey's question-and-answer pairs: label (the survey question) and answer (the survey answer). Required: id.
- **List all LiveHelpNow analytics chat surveys** (List). List LiveHelpNow chat survey submissions for a given date range. Returns: chat_session_detail_id, notes, submit_date, survey_id, survey_submission_id, visitor_id. Required: date_from, date_to (both in YYYY-MM-DD format).
- **List all LiveHelpNow analytics contact list** (List). List LiveHelpNow chat contact list data for a given date range. Returns: AgentEmail, ChatID, ChatInitiatedBy, ChatLaunchedAt, ChatTime, Country, Custom1, Custom2, Custom3, Department, Detail1, Detail2, Detail3, Detail4, HostName, IPAddress, SurveyComment, SurveyName, SurveyQuestion1, and 9 more. Required: date_from, date_to (YYYY-MM-DD format).
- **List all LiveHelpNow analytics contact nav list** (List). List LiveHelpNow chat contact navigation data showing which pages each contact visited. Returns: AgentEmail, ChatID, Detail1, Detail2, Detail3, Detail4, Page, VisitTime, VisitorID. Required: date_from, date_to (YYYY-MM-DD format).
- **List all LiveHelpNow analytics daily account chat statistics** (List). List daily account-level chat statistics in LiveHelpNow for a date range. Returns: abandoned_chats, auto_invitations_accepted, auto_invitations_shown, average_greet_time, average_wait_time, avg_session_chat_time, chat_sessions, chat_time, chats_handled, date, name, and 12 more. Required: date_from, date_to (both in YYYY-MM-DD format).
- **List all LiveHelpNow analytics daily chatters** (List). List daily chatters data for the LiveHelpNow account, one record per chat visitor for the given day. Returns each chatter's @VisitorID, ChatTime, Country, DepartmentName, HostName, Referrer, visitor custom info, and pre-chat fields. Required: date_from, date_to (YYYY-MM-DD).
- **List all LiveHelpNow analytics daily department chat statistics** (List). List LiveHelpNow daily department chat statistics between date_from and date_to (YYYY-MM-DD format), with one record per department per day. Returns: abandoned_chats, auto_invitations_accepted, avg_chat_time, avg_greet_time, avg_wait_time, chat_sessions, date, department_id, department_name, and 13 more. Required: date_from, date_to.
- **List all LiveHelpNow analytics operator activity** (List). List a LiveHelpNow operator's online and offline activity for a date range. Returns activity entries with action and date. Required: operator_id, date_from, date_to (YYYY-MM-DD format).
- **List all LiveHelpNow analytics operator stats** (List). List daily operator statistics for a LiveHelpNow operator. Returns: date, avg_chat_time_sec, avg_customer_wait_time_sec, avg_response_time_sec, chat_tranfers, chats_missed, proactive_chat_requests, total_chats, total_online_time, utilized_on_chat, and 2 more. Required: operator_id, date_from, date_to (both YYYY-MM-DD).
- **List all LiveHelpNow analytics operators activity** (List). List online and offline activity for LiveHelpNow operators over a date range. Returns each operator's activity entries (action, timestamp), departments, and name, keyed by operator id. Required: date_from, date_to in YYYY-MM-DD format.
- **List all LiveHelpNow analytics operators stats** (List). List daily operator statistics in LiveHelpNow over a date range. Returns an object keyed by operator_id, each entry containing the operator's name and a daily stats array with avg_chat_time_sec, total_chats, total_online_time and utilization. Required: date_from, date_to (YYYY-MM-DD).
- **Get single LiveHelpNow analytics ticket survey detail by ID** (Get). Get the details of a ticket survey in LiveHelpNow by id. Returns the survey questions and answers: label, answer. Required: id.
- **List all LiveHelpNow analytics ticket surveys** (List). List ticket surveys in LiveHelpNow submitted within a given date range. Returns: comment_id, department_id, notes, submit_date, survey_id, survey_submission_id, ticket_id. Required: date_from, date_to (both YYYY-MM-DD).
- **Update a LiveHelpNow attachment by ID** (Update). Update a LiveHelpNow attachment's context assignment, tying the attachment to a chat or ticket. Returns: message, status. Required: id, system, context_id.
- **LiveHelpNow attachments upload context** (Upload). Upload a file to LiveHelpNow and link it to a chat session. Returns the attachment payload: chatMessage, createdTime, fromName, messageId, messageSubType, messageType, operatorId. Required: system, chat_session_id, name, length, data.
- **LiveHelpNow attachments upload system** (Upload). Upload a new file attachment for a LiveHelpNow system (chat, ticket, or callback); the attachment is not assigned to a context. Returns: attachment_id, url. Required: system, name, length, data.
- **LiveHelpNow callbacks accept** (Accept). Accept a pending LiveHelpNow callback on behalf of an operator. Returns: department_id, message. Required: callback_id, operator_id.
- **LiveHelpNow callbacks create comment** (Create). Add a comment to a LiveHelpNow callback. Returns: message, status. Required: callback_id, comment, comment_type (notes_added or closed), operator_id.
- **LiveHelpNow callbacks assign** (Assign). Assign a LiveHelpNow callback to an operator and department. Returns: department_id, message. Required: callback_id, operator_id, department_id.
- **Get single LiveHelpNow callback by ID** (Get). Get a LiveHelpNow callback by id. Returns the callback record with id, title, status, assigned_operator_name, department_name, created_time, actions, fields, notes, and tags. Required: id.
- **LiveHelpNow callbacks list filter options** (List). List the available filter options for LiveHelpNow callback filters. Returns the assigned_to filter field with its selectable options (name, value) and input type.
- **LiveHelpNow callbacks list filters** (List). List LiveHelpNow callback filters for a given operator. Returns: filter_id, filter_name, is_current. Required: operator_id.
- **LiveHelpNow callbacks search** (Search). Search LiveHelpNow callbacks using a generic search term. Returns: id, title, subtitle, status, assigned_operator, assigned_operator_name, country_code, created_by, created_time, department_name, fields, visitor_id. Required: search_term.
- **List all LiveHelpNow callbacks** (List). List LiveHelpNow callbacks for your account. Returns: id, title, subtitle, status, assigned_operator, assigned_operator_name, country_code, created_by, created_time, department_name, fields, visitor_id.
- **Delete a LiveHelpNow callback by ID** (Delete). Delete a LiveHelpNow callback by id. Returns the confirmation message and system status of the deletion. Required: id.
- **LiveHelpNow callbacks reassign** (Action). Reassign a LiveHelpNow callback to an operator. Returns: department_id, message. Required: callback_id, operator_id, department_id.
- **List all LiveHelpNow canned response sets** (List). List available canned response sets in LiveHelpNow. Returns: enabled, id, name, order, parent_id.
- **List all LiveHelpNow canned response items** (List). List canned response items for a given canned set in LiveHelpNow. Returns: enabled, id, message, order, title. Required: canned_set_id.
- **LiveHelpNow chats accept** (Accept). Have an operator accept a chat in LiveHelpNow. Returns: message, status. Required: chat_id.
- **Create a LiveHelpNow chat** (Create). Create a new chat session in LiveHelpNow. Returns the session-start response from LiveHelpNow as an opaque payload; the upstream documentation does not enumerate its fields.
- **LiveHelpNow chats list history** (List). List previous messages for a LiveHelpNow chat session. Returns each message with messageId, message, createdBy, createdTime, messageType, messageSubType, and visitorId. Required: chat_id, limit, ending_message_id.
- **LiveHelpNow chats list messages** (List). List messages for a LiveHelpNow chat session. Returns each message with messageId, message, createdBy, createdTime, and messageType. Required: chat_id.
- **LiveHelpNow chats create message** (Create). Post a new message into a LiveHelpNow chat session. Returns: chatMessage, createdTime, fromName, messageId, messageSubType, messageType, operatorId. Required: chat_id, message.
- **LiveHelpNow chats proactive invite** (Invite). Send a visitor a proactive chat invitation in LiveHelpNow. Returns the sent invite details: chatMessage, createdTime, fromName, messageId, messageSubType, messageType, operatorId. Required: message, visitor_id.
- **LiveHelpNow chats reassign** (Action). Reassign a LiveHelpNow chat to a different department or operator by chat id. Returns: message, status. Required: chat_id, department_id.
- **LiveHelpNow chats set typing status** (Set). Set the typing status for the operator or visitor in a LiveHelpNow chat session by chat id. Returns the typing status payload and the system response status. Required: chat_id, status.
- **LiveHelpNow chats terminate** (Action). Terminate a LiveHelpNow chat session by chat id. Returns: message, status. Required: chat_id.
- **List all LiveHelpNow client status** (List). Get the online status of your LiveHelpNow account. Returns: status.
- **List all LiveHelpNow departments** (List). List departments for your LiveHelpNow account. Returns: department_id, department_name, department_description, department_email, operators, hours.
- **Get single LiveHelpNow department by ID** (Get). Get the online status for a specific LiveHelpNow department by id. Returns the department's current status, which will be online or offline. Required: id.
- **LiveHelpNow tickets accept** (Accept). Accept a LiveHelpNow ticket by id, claiming it for handling. Returns the accept data: department_id, message. Required: ticket_id.
- **LiveHelpNow tickets acknowledge** (Action). Acknowledge a LiveHelpNow ticket by id. Returns: message, status. Required: ticket_id.
- **LiveHelpNow tickets assign** (Assign). Assign a LiveHelpNow ticket to a department, optionally to a specific operator. Returns: message, status. Required: ticket_id, department_id.
- **Delete a LiveHelpNow ticket by ID** (Delete). Delete a LiveHelpNow ticket by id. Returns: message, status. Required: id.
- **LiveHelpNow tickets reassign** (Action). Reassign a LiveHelpNow ticket to a different department, optionally to a specific operator. Returns: message, status. Required: ticket_id, department_id.
- **LiveHelpNow tickets resolve** (Action). Resolve a LiveHelpNow ticket by providing the solution. Returns: message, status. Required: ticket_id, solution, comment_type (must be "resolved").
- **Get single LiveHelpNow ticket by ID** (Get). Get a single LiveHelpNow ticket by id. Optional flags include_comments, include_actions, include_tags and visible_only add comments, actions and tags or exclude private tickets. Returns the full ticket record including id, title, status, priority, category, submitter name and email, tags, and created/updated times. Required: id.
- ...and 14 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
