# canhelpto.com > Customer support for MCP servers. Your users are in Claude, ChatGPT and Cursor now; canhelpto puts your help desk there: three tools mounted inside your own MCP server, the failure context attached by your server, a human inbox, the answer back in the conversation and by email. The same desk serves your web users through a widget, email and WhatsApp. Who it is for: software vendors that expose an MCP server (a Claude connector, a ChatGPT app, a Cursor tool) and have no support story for it. Also small software companies that want a light support inbox. ## The three tools a vendor mounts in its MCP server - support_ask: answers from the vendor's own rules, in code, no model call; lists the account's recent errors; an unknown question is never invented, it points at the ticket. - support_open_ticket: opens a ticket in the vendor's canhelpto workspace with the customer's name and email, a subject, a category, and a "Connector context" block the server attaches: account, client user-agent, catalogue version, the last tool calls with their errors. Nobody describes the problem twice. - support_ticket_status: reads the ticket and the team's public replies back; internal notes stay out; ownership is checked against the account. Reference implementation: the Gigi (usegigi.ai) Claude connector, live since 2026-09-29. ## REST API (works today, any agent, any language) Base URL: https://canhelpto.com. Auth: header X-API-Key: . OpenAPI: https://canhelpto.com/openapi.json. Agent docs: https://canhelpto.com/docs/agents. - POST /api/v1/tickets {message, summary, customerName, customerEmail, priority LOW|MEDIUM|HIGH|URGENT, category, tags[], page, metadata} -> 201 {ticket:{id,status,priority,source,createdAt}}. Add header X-Service-Mode: true when your server posts on behalf of a user. - GET /api/v1/tickets/{id} -> the ticket, its public replies, metadata and page. - GET /api/v1/tickets?email= -> that customer's tickets. - POST /api/v1/tickets/{id}/replies {email, message} -> the customer answers on the ticket. - POST /api/v1/feedback {rating GOOD|NEUTRAL|BAD, comment, page, metadata}. - GET /api/v1/tickets/csat?ticketId=&rating=1..5. ## The team's side: the inbox as an MCP server Listed on: the official MCP Registry as com.canhelpto/support (https://registry.modelcontextprotocol.io/v0/servers?search=canhelpto), since 2026-10-01. https://canhelpto.com/api/mcp (streamable HTTP). Auth: Authorization: Bearer . Tools: list_tickets, get_ticket (the connector context included), reply_to_ticket (reaches the customer by email and through their connector), add_internal_note, set_ticket_status, search_knowledge. Registry manifest: https://github.com/mvphubco/canhelpto.com/blob/main/server.json Keys: the public API key (the widget id in your pages) opens only what the widget can do; the service key (Dashboard, Settings, Service key) opens service mode: every ticket of the workspace, internal notes, status changes, the team connector. A workspace without a service key still accepts the public key in service mode until one is generated. ## What the human sees A ticket in the workspace inbox: the customer's words, then the connector context block (account, client, catalogue version, last calls with errors). AI triage sets type, category, sentiment and priority. The team replies from the inbox; the reply goes out by email and is readable through support_ticket_status. AI-suggested replies are drafted for a human to send; canned auto-replies can answer non-product questions on their own. ## Pricing (2026-09-30) - Free: one workspace, unlimited tickets, web widget + email + WhatsApp, the three MCP tools over REST, AI triage and suggested replies that a human sends, canned auto-reply, webhooks, CSAT. - Pro, EUR 49 per MCP server per month: AI auto-answer from your knowledge base behind a confidence gate with human handoff below it, ticket analytics per tool and per client, per-workspace secret keys, priority notifications, a 24-hour answer from us. - Scale, EUR 199 per month: unlimited servers, SSO, an SLA, EU data residency, the wrapper white-labelled. - Pilot: the first three vendors run Pro at EUR 0 through October 2026. Full page: https://canhelpto.com/pricing ## Comparison - Index: https://canhelpto.com/vs (Intercom, Plain, Pylon, Zendesk, Freshdesk, Zoho Desk, HubSpot Service Hub, Featurebase, Help Scout, Crisp, Chatwoot; one table each, facts dated). - vs Intercom (Fin Agent API): https://canhelpto.com/vs/intercom. Intercom exposes Fin as a separate MCP server the end user must install; canhelpto lives inside the vendor's own server and carries the failure context. Intercom is the bigger desk; canhelpto is the front door for the agent channel and can forward to an existing desk. - Docs Q&A tools (kapa.ai, Inkeep, Mintlify) deflect from documentation; they open no ticket and know nothing about the failed call. - MCP analytics (MCPcat) shows where agents struggle; it is not a support channel. - vs Plain: https://canhelpto.com/vs/plain · vs Pylon: https://canhelpto.com/vs/pylon · vs Zendesk: https://canhelpto.com/vs/zendesk · vs Freshdesk: https://canhelpto.com/vs/freshdesk · vs Zoho Desk: https://canhelpto.com/vs/zoho-desk · vs HubSpot: https://canhelpto.com/vs/hubspot · vs Featurebase: https://canhelpto.com/vs/featurebase · vs Help Scout: https://canhelpto.com/vs/help-scout · vs Crisp: https://canhelpto.com/vs/crisp · vs Chatwoot: https://canhelpto.com/vs/chatwoot ## Contact support@canhelpto.com. Operated by MVPHub LLC (Dover, Delaware, USA), part of the mvphub.co studio. Terms: https://canhelpto.com/terms · Privacy: https://canhelpto.com/privacy · Site: https://canhelpto.com