# Vision Helpdesk Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Vision Helpdesk

Manage helpdesk tickets, search clients, and handle support conversations from your helpdesk system.

- Record: https://musedirectory.ai/connector/vision-helpdesk
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/vision-helpdesk/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 83ms, checked 2026-10-30T05:41:26Z
- Endpoint: https://vision-helpdesk.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-30T05:41:26Z)
- Source: Found in the official MCP Registry (io.usefulapi/vision-helpdesk) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fvision-helpdesk

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.

Example request: "Show me all open tickets in the sales department and assign the highest priority one to me."

How to connect: Not 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.

Tools:
- 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.

Screening checks:
- MCP handshake: pass (Answered in 83ms)
- Domain against threat feeds (Cloudflare security DNS): pass (vision-helpdesk.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: warn (vision_get_ticket: Tool text tells the model to take extra steps)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)