Triage Vision Helpdesk tickets, read conversations, find clients and manage internal handoffs. For support teams and helpdesk operators using Vision Helpdesk. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"vision-helpdesk": {
"url": "https://vision-helpdesk.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"vision-helpdesk": {
"type": "http",
"url": "https://vision-helpdesk.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Read dashboard counts, list the overdue folder and open selected tickets to summarize the conversation and current ownership.
vision_get_dashboard_counts vision_list_tickets vision_get_ticket
Find a client by name or email, then inspect their summary, notes and ticket counts for context.
vision_search_clients vision_get_client_summary
After reviewing the ticket, confirm an internal note, staff assignment or status change to record the handoff.
Changes data · vision_add_ticket_note vision_assign_ticket_staff vision_update_ticket_property
Search for an exact ticket reference or subject, then read its conversation without scanning the whole inbox.
vision_search_tickets vision_get_ticket
The login page asks for your Helpdesk address and API access token.
Address: where your helpdesk runs, for example https://acme.visionhelpdesk.com or https://support.yourcompany.com (https only; if it sits in a folder, include it, for example https://yourcompany.com/support). Credential: use an admin or staff API access token (vis_txttoken) for a role with the API Access permission (Admin Settings → User → Role). Ask your helpdesk administrator for the token if you do not already have one; this form does not accept staff passwords. A dedicated user with only the permissions you need makes its activity easy to track. The REST API is not part of the Starter plan. Your token is used to call only the helpdesk address you enter and is never shown or returned.
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: the login page asks for your Helpdesk address and API access token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Vision Helpdesk connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
vision_get_dashboard_counts | read | 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 | read | 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 | read | 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. |
vision_get_ticket | read | Get ticket One ticket with its fields (status, owner, priority, department...) and its posts (the conversation). ticket / ticket_details. |
vision_list_tickets_by_tag | read | List tickets by tag Tickets that carry a tag, by tag id. ticket / tag_search. |
vision_list_tickets_by_label | read | List tickets by label Tickets that carry a label, by label id. ticket / search_label_tickets. |
vision_list_statuses | read | List ticket statuses The ticket statuses of a department (ids and names), for filters and status changes. ticket / get_status. |
vision_list_priorities | read | List ticket priorities The ticket priorities of a department (ids and names). ticket / get_priority. |
vision_list_ticket_types | read | List ticket types The ticket types of a department (ids and names). ticket / get_ticket_type. |
vision_list_clients | read | 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 | read | Search clients Search clients by name or email text. client / list_clients. |
vision_get_client_summary | read | Get client summary A client's summary: notes and ticket counts. client / get_summary. |
vision_create_ticket | write | 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. |
vision_reply_to_ticket | write | 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 | 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 | 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 | 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. |
vision_assign_ticket_staff | write | 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. |
vision_add_ticket_tag | write | Add tag to ticket WRITE: confirm:true required. add a tag (by title) to a ticket. ticket / add_live_tag. |
vision_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
vision_request_feature | Request a missing feature Tell usefulapi that the user needs something the Vision Helpdesk tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
vision_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Vision Helpdesk (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
vision_cancel_subscription | Cancel the Pro subscription Cancel the caller's Vision Helpdesk Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run vision_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper helpdesk | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Vision Helpdesk 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].
Review overdue support tickets. Look up a customer before replying. Hand off a support ticket. Find tickets by reference or subject. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Vision Helpdesk. The server calls the Vision Helpdesk API with your own Vision Helpdesk access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Helpdesk address and API access token. See Before you connect for where to find them.
No. 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: the login page asks for your Helpdesk address and API access token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Vision Helpdesk API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Vision Helpdesk.
Yes, if you approve it. 7 of the 19 Vision Helpdesk tools can create or change data. The other 12 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Vision Helpdesk server only. Cancel any time: Pro then runs to the end of the paid period. Run vision_usage_status to see how many calls you used.
Ask the AI to run vision_upgrade: it returns a Stripe Checkout link. To cancel, run vision_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with vision_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.