MCP server for interacting with your LINE Official Account
Nothing to run from here
Kayako is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
21
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Search Kayako cases, replies, customers and help-center articles, and reply to or create cases.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http kayako-mcp https://kayako.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# kayako_get_me, kayako_list_cases, kayako_get_case and 18 more
Kayako costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http kayako-mcp https://kayako.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | array | no | Status types to include, e.g. ['OPEN','PENDING']. |
| tags | string | no | Comma-separated tags to filter by. |
| priority | integer | no | Include cases whose priority level is less than or equal to this level. |
| identity_type | string | no | Filter by the requester's identity type; requires identity_value. |
| identity_value | string | no | Email, Facebook username, Twitter screen name or phone number, matching identity_type. |
| ids | array | no | Fetch these case ids instead of filtering. |
| offset | integer | no | Offset into the collection (0-based). Default 0. |
| limit | integer | no | Items per page, 1-100. Kayako's default is 10. |
| include | string | no | Comma-separated resource types to expand instead of returning {id, resource_type} references, e.g. 'user,case_status,case_priority,team', or '*' for all. |
| fields | string | no | Partial-output field rules, e.g. '+tags' to add tags to a case, or 'subject,status' to return only those. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | integer | yes | The case id (integer). |
| include | string | no | Comma-separated resource types to expand instead of returning {id, resource_type} references, e.g. 'user,case_status,case_priority,team', or '*' for all. |
| fields | string | no | Partial-output field rules, e.g. '+tags' to add tags to a case, or 'subject,status' to return only those. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | integer | yes | The case id (integer). |
| filters | string | no | Which kinds of post to return. |
| after_id | integer | no | Cursor: return the page after this post id. |
| before_id | integer | no | Cursor: return the page before this post id. |
| limit | integer | no | Items per page, 1-100. Kayako's default is 10. |
| include | string | no | Comma-separated resource types to expand instead of returning {id, resource_type} references, e.g. 'user,case_status,case_priority,team', or '*' for all. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | integer | no | Existing case to reply on. |
| user_id | integer | no | Requester of a NEW case (ignored with case_id). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | Which list to return. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search text (Kayako Unified Search Language). |
| resources | array | no | Restrict to these resource kinds. |
| limit | integer | no | Max results, 1-30 (default 30). |
| fields | string | no | Resource fields to return, e.g. '*' for full resources. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| role | string | no | Only users of this role type. |
| ids | array | no | Fetch these user ids. |
| offset | integer | no | Offset into the collection (0-based). Default 0. |
| limit | integer | no | Items per page, 1-100. Kayako's default is 10. |
| include | string | no | Comma-separated resource types to expand instead of returning {id, resource_type} references, e.g. 'user,case_status,case_priority,team', or '*' for all. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_id | integer | yes | The user id (integer). |
| include | string | no | Comma-separated resource types to expand instead of returning {id, resource_type} references, e.g. 'user,case_status,case_priority,team', or '*' for all. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| offset | integer | no | Offset into the collection (0-based). Default 0. |
| limit | integer | no | Items per page, 1-100. Kayako's default is 10. |
| include | string | no | Comma-separated resource types to expand instead of returning {id, resource_type} references, e.g. 'user,case_status,case_priority,team', or '*' for all. |
List the cases (conversations) raised by members of one organization, newest-updated first. Kayako: GET /api/v1/organizations/{id}/cases.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| organization_id | integer | yes | The organization id (integer). |
| offset | integer | no | Offset into the collection (0-based). Default 0. |
| limit | integer | no | Items per page, 1-100. Kayako's default is 10. |
| include | string | no | Comma-separated resource types to expand instead of returning {id, resource_type} references, e.g. 'user,case_status,case_priority,team', or '*' for all. |
List agent teams (id, title, member count) — the ids for assigned_team_id. Kayako: GET /api/v1/teams.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| offset | integer | no | Offset into the collection (0-based). Default 0. |
| limit | integer | no | Items per page, 1-100. Kayako's default is 10. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| offset | integer | no | Offset into the collection (0-based). Default 0. |
| limit | integer | no | Items per page, 1-100. Kayako's default is 10. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| section_id | integer | no | Only articles in this section. |
| tags | string | no | Comma-separated tags. |
| filter | string | no | Only pinned or only published articles. |
| offset | integer | no | Offset into the collection (0-based). Default 0. |
| limit | integer | no | Items per page, 1-100. Kayako's default is 10. |
| include | string | no | Comma-separated resource types to expand instead of returning {id, resource_type} references, e.g. 'user,case_status,case_priority,team', or '*' for all. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| article_id | integer | yes | The article id (integer). |
| include | string | no | Resource types to expand. Defaults to 'locale_field' so titles/contents are readable. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search text, at least 3 characters. |
| in | string | no | What to search. Default ALL. |
| locale | string | no | Locale, e.g. en-us. |
| offset | integer | no | Offset into the collection (0-based). Default 0. |
| limit | integer | no | Items per page, 1-100. Kayako's default is 10. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | yes | Case subject. |
| contents | string | yes | Body of the first post. |
| requester_id | integer | yes | The requester (customer user) id (integer). |
| channel | string | yes | MAIL, TWITTER, FACEBOOK or NOTE (internal, not sent). |
| channel_id | integer | no | Channel account id (e.g. the mailbox id). Required unless channel is NOTE. |
| cc | array | no | MAIL only: CC addresses. |
| html | boolean | no | MAIL/NOTE: treat contents as HTML (sanitized by Kayako). |
| priority_id | integer | no | — |
| type_id | integer | no | — |
| status_id | integer | no | — |
| assigned_team_id | integer | no | — |
| assigned_agent_id | integer | no | — |
| form_id | integer | no | — |
| tags | string | no | Comma-separated tags. |
| field_values | object | no | Custom field values keyed by field key, e.g. {"order_number": "1234"}. For multi-select fields pass CSV options — ALL options must be passed; omitted ones are removed. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | integer | yes | The case id (integer). |
| subject | string | no | — |
| requester_id | integer | no | — |
| assigned_team_id | integer | no | — |
| assigned_agent_id | integer | no | — |
| brand_id | integer | no | — |
| status_id | integer | no | — |
| priority_id | integer | no | — |
| type_id | integer | no | — |
| form_id | integer | no | — |
| tags | string | no | Comma-separated tags (sets the list). |
| field_values | object | no | Custom field values keyed by field key, e.g. {"order_number": "1234"}. For multi-select fields pass CSV options — ALL options must be passed; omitted ones are removed. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | integer | yes | The case id (integer). |
| contents | string | yes | Reply or note text. |
| channel | string | yes | NOTE for an internal note; MAIL/TWITTER/FACEBOOK for a public reply. |
| channel_id | integer | no | Channel account id. Required unless channel is NOTE. |
| cc | array | no | MAIL only: CC addresses. |
| html | boolean | no | NOTE only: treat contents as HTML (sanitized by Kayako). |
| status_id | integer | no | Also set the case status. |
| priority_id | integer | no | — |
| type_id | integer | no | — |
| assigned_team_id | integer | no | — |
| assigned_agent_id | integer | no | — |
| tags | string | no | Comma-separated tags. |
WRITE: add tags to a case, keeping its existing tags. Kayako: POST /api/v1/cases/{id}/tags.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | integer | yes | The case id (integer). |
| tags | string | yes | Comma-separated tags to add. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| full_name | string | yes | — |
| role_id | integer | yes | The role id (integer). |
| string | no | Primary email. Required for collaborator/agent/admin roles. | |
| designation | string | no | Job title. |
| team_ids | array | no | Team ids (required for collaborator/agent/admin). |
| organization_case_access | string | no | CUSTOMER only: see only own cases (default) or the whole organization's. |
| time_zone | string | no | — |
| field_values | object | no | Custom field values keyed by field key, e.g. {"order_number": "1234"}. For multi-select fields pass CSV options — ALL options must be passed; omitted ones are removed. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Kayako or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Kayako can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.