Connect an AI assistant to HelpVox

HelpVox is a remote Model Context Protocol server. Add one URL to your assistant, sign in with your HelpVox account, and it can read your orders, catalogue, conversations, requests and knowledge base — and, with the permissions you grant, move orders, resolve requests and update the FAQ.

https://www.helpvox.ai/mcp

Set up

Works the same on claude.ai and in the Claude desktop app for Mac and Windows. Custom connectors are available on Pro, Max, Team and Enterprise plans.

Open Settings → Connectors (in the app: the Claude menu → Settings → Connectors).
Click Add custom connector.
Name it HelpVox and paste the URL:
```
https://www.helpvox.ai/mcp
```
Leave the advanced OAuth fields empty — HelpVox registers the client on its own.
Click Add, then Connect. A HelpVox window opens: sign in, choose the company and press Allow.
Start a new chat and enable HelpVox from the tools menu. Try: “How many orders are waiting to be processed?”

On Team and Enterprise plans an organisation owner adds the connector first under Organisation settings → Connectors; each member then presses Connect and signs in with their own HelpVox account.

No browser? Use an API key

The OAuth sign-in needs a browser and a localhost redirect. A server without a screen, a CI job or a client that can only send a fixed header can use a HelpVox API key instead: the same key that opens the REST API. Create one under Integrations → HelpVox API keys in the dashboard and send it as a bearer token:

Authorization: Bearer hv_live_…

For example, in Claude Code:

claude mcp add --transport http helpvox https://www.helpvox.ai/mcp --header "Authorization: Bearer hv_live_…"

An API key has every permission of the company, with no per-client approval — keep it where you keep other secrets. Everything done with it is logged as the key, not as a person, and revoking the key under Integrations cuts the assistant off at once.

What you approve

The approval page shows the company (pick one if you belong to several) and the permissions the assistant asked for. Untick any write permission to grant less.

read — orders, catalogue, conversations, callback requests, appointments, knowledge base, account
orders:write — update order status and courier details, add shipment events, create orders
requests:write — resolve callback requests, confirm or cancel appointments
knowledge:write — replace the FAQ / knowledge base
products:write — create, update and delete catalogue products and their prices

Everything the assistant reads or changes is logged as done by the person who connected it. Disconnect it any time from Dashboard → Settings → Connected AI apps; the assistant then has to ask for access again.

Tools

get_account                list_orders            get_order              get_order_events
update_order               add_order_events       create_order
search_products            list_products          get_product
create_products            upsert_products        delete_product
list_conversations         get_conversation
list_callback_requests     resolve_callback_request
list_appointments          update_appointment
list_knowledge             replace_knowledge

Tools not covered by the granted permissions are not offered at all. Each tool mirrors the matching endpoint of the HelpVox REST API — same fields, same status rules, same errors.

If something does not work

Opening the URL in a browser shows a short JSON description. That is expected — the address is for assistants, not browsers. Add it in the client instead.
The approval page says the app is not registered. The client skipped registration; remove the server from the client and add it again with the plain URL, without a client id or secret.
“Needs authentication” after it used to work. Access was revoked in the dashboard or the sign-in expired after 30 days of no use. Run the client’s login step again.
A tool is missing. Its permission was not granted. Disconnect in the dashboard and connect again, leaving that permission ticked.

Technical details for client developers: transport is Streamable HTTP (POST JSON-RPC, no server-sent events); authorization is discovered from /.well-known/oauth-protected-resource/mcp; PKCE S256 is required and dynamic client registration is open.