Kerux for Claude
Connect Claude to your Kerux helpdesk and ask about your support in plain words. Claude reads your workspace live and can save a suggested reply as a draft for your team to approve. The thinking runs on your Claude plan, so it uses none of the AI key you connected to Kerux.
Try asking
- “How many open tickets does each person on my team have right now?”
- “Which tickets have customers been waiting on for more than a day?”
- “How did support go over the last 7 days? What were the top topics?”
- “Read the latest ticket from Maria and suggest a reply using our help articles.”
Connect it
- In Claude, open Settings → Connectors and choose Add custom connector.
- Paste
https://www.kerux.io/api/mcpand select Connect. - Sign in to Kerux if asked, review what Claude will be able to do, and select Allow.
You need a Kerux account. The connector sees the same workspace you see when you sign in, and a viewer account stays read-only. Disconnect any time in Kerux under Settings → Integrations, or remove the connector in Claude.
Uses your Claude plan, by design
A person on your team asks, Claude works through the queue and drafts, and the person approves. That is the use your Claude plan covers. Answering customers on its own, around the clock, is what Kerux's autopilot does on your own AI key, at about 3¢ an answer.
Other AI apps
The connector follows the open MCP standard with OAuth sign-in, the same one other AI apps use for custom connectors. We've tested it in Claude. If your app supports remote MCP connectors, the same URL is the one to try; tell us how it goes.
What it can do
Counts unresolved tickets in Kerux per teammate (open, pending, needing a human, oldest age in hours), plus unassigned tickets and tickets the AI is handling.
Lists unresolved Kerux tickets where the customer sent the latest message and has been waiting at least hours (default 24), longest wait first, with assignee and SLA status.
Summarises Kerux support over the last days (default 30): tickets created and closed, by channel, AI answers and hand-offs, median first response, SLA breaches, CSAT, negative sentiment and top topics.
Finds Kerux tickets whose subject, customer name or customer email contains query, optionally filtered by status. Returns up to limit summaries, newest first.
Returns one Kerux ticket with its full conversation (customer and team messages as plain text), internal notes, assignee, status, SLA and a link to open it in Kerux.
Searches the company's published Kerux help-center articles by title and body, returning matching articles with their text, for grounding an answer in the company's own documentation.
Saves a proposed reply on a Kerux ticket as a pending draft. A teammate reviews, edits, sends or discards it in Kerux. Nothing is sent to the customer by this tool.
It can't send email, close tickets, change settings or delete anything.
Your data
- Kerux answers each request from your workspace at the moment Claude asks. Kerux doesn't keep a copy of your Claude conversations.
- What Claude reads is handled under your agreement with Anthropic, the same as anything else you share in Claude.
- Access is through a sign-in you approve. Tokens are stored only as hashes and expire; disconnecting cuts access immediately.
- More detail is in our Privacy Policy and on the Security page.
Help
Email support@kerux.io.