Vision Helpdesk MCP by usefulapi

它能帮你做什么

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

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 其他

安装

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

你需要

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

你用的是哪个应用？

https://vision-helpdesk.usefulapi.io/mcp

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

{
  "mcpServers": {
    "vision-helpdesk": {
      "url": "https://vision-helpdesk.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "vision-helpdesk": {
      "type": "http",
      "url": "https://vision-helpdesk.usefulapi.io/mcp"
    }
  }
}

https://vision-helpdesk.usefulapi.io/mcp

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

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

它能做什么

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

• vision_get_dashboard_counts

  The ticket counts of the staff dashboard (quick view): for example new, open, overdue and assigned tickets. ticket / quick_view.

• vision_list_tickets

  List tickets, with at most ONE filter: a ticket id, a status id, a department id or a folder (inbox, new, overdue, assigned, trash, spam, draft). Without a filter it lists the tickets the API user can see. Status ids come from vision_list_statuses. ticket / get_tickets.

• vision_search_tickets

  Find tickets by an EXACT ticket reference (the ticket hash such as VHD-218) or an EXACT subject. Give one of them. ticket / get_tickets with a filter on ticket_hash or subject.

• vision_get_ticket

  One ticket with its fields (status, owner, priority, department...) and its posts (the conversation). ticket / ticket_details.

• vision_list_tickets_by_tag

  Tickets that carry a tag, by tag id. ticket / tag_search.

• vision_list_tickets_by_label

  Tickets that carry a label, by label id. ticket / search_label_tickets.

• vision_list_statuses

  The ticket statuses of a department (ids and names), for filters and status changes. ticket / get_status.

• vision_list_priorities

  The ticket priorities of a department (ids and names). ticket / get_priority.

• vision_list_ticket_types

  The ticket types of a department (ids and names). ticket / get_ticket_type.

• vision_list_clients

  List clients (customers), with at most ONE filter: a client id, a first name (exact), or a parent client id (lists that client's contacts). client / get_clients.

• vision_search_clients

  Search clients by name or email text. client / list_clients.

• vision_get_client_summary

  A client's summary: notes and ticket counts. client / get_summary.

• vision_create_ticket

  WRITE: confirm:true required. open a new ticket for a client, given by client id or email. By default no email and no autoresponder is sent; a normal ticket's first post is created on behalf of the client and shown to the client. Internal tickets are staff-only and cannot have cl

• vision_reply_to_ticket

  WRITE: confirm:true required. add a staff reply to a ticket. Say explicitly whether the client can see it (visible_to_client) and whether it is emailed to the client (send_email, default false). ticket / reply_ticket.

• vision_add_ticket_note

  WRITE: confirm:true required. add an internal note to a ticket (not shown to the client). ticket / add_note with notetype 0.

• vision_add_client_note

  WRITE: confirm:true required. add an internal note to a client record. ticket / add_note with notetype 1.

• vision_update_ticket_property

  WRITE: confirm:true required. change one property of a ticket to another id: status, priority, department or type. Look the ids up first (vision_list_statuses and the like). Changing the department can change which statuses and priorities apply. ticket / update_properties.

• vision_assign_ticket_staff

  WRITE: confirm:true required. add a staff member as an owner of a ticket, or remove one. ticket / update_properties with action staff.

• vision_add_ticket_tag

  WRITE: confirm:true required. add a tag (by title) to a ticket. ticket / add_live_tag.

基础检查i

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

• ✓ 通过

  作者与仓库一致

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

• … 尚未检查

  仍在维护

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

• … 尚未检查

  有许可证

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

• ✓ 通过

  端点有响应

  在 56 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

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

与“其他”中的其他服务器比较i

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

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

替代选择

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

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

作者的 README

{