MCP server for interacting with your LINE Official Account
Nothing to run from here
Zammad MCP by usefulapi 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.
19
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Search and read Zammad tickets, customers and organizations; add notes, replies and ticket updates.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http zammad-mcp-by-usefulapi https://zammad.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# zammad_get_me, zammad_search_tickets, zammad_list_tickets and 16 more
Zammad MCP by usefulapi 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 zammad-mcp-by-usefulapi https://zammad.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
19 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.
The Zammad user this access token belongs to: id, name, e-mail, roles and groups. Use it to confirm the connection and the token's permissions. GET /api/v1/users/me.
No parameter schema on file.
Search tickets with Zammad's query syntax. With Elasticsearch on the instance you can use fields, e.g. state.name:open AND group.name:Sales, customer.email:"a@b.com", title:invoice, number:20001; a plain word searches ticket text. Replies carry ids plus names (group, state, priority, owner, customer). GET /api/v1/tickets/search?expand=true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query. |
| sort_by | string | no | Field to sort by, e.g. updated_at or created_at. |
| order_by | string | no | Sort direction (default: relevance). |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | no | Results per page, 1-100 (default 25). |
List the tickets the token's user can see (an agent sees the tickets of their groups; a customer only their own). For anything targeted use zammad_search_tickets. GET /api/v1/tickets?expand=true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | no | Results per page, 1-100 (default 25). |
One ticket by its numeric id (not the ticket number): title, group, state, priority, owner, customer, organization, dates, escalation and article count. GET /api/v1/tickets/{id}?expand=true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | Zammad ticket id (the number in the ticket URL, not the 5-digit ticket number). |
All articles (messages, internal notes, e-mails, phone notes) of one ticket in order, with sender, type, internal flag, from/to/cc, subject, body and attachment names (attachments are not downloaded). Long bodies are cut at 6000 characters; use zammad_get_ticket_article for the full text. GET /api/v1/ticket_articles/by_ticket/{ticket_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | Zammad ticket id. |
One article by its id with its full body, headers and attachment names. GET /api/v1/ticket_articles/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| article_id | integer | yes | Zammad article id (from zammad_list_ticket_articles). |
The tags on one ticket. GET /api/v1/tags?object=Ticket&o_id={ticket_id}. Needs an agent token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | Zammad ticket id. |
The ticket states of the instance (new, open, pending reminder, pending close, closed, ...) with ids and whether they are active. Use the names in zammad_update_ticket. GET /api/v1/ticket_states.
No parameter schema on file.
The ticket priorities of the instance (e.g. '1 low', '2 normal', '3 high') with ids. Use the names in zammad_update_ticket. GET /api/v1/ticket_priorities.
No parameter schema on file.
The ticket groups (queues) of the instance, with ids, names and agent ids. Zammad requires the admin.group permission for this list; with an agent-only token it returns an authorization error. GET /api/v1/groups.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | no | Results per page, 1-100 (default 25). |
Search customers and agents by name, e-mail, login, phone or organization. Returns profile fields (no credentials). Needs an agent token. GET /api/v1/users/search?expand=true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search text, e.g. an e-mail address or a name. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | no | Results per page, 1-100 (default 25). |
One user (customer or agent) by id: name, e-mail, phone, organization, roles, VIP flag and notes. No credentials. GET /api/v1/users/{id}?expand=true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_id | integer | yes | Zammad user id. |
Search customer organizations by name or domain. Needs an agent token. GET /api/v1/organizations/search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search text, e.g. an organization name. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | no | Results per page, 1-100 (default 25). |
List customer organizations with domain, VIP flag and member ids. Needs an agent token. GET /api/v1/organizations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | no | Results per page, 1-100 (default 25). |
One organization by id: name, domain, notes, VIP flag, member ids. GET /api/v1/organizations/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| organization_id | integer | yes | Zammad organization id. |
WRITE: add an INTERNAL note (visible to agents only, never e-mailed to the customer) to ONE ticket. Needs an agent's token (a customer's token is refused, because Zammad would make the note public). The ticket's other data is not changed. POST /api/v1/ticket_articles with type=note, internal=true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | Zammad ticket id. |
| body | string | yes | Note text (plain text). |
| subject | string | no | Optional note subject (one line). |
WRITE: send a customer-visible reply on ONE ticket. THIS E-MAILS A REAL PERSON: the reply is delivered by e-mail to exactly ONE recipient and cannot be recalled. By default the recipient is the ticket's customer (looked up from the ticket); to may name one other single address. No cc, no bulk, no attachments. Needs an agent's token (a customer's token is refused). For an internal remark use zamm
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | Zammad ticket id. |
| body | string | yes | Reply text (plain text). |
| to | string | no | Optional: ONE recipient e-mail address. Default: the ticket customer's address. |
| subject | string | no | Optional subject (one line). Default: 'Re: <ticket title>'. |
WRITE: change fields of ONE ticket: state, priority, owner (agent), group and/or title. Use names from zammad_list_ticket_states / zammad_list_ticket_priorities / zammad_list_groups. Pending states need pending_time. Never deletes, removes or merges (those states are refused). The instance's own triggers still run, so closing or reassigning a ticket can send the customer or agent a notification
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | Zammad ticket id. |
| state | string | no | State name, e.g. open, closed, 'pending reminder'. |
| priority | string | no | Priority name, e.g. '3 high'. |
| owner_id | integer | no | User id of the agent who should own the ticket. Id 1 is Zammad's 'no owner' placeholder. |
| group | string | no | Group name, e.g. Sales (subgroups as Sales::Europe). |
| title | string | no | New ticket title. |
| pending_time | string | no | Required for the pending states: when the ticket reminds or closes, ISO 8601 with a timezone. |
WRITE: create ONE new ticket for an EXISTING customer (by e-mail address or user id) in a group, with a first article recorded as written by the customer (type note or phone). It does not send an e-mail by itself, but the instance's triggers may (for example an automatic confirmation to the customer). It never creates new users. POST /api/v1/tickets.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Ticket title. |
| group | string | yes | Group name the ticket goes to, e.g. Users or Sales. |
| customer | string | no | E-mail address of an existing customer. Give this or customer_id. |
| customer_id | integer | no | User id of an existing customer. Give this or customer. |
| body | string | yes | First message of the ticket (plain text). |
| subject | string | no | Subject of the first article (default: the title). |
| article_type | string | no | Type of the first article: note (default) or phone. |
| state | string | no | Initial state name (default: new). |
| priority | string | no | Initial priority name (default: 2 normal). |
| owner_id | integer | no | User id of the agent who should own the ticket. |
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 Zammad MCP by usefulapi 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.0.0.
1.0.0
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 Zammad MCP by usefulapi 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.