MCP server
Kayako MCP by usefulapi
io.usefulapi/kayako
Checked 26 Oct 2026, 08:29 UTC · Connected to it and listed its tools
Search Kayako cases, replies, customers and help-center articles, and reply to or create cases.
Working at last checkVerified publisher: usefulapi.ioAbout 6,382 tokens per request once connected21 tools
https://kayako.usefulapi.io/mcp
At a glance
- Type
- MCP server
- Publisher
- usefulapi.io (verified by the MCP Registry)
- Status
- Working at last check
- Tools
- 21
- Token cost
- About 6,382 tokens per request
- Sets up in
- Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok
- Last checked
- 26 Oct 2026, 08:29 UTC
Connect it to your agent
Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.
Claude Code
claude mcp add --transport http kayako https://kayako.usefulapi.io/mcp
Claude Desktop
Settings → Connectors → Add custom connector, and paste the URL.
Codex (config.toml)
[mcp_servers.kayako] url = "https://kayako.usefulapi.io/mcp"
Gemini CLI
{"mcpServers":{"kayako":{"httpUrl":"https://kayako.usefulapi.io/mcp"}}}
Cursor
{"mcpServers":{"kayako":{"url":"https://kayako.usefulapi.io/mcp"}}}
VS Code
{"servers":{"kayako":{"type":"http","url":"https://kayako.usefulapi.io/mcp"}}}
Antigravity
agy mcp add kayako https://kayako.usefulapi.io/mcp
ChatGPT
Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.
OpenAI API (Responses tools)
{"type":"mcp","server_label":"kayako","server_url":"https://kayako.usefulapi.io/mcp","require_approval":"always"}
Grok (xAI API tools)
{"type":"mcp","server_label":"kayako","server_url":"https://kayako.usefulapi.io/mcp"}
Tools
kayako_add_case_tags~142 tokens
WRITE: add tags to a case, keeping its existing tags. Kayako: POST /api/v1/cases/{id}/tags.json.kayako_create_case~684 tokens
WRITE: open a new case (conversation) for a requester. channel MAIL sends the first message to the customer by email from the mailbox given as channel_id; channel NOTE creates it with an internal note and emails nobody. Get channel ids from kayako_list_channels and status/priority/type ids from kayakayako_create_userChanges accounts · ~463 tokens
WRITE: create a user — typically a CUSTOMER to use as requester_id on a new case. role_id comes from kayako_list_roles. Collaborator/agent/admin roles also require email and team_ids. No password is set by this tool. Kayako: POST /api/v1/users.json.kayako_get_article~187 tokens
Fetch one knowledge-base article with its localized titles and contents expanded (include defaults to 'locale_field'), status, section, tags, votes and help-center URL. Kayako: GET /api/v1/articles/{id}.json.kayako_get_case~271 tokens
Fetch one case (conversation) by id: subject, requester, assignee, status, priority, type, SLA metrics, custom fields, last post preview. Use include (e.g. 'user,case_status,case_priority,team') to expand references and fields='+tags' for tags. Kayako: GET /api/v1/cases/{id}.json.kayako_get_me~90 tokens
Fetch the Kayako user these credentials belong to (name, role, teams, locale). A cheap way to confirm the subdomain and credentials work. Kayako: GET /api/v1/me.json.kayako_get_user~201 tokens
Fetch one user by id: name, role, organization, teams, identities (emails, phones, social), custom fields. include='identity_email,organization' expands references. Kayako: GET /api/v1/users/{id}.json.kayako_list_articles~321 tokens
List knowledge-base articles, optionally by section, tags, or PUBLISHED / PINNED. Titles and contents are locale references unless include='locale_field'. Kayako: GET /api/v1/articles.json.kayako_list_case_options~158 tokens
List the instance's case statuses (id, label, type), priorities (id, label, level) or types (id, label, type) — the ids needed for status_id / priority_id / type_id when creating, updating or replying to a case. Kayako: GET /api/v1/cases/{statuses|priorities|types}.json.kayako_list_case_posts~418 tokens
Read a case's timeline: customer messages, agent replies and internal notes (newest first). By default activities are excluded; filters='NOTES' for internal notes only, 'MESSAGES' for messages, 'ALL' to include activities. Paginate with before_id / after_id (one at a time). Kayako: GET /api/v1/caseskayako_list_cases~572 tokens
List cases (conversations / tickets), newest-updated first. Filter by status type, tags, max priority level, or a requester identity (email, Twitter screen name, Facebook username, phone); or fetch specific ids. Nested resources are references unless `include` expands them. Kayako: GET /api/v1/caseskayako_list_channels~224 tokens
List the channels (MAIL mailbox, TWITTER, FACEBOOK, NOTE) usable for a reply on an existing case (pass case_id) or for a new case (omit case_id; optionally pass the requester's user_id). A channel's account.id is the channel_id to pass to kayako_reply_to_case / kayako_create_case. Kayako: GET /api/vkayako_list_organization_cases~266 tokens
List the cases (conversations) raised by members of one organization, newest-updated first. Kayako: GET /api/v1/organizations/{id}/cases.json.kayako_list_organizations~232 tokens
List customer organizations (name, domains, phone, custom fields), oldest first. To find one by name use kayako_search with resources=['ORGANIZATIONS']. Kayako: GET /api/v1/organizations.json.kayako_list_roles~157 tokens
List user roles (id, title, type OWNER/ADMIN/AGENT/COLLABORATOR/CUSTOMER) — the role_id needed by kayako_create_user. Kayako: GET /api/v1/roles.json.kayako_list_teams~144 tokens
List agent teams (id, title, member count) — the ids for assigned_team_id. Kayako: GET /api/v1/teams.json.kayako_list_users~308 tokens
List users (customers, collaborators, agents, admins), newest first, optionally by role type or specific ids. To find a user by email or name use kayako_search. Kayako: GET /api/v1/users.json.kayako_reply_to_caseSends messages · ~544 tokens
WRITE: add a post to a case. channel NOTE adds an INTERNAL note visible only to agents (no channel_id needed). channel MAIL/TWITTER/FACEBOOK sends a PUBLIC reply to the customer — get channel_id from kayako_list_channels with case_id. Can also set status/priority/assignee in the same call. Kayako: Pkayako_search~252 tokens
Unified search across conversations (cases), users and organizations. Returns id, title, snippet, relevance and resource type; pass fields='*' to get each full resource inline. Max 30 results. Kayako: GET /api/v1/search.json.kayako_search_help_center~266 tokens
Search the help center's articles and/or public conversations. Returns references (e.g. {id, resource_type: 'article'}); read an article with kayako_get_article. Kayako: GET /api/v1/helpcenter/search.json.kayako_update_case~482 tokens
WRITE: change a case's subject, requester, assignee (team/agent), status, priority, type, brand, form, tags or custom fields. Sends nothing to the customer. `tags` sets the case's tag list (use kayako_add_case_tags to append). Trashing is deliberately not exposed. Kayako: PUT /api/v1/cases/{id}.json
Browse
Related MCP servers
- Supovia Customer Support
Reply to and resolve customer chats, search your help docs and see which conversations need you. - Summer
Telehealth support for Claude, Codex and Cursor: investigate cases and connect your tools. - Zammad MCP by usefulapi
Search and read Zammad tickets, customers and organizations; add notes, replies and ticket updates. - Re:amaze MCP by usefulapi
Manage Re:amaze conversations, messages, contacts and help articles. - Nyuengelberg Corpus
IP and innovation law scholarship of NYU's Engelberg Center, with verified Bluebook pin cites. - Refapp Help
Answers how Refapp works from its help center, with article links. No sign-in, no customer data. - Deskpro MCP by usefulapi
Search tickets, people, organizations and KB articles in Deskpro, and create tickets and replies. - HappyFox MCP by usefulapi
Triage HappyFox tickets, contacts and KB articles, run reports, and reply or add private notes.
Badge for your README
[](https://aptlynx.net/servers/io.usefulapi/kayako)
Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents