Helpwise MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 聊天与邮件

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://helpwise.usefulapi.io/mcp

claude mcp add --transport http helpwise https://helpwise.usefulapi.io/mcp

{
  "mcpServers": {
    "helpwise": {
      "url": "https://helpwise.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "helpwise": {
      "type": "http",
      "url": "https://helpwise.usefulapi.io/mcp"
    }
  }
}

https://helpwise.usefulapi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• helpwise_list_conversations

  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 /conversation

• helpwise_get_conversation

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

• helpwise_list_contacts

  List contacts (name, company, job title, emails, phones, id). Page with limit and offset. GET /contacts.

• helpwise_search_contacts

  Search contacts by a name, email or phone term. Page with limit and offset. GET /contacts/search.

• helpwise_get_contact

  One contact with emails, phones, company, custom fields and recent conversations. GET /contacts/{id}.

• helpwise_list_tags

  All tags (id, name, colour, parent, inbox). Use the ids with helpwise_apply_tags. GET /tags.

• helpwise_get_tag

  One tag by id. GET /tags/{id}.

• helpwise_get_report

  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

• helpwise_get_tags_report

  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.

• helpwise_list_inboxes

  List the account's inboxes (mailboxes) with id, name, address and type. Use the ids in the other tools. POST /mailboxes/list (V0).

• helpwise_list_users

  List the team members (agents) with access to an inbox: id, name, email. Use the ids with helpwise_assign_conversation. POST /users/list (V0).

• helpwise_get_current_user

  The Helpwise user the API key belongs to (name, email, id). POST /users/me (V0).

• helpwise_create_contact

  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.

• helpwise_update_contact

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

• helpwise_add_note

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

• helpwise_assign_conversation

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

• helpwise_close_conversations

  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.

• helpwise_reopen_conversations

  WRITE: move up to 25 conversations back to the inbox (reopen closed ones). Nothing is sent to customers. PUT /conversations/action/moveToInbox.

• helpwise_apply_tags

  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.

• helpwise_remove_tags

  WRITE: take tags off up to 25 conversations. The tags themselves are not deleted. POST /tags/remove.

• helpwise_send_email

  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

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 18 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 21 个工具描述，未发现针对 AI 的隐藏指令

与“聊天与邮件”中的其他服务器比较i

• 星标数多于此分类中其他 1762 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1762 个服务器的 96% 更新
• 基础检查结果等于或优于此分类中其他 1762 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{