Manage helpdesk tickets, search clients, and handle support conversations from your helpdesk system.
Connects to Vision Helpdesk to let support staff triage tickets, read conversations, search clients, assign work, add notes, and manage ticket status and priority. Requires Vision Helpdesk account and API access.
Try asking Muse: "Show me all open tickets in the sales department and assign the highest priority one to me."
Source: Found in the official MCP Registry (io.usefulapi/vision-helpdesk) · First listed October 30, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 2 h ago.
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://vision-helpdesk.usefulapi.io/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Vision Helpdesk is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
In Claude, open Settings, then Connectors.
Choose Add custom connector, give it a name, and paste the link.
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://vision-helpdesk.usefulapi.io/mcpResponse time at the last check: 83ms. Worked in n/a of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
vision_get_dashboard_countsThe ticket counts of the staff dashboard (quick view): for example new, open, overdue and assigned tickets. ticket / quick_view.vision_list_ticketsList 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_ticketsFind 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_ticketOne ticket with its fields (status, owner, priority, department...) and its posts (the conversation). ticket / ticket_details.vision_list_tickets_by_tagTickets that carry a tag, by tag id. ticket / tag_search.vision_list_tickets_by_labelTickets that carry a label, by label id. ticket / search_label_tickets.vision_list_statusesThe ticket statuses of a department (ids and names), for filters and status changes. ticket / get_status.vision_list_prioritiesThe ticket priorities of a department (ids and names). ticket / get_priority.vision_list_ticket_typesThe ticket types of a department (ids and names). ticket / get_ticket_type.vision_list_clientsList 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_clientsSearch clients by name or email text. client / list_clients.vision_get_client_summaryA client's summary: notes and ticket counts. client / get_summary.vision_create_ticketWRITE: 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 clvision_reply_to_ticketWRITE: 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_noteWRITE: confirm:true required. add an internal note to a ticket (not shown to the client). ticket / add_note with notetype 0.vision_add_client_noteWRITE: confirm:true required. add an internal note to a client record. ticket / add_note with notetype 1.vision_update_ticket_propertyWRITE: 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_staffWRITE: 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_tagWRITE: confirm:true required. add a tag (by title) to a ticket. ticket / add_live_tag.https://vision-helpdesk.usefulapi.io/mcpNot in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Vision Helpdesk to help me. It is a free service with an MCP server at https://vision-helpdesk.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
At the last check (October 30, 2026, 05:41 UTC) the endpoint was working, answering in 83ms. It is checked every 15 minutes.
It was screened on October 30, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
It exposes 19 tools, including vision_get_dashboard_counts, vision_list_tickets, vision_search_tickets, vision_get_ticket. For example, you could ask Muse: "Show me all open tickets in the sales department and assign the highest priority one to me."
This listing was added from public sources (Found in the official MCP Registry (io.usefulapi/vision-helpdesk)). If you build Vision Helpdesk, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/vision-helpdesk"><img src="https://musedirectory.ai/badge/vision-helpdesk.svg" alt="Vision Helpdesk on musedirectory.ai" width="236" height="40"></a>