Kayako MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Kayako MCP by usefulapi is answering right now. Last checked 1 min ago. It exposes 21 tools. Last commit 10 Oct 2026.

Search Kayako cases, replies, customers and help-center articles, and reply to or create cases.

Uptime history 13 days of history

13 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

112 ms

Response time

average over 24h

Stars

last commit 10 Oct 2026

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 October 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day

1 Oct a tool changed version

and 3 more, back to 1 October 2026

Nothing serious here today

Today is the operative word: we check Kayako MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add kayako --transport http https://kayako.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "kayako": {
      "url": "https://kayako.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.kayako]
url = "https://kayako.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "kayako": {
      "url": "https://kayako.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "kayako": {
      "url": "https://kayako.usefulapi.io/mcp"
    }
  }
}

Available tools 21

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

kayako

kayako_add_case_tags

WRITE: add tags to a case, keeping its existing tags. Kayako: POST /api/v1/cases/{id}/tags.json.

kayako_create_case

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 kayako_list_case_options. Kayako: POST /api/v1/cases.json.

kayako_create_user

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

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

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

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

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

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

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

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/cases/{id}/posts.json.

kayako_list_cases

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/cases.json.

kayako_list_channels

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/v1/cases/{id}/reply/channels.json or GET /api/v1/cases/channels.json.

kayako_list_organization_cases

List the cases (conversations) raised by members of one organization, newest-updated first. Kayako: GET /api/v1/organizations/{id}/cases.json.

kayako_list_organizations

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

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

List agent teams (id, title, member count) — the ids for assigned_team_id. Kayako: GET /api/v1/teams.json.

kayako_list_users

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_case

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: POST /api/v1/cases/{id}/reply.json.

kayako_search

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

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

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.

Endpoints

URL	Transport	State	Latency	Checked
https://kayako.usefulapi.io/mcp	streamable-http	answering	71 ms	1 min ago

Alternatives to Kayako MCP by usefulapi

same job, measured the same way

Deskpro MCP by usefulapi

by usefulapi

Search tickets, people, organizations and KB articles in Deskpro, and create tickets and replies.

20 tools answering

HelpCrunch MCP by usefulapi

by usefulapi

Manage HelpCrunch chats, customers, agents and knowledge-base articles.

12 tools answering

Orb MCP by usefulapi

by usefulapi

Read Orb customers, subscriptions, invoices, usage and costs; create or update customers.

26 tools answering

Shopmonkey MCP by usefulapi

by usefulapi

Look up shop customers, vehicles, work orders and parts, and create orders or book appointments.

23 tools answering

Linear MCP by usefulapi

by usefulapi

Search, read and create Linear issues, projects, teams and cycles.

8 tools answering

KnowledgeOwl MCP by usefulapi

by usefulapi

Read and write knowledge-base articles, categories, snippets, glossary, readers, and search data.

24 tools answering

Lightspeed Retail (R-Series) MCP by usefulapi

by usefulapi

Read Lightspeed R-Series items, stock, sales, customers and POs; create customers and set stock.

17 tools answering

Tookan MCP by usefulapi

by usefulapi

Read Tookan tasks, agents, teams and customers; create delivery tasks and assign agents.

15 tools answering

Kayako MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Kayako MCP by usefulapi do?

It exposes 21 tools, read directly from the server on our last check. Among them: kayako_add_case_tags, kayako_create_case, kayako_create_user, kayako_get_article, kayako_get_case, kayako_get_me and 15 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Kayako MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 112 ms. The bar chart above shows every period we have measured.

How do I connect Kayako MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Kayako MCP by usefulapi need an API key?

No. Kayako MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 21 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Kayako MCP by usefulapi?

It answers our handshake in 112 ms on average, which is faster than 80% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Kayako MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.