Vision Helpdesk MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.7.4Updated Nov 7, 2026

Triage Vision Helpdesk tickets, read conversations, find clients and manage internal handoffs.

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableCommunication & Collaboration Business & Commerce

Server details

Identifier: io.usefulapi/vision-helpdesk
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 30, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to usefulapi.io, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.usefulapi%2Fvision-helpdesk.svg)](https://sourceweft.com/mcp/io.usefulapi%2Fvision-helpdesk?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Connects an assistant to a Vision Helpdesk instance to triage tickets, read conversations, look up clients and make confirmed updates.

What you can do: View dashboard ticket counts and list, search or open tickets with their full conversation.
Filter tickets by tag, label, status, priority or type, and list the statuses, priorities and types of a department.
List and search clients, and read a client's notes and ticket counts.
Create tickets, reply to tickets, and add internal notes to tickets or client records.
Change ticket status, priority, department or type, assign or unassign staff, and add tags.
Check usage, request a feature, and manage or cancel the subscription.
When to use it: Useful for support and helpdesk teams that want an assistant to summarize incoming tickets, find a customer's history, draft replies, or keep statuses, owners and tags up to date without switching to the helpdesk UI.
Requirements: A remote MCP endpoint added by URL only; the server signs in with OAuth and the login page asks for Vision Helpdesk credentials. Needs a public HTTPS helpdesk address and an admin or staff API access token (vis_txttoken) from a role with API Access permission; the vendor's Starter plan does not include the REST API.

Before you install

Write tools create tickets, post replies, add notes, change ticket properties, assign staff and add tags; they require confirm:true and should be confirmed by the user first. Replies can be made visible to the client and optionally emailed, so check visibility and email flags. The service is metered: free plan 50 calls per month, paid plans with Stripe checkout links, and cancellation has no refund for the current period.

Installation

In SourceWeft

Open Vision Helpdesk MCP by usefulapi in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Fvision-helpdesk/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

Vision Helpdesk MCP by usefulapi

Connect your assistant at https://vision-helpdesk.usefulapi.io/mcp.

Connect

Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://vision-helpdesk.usefulapi.io/mcp.
Claude Code: claude mcp add --transport http vision-helpdesk https://vision-helpdesk.usefulapi.io/mcp, then run /mcp to log in.
VS Code: Add to VS Code.
Cursor and other clients: add the URL as a remote MCP server:

json

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

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

Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Vision Helpdesk credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/vision-helpdesk/

Enter your public HTTPS helpdesk address and an admin or staff API access token (vis_txttoken). Ask your helpdesk administrator for the token if you do not already have one. Your role needs API Access permission, and the vendor's Starter plan does not include the REST API.

Use the URL of your hosted helpdesk or your publicly reachable installation, including its folder if applicable. The connector sends your token only to that address and does not follow API redirects.

Every write requires explicit confirmation. Ticket creation and replies disable customer email by default. Internal tickets stay private and cannot include client recipients or customer email flags.

Tools

Tool	Type	What it does
`vision_get_dashboard_counts`	read	Get dashboard counts
`vision_list_tickets`	read	List tickets
`vision_search_tickets`	read	Search tickets by reference or subject
`vision_get_ticket`	read	Get ticket
`vision_list_tickets_by_tag`	read	List tickets by tag
`vision_list_tickets_by_label`	read	List tickets by label
`vision_list_statuses`	read	List ticket statuses
`vision_list_priorities`	read	List ticket priorities
`vision_list_ticket_types`	read	List ticket types
`vision_list_clients`	read	List clients
`vision_search_clients`	read	Search clients
`vision_get_client_summary`	read	Get client summary
`vision_create_ticket`	write	Create ticket
`vision_reply_to_ticket`	write	Reply to ticket
`vision_add_ticket_note`	write	Add ticket note
`vision_add_client_note`	write	Add client note
`vision_update_ticket_property`	write	Update ticket status, priority, department or type
`vision_assign_ticket_staff`	write	Assign or unassign ticket staff
`vision_add_ticket_tag`	write	Add tag to ticket
`vision_usage_status`	meta	Usage status (free-tier meter)
`vision_request_feature`	meta	Request a missing feature
`vision_upgrade`	meta	Upgrade to Pro or Pro+
`vision_cancel_subscription`	meta	Cancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].

Pro covers this server only. Subscribe with vision_upgrade (it returns a Stripe Checkout link). Cancel any time with vision_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running vision_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT. An independent integration by usefulapi; not affiliated with Vision Helpdesk.

Source: servers/vision-helpdesk/README.md at commit 4046075

Tools

vision_get_dashboard_counts

Get dashboard counts

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

Takes no parameters.

vision_list_tickets

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.

Parameterslimitfolderoffsetstatus_idticket_iddepartment_idinclude_count

vision_search_tickets

Search tickets by reference or subject

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.

Parameterslimitoffsetsubjectticket_hash

vision_get_ticket

Get ticket

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

Parametersticket_idrequired

vision_list_tickets_by_tag

List tickets by tag

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

Parameterstag_idrequired

vision_list_tickets_by_label

List tickets by label

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

Parameterslabel_idrequired

vision_list_statuses

List ticket statuses

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

Parametersdepartment_idrequired

vision_list_priorities

List ticket priorities

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

Parametersdepartment_idrequired

vision_list_ticket_types

List ticket types

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

Parametersdepartment_idrequired

vision_list_clients

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.

Parameterslimitoffsetclient_idparent_idfirst_nameinclude_count

vision_search_clients

Search clients

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

Parameterstextrequiredlimitoffset

vision_get_client_summary

Get client summary

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

Parametersclient_idrequired

vision_create_ticket

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 client recipients or email enabled. Look up the department, status, priority and type ids first (vision_list_statuses, vision_list_priorities, vision_list_ticket_types). ticket / open_new_ticket.

Parametersccfromrequiredconfirmrequiredmessagerequiredsubjectrequiredtype_idrequiredinternalas_clientclient_iddomain_idrequiredowner_idsstatus_idrequired+6 more

vision_reply_to_ticket

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.

Parametersfromrequiredconfirmrequiredmessagerequiredticket_idrequiredsend_emailvisible_to_clientrequired

vision_add_ticket_note

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.

Parametersnoterequiredconfirmrequiredticket_idrequired

vision_add_client_note

Add client note

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

Parametersnoterequiredconfirmrequiredclient_idrequired

vision_update_ticket_property

Update ticket status, priority, department or type

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.

Parametersconfirmrequiredpropertyrequiredvalue_idrequiredticket_idrequired

vision_assign_ticket_staff

Assign or unassign 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.

Parametersactionrequiredconfirmrequiredstaff_idrequiredticket_idrequired

vision_add_ticket_tag

Add tag to ticket

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

Parameterstagrequiredconfirmrequiredticket_idrequired

Version history

v1.7.4LatestNov 7, 2026
v1.6.3Nov 5, 2026
v1.6.2Nov 5, 2026
v1.6.1Nov 4, 2026
v1.6.0Nov 3, 2026
v1.5.1Nov 3, 2026
v1.4.0Nov 1, 2026
v1.2.0Oct 31, 2026
v1.1.0Oct 31, 2026
v1.0.2Oct 30, 2026
v1.0.0Oct 30, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Business & Commerce5 toolsNov 7, 2026

Plan	Price	Limit
Free	$0	50 tool calls / month
Pro (per helpdesk)	$9/mo or $90/yr (2 months free)	Unlimited*