Vision Helpdesk MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

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

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

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

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 56 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 19 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32417 servers in this category
• Published to the registry more recently than 97% of the other 32417 servers in this category
• Basic checks equal to or better than 100% of the other 32417 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{