MCP server for interacting with your LINE Official Account
Nothing to run from here
Helpwise MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
21
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read Helpwise conversations, contacts, tags and reports; note, tag, assign, close; send one email.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http helpwise-mcp-by-usefulapi https://helpwise.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# helpwise_list_conversations, helpwise_get_conversation, helpwise_list_contacts and 18 more
Helpwise MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http helpwise-mcp-by-usefulapi https://helpwise.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List conversations (threads) of one or more inboxes, newest first, with subject, snippet, tags, assignee, read/starred/closed flags and contact. Pick the folder with folder (default: all). Page with next_page_token. Inbox ids come from helpwise_list_inboxes. GET /conversations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| inbox_ids | array | yes | Inbox (mailbox) ids to list (1-20). |
| folder | string | no | Folder: all, assigned, unassigned, starred, snoozed, draft, sent, closed, spam, trash, scheduled. |
| limit | integer | no | Results per page, 1-100 (default 25). |
| page_token | string | no | The previous reply's next_page_token. |
One conversation with its messages, notes, drafts, assignment and contacts. Page long conversations with page_token from the previous reply. GET /inboxes/{inbox_id}/conversations/{conversation_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| inbox_id | integer | yes | Inbox (mailbox) id the conversation lives in. |
| conversation_id | integer | yes | Conversation (thread) id. |
| folder | string | no | Folder context (optional). |
| limit | integer | no | Results per page, 1-100 (default 25). |
| page_token | string | no | Page token from the previous reply, for older messages. |
List contacts (name, company, job title, emails, phones, id). Page with limit and offset. GET /contacts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Results per page, 1-100 (default 25). |
| offset | integer | no | How many results to skip (default 0). Pass the previous reply's next_offset. |
Search contacts by a name, email or phone term. Page with limit and offset. GET /contacts/search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| term | string | yes | Search term (name, email or phone). |
| limit | integer | no | Results per page, 1-100 (default 25). |
| offset | integer | no | How many results to skip (default 0). Pass the previous reply's next_offset. |
One contact with emails, phones, company, custom fields and recent conversations. GET /contacts/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | integer | yes | Helpwise contact id. |
All tags (id, name, colour, parent, inbox). Use the ids with helpwise_apply_tags. GET /tags.
No parameter schema on file.
One tag by id. GET /tags/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tag_id | integer | yes | Helpwise tag id. |
Overall and team-performance report for a date range: new/closed/assigned conversations (with change vs the previous period), inbound/outbound messages per day, busiest hour/day, average first response, response and resolution time, CSAT and per-agent performance. Optional inbox and tag filters. GET /reports.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | yes | Start, yyyy-mm-dd or yyyy-mm-dd hh:mm:ss (a date alone means 00:00:00). |
| end | string | yes | End, yyyy-mm-dd or yyyy-mm-dd hh:mm:ss (a date alone means 23:59:59). |
| business_hours_only | boolean | no | Count business hours only (default false). |
| inbox_id | integer | no | Only this inbox (default: all inboxes). |
| tag_ids | array | no | Only conversations with these tag ids. |
Per-tag report for one inbox and a date range: conversations per tag (and share), open conversations, average response, first-response and resolution time. GET /inboxes/{inbox_id}/reports/tags.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| inbox_id | integer | yes | Inbox (mailbox) id. |
| start | string | yes | Start, yyyy-mm-dd or yyyy-mm-dd hh:mm:ss (a date alone means 00:00:00). |
| end | string | yes | End, yyyy-mm-dd or yyyy-mm-dd hh:mm:ss (a date alone means 23:59:59). |
| business_hours_only | boolean | no | Count business hours only (default false). |
| tag_ids | array | no | Only these tag ids. |
List the account's inboxes (mailboxes) with id, name, address and type. Use the ids in the other tools. POST /mailboxes/list (V0).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1). |
| limit | integer | no | Results per page, 1-100 (default 25). |
List the team members (agents) with access to an inbox: id, name, email. Use the ids with helpwise_assign_conversation. POST /users/list (V0).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| inbox_id | integer | yes | Inbox (mailbox) id. |
The Helpwise user the API key belongs to (name, email, id). POST /users/me (V0).
No parameter schema on file.
WRITE: create a new contact in Helpwise (name, company, job title, emails, phones, custom fields). Nothing is sent to the person. Creating the same email twice may create a duplicate. POST /contacts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| firstname | string | yes | First name. |
| lastname | string | no | Last name. |
| company | string | no | Company name. |
| job_title | string | no | Job title. |
| emails | array | no | Email addresses (1-10). |
| phones | array | no | Phone numbers (up to 10). |
| custom_fields | array | no | Custom field values. |
WRITE: change a contact's name, company, job title, emails, phones or custom fields. Helpwise updates with PUT, so this tool first reads the contact and sends the current values together with your changes; a list you pass (emails, phones, custom_fields) REPLACES the old list. Nothing is sent to the person. PUT /contacts/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | integer | yes | Helpwise contact id. |
| firstname | string | no | New first name. |
| lastname | string | no | New last name. |
| company | string | no | New company. |
| job_title | string | no | New job title. |
| emails | array | no | The full list of email addresses (replaces the current list). |
| phones | array | no | The full list of phone numbers (replaces the current list). |
| custom_fields | array | no | Custom field values to set (replaces the current list). |
WRITE: add an internal note to a conversation. Visible to your Helpwise team only; it is not sent to the customer. Notes cannot be deleted through this API. POST /notes/add (V0).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| inbox_id | integer | yes | Inbox (mailbox) id of the conversation. |
| conversation_id | integer | yes | Conversation (thread) id. |
| message | string | yes | The note text. |
WRITE: assign a conversation to a team member (user id from helpwise_list_users), or pass assigned_to 0 to unassign it. The assignee may be notified by Helpwise. POST /threads/assign (V0).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| inbox_id | integer | yes | Inbox (mailbox) id of the conversation. |
| conversation_id | integer | yes | Conversation (thread) id. |
| assigned_to | integer | yes | User id to assign to, or 0 to unassign. |
WRITE: close up to 25 conversations (mark them done). They can be reopened with helpwise_reopen_conversations. Nothing is sent to customers. PUT /conversations/action/close.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversation_ids | array | yes | Conversation (thread) ids to close (1-25). |
WRITE: move up to 25 conversations back to the inbox (reopen closed ones). Nothing is sent to customers. PUT /conversations/action/moveToInbox.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversation_ids | array | yes | Conversation (thread) ids to reopen (1-25). |
WRITE: apply existing tags (ids from helpwise_list_tags) to up to 25 conversations. Tags can drive Helpwise automations. Applying a tag already present changes nothing. POST /tags/apply.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversation_ids | array | yes | Conversation (thread) ids (1-25). |
| tag_ids | array | yes | Tag ids to apply (1-10). |
WRITE: take tags off up to 25 conversations. The tags themselves are not deleted. POST /tags/remove.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversation_ids | array | yes | Conversation (thread) ids (1-25). |
| tag_ids | array | yes | Tag ids to remove from them (1-10). |
WRITE: SEND A REAL EMAIL from a Helpwise inbox to the given customer address(es). Irreversible; once sent it cannot be recalled. At most 10 recipients in total (to + cc), one message per call; never use it for lists or campaigns. This starts a new message (it is not a reply on an existing conversation). The body is plain text (blank line = new paragraph); it is sent as HTML. POST /emails/send_mail
| Parameter | Type | Required | Notes |
|---|---|---|---|
| inbox_id | integer | yes | Inbox (mailbox) id to send from (see helpwise_list_inboxes). |
| to | array | yes | Recipient addresses (1-10 with cc together). |
| cc | array | no | Cc addresses. |
| subject | string | yes | Subject line. |
| body | string | yes | Plain-text message body. |
| reply_to | string | no | Reply-to address (optional). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Helpwise MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Helpwise MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.