MCP server for interacting with your LINE Official Account
Nothing to run from here
Enchant 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.
16
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Work with Enchant help desk tickets: list, read, reply, add notes and labels, manage customers.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http enchant-mcp-by-usefulapi https://enchant.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# enchant_list_tickets, enchant_get_ticket, enchant_list_users and 13 more
Enchant 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 enchant-mcp-by-usefulapi https://enchant.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
16 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.
List and filter tickets (newest first by default). Enchant REST: GET /tickets. Use user_ids ["null"] for unassigned tickets. Each result has a short summary; use enchant_get_ticket for messages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | no | Only these ticket ids. |
| inbox_ids | array | no | Only tickets in these inbox ids. |
| states | array | no | Only tickets in these states. |
| user_ids | array | no | Only tickets assigned to these user ids ("null" = unassigned). |
| label_ids | array | no | Only tickets with these label ids. |
| types | array | no | Ticket types, e.g. email, chat, sms, phone, web, twitter, whatsapp. |
| spam | boolean | no | Only spam (true) or only non-spam (false) tickets. |
| trash | boolean | no | Only trashed (true) or only non-trashed (false) tickets. |
| since_created_at | string | no | Only tickets created since this UTC ISO 8601 time, e.g. 2026-01-31T13:41:10Z. |
| since_updated_at | string | no | Only tickets updated since this UTC ISO 8601 time. |
| sort | string | no | Sort order; a leading - means descending. |
| per_page | integer | no | Results per page (0-100, default 10). Use 0 with count to get only the total. |
| page | integer | no | Page number (1-based). Past 10,000 results, filter by since_created_at instead. |
| count | boolean | no | If true, also return the total number of matching results (costs 1 extra rate-limit credit). |
Get one ticket by id. Embed related data with embed: messages (the conversation: replies and notes), customer, user, inbox, labels. Each embedded type costs 1 extra rate-limit credit. Enchant REST: GET /tickets/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Ticket id (the string id, not the friendly ticket number). |
| embed | array | no | Related resources to embed. |
List the help desk users (agents): id, name, email. Use the ids to assign tickets and to author replies and notes. Enchant REST: GET /users.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| per_page | integer | no | Results per page (0-100, default 10). Use 0 with count to get only the total. |
| page | integer | no | Page number (1-based). Past 10,000 results, filter by since_created_at instead. |
List customers, or find one by contact: set contact_type and contact_value (for example email + an address). Enchant REST: GET /customers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_type | string | no | Contact type to match (use with contact_value). |
| contact_value | string | no | Email address or Twitter screen name to match (use with contact_type). |
| since_created_at | string | no | Only customers created since this UTC ISO 8601 time. |
| per_page | integer | no | Results per page (0-100, default 10). Use 0 with count to get only the total. |
| page | integer | no | Page number (1-based). Past 10,000 results, filter by since_created_at instead. |
| count | boolean | no | If true, also return the total number of matching results (costs 1 extra rate-limit credit). |
Get one customer by id, with the contacts (emails, phones, Twitter names). Enchant REST: GET /customers/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Customer id. |
Get the metadata of an attachment (name, size, MIME type) by id; attachment ids appear in ticket messages. Enchant REST: GET /attachments/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Attachment id. |
WRITE: create an email ticket. Give customer_id, or a customer (matched by contact email, created if new). Optionally add the customer's first message with body (needs the customer's email). Enchant REST: POST /tickets.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | yes | Ticket subject. |
| customer_id | string | no | Existing customer id. Give this or customer. |
| customer | object | no | Customer to find or create, instead of customer_id. |
| body | string | no | First inbound message from the customer (plain text). |
| user_id | string | no | User id to assign the ticket to. |
| inbox_id | string | no | Inbox id (the default inbox if omitted). |
WRITE: change a ticket: state (open, hold, closed), assignee, inbox, subject, spam or trash (not both true). label_ids REPLACES all labels (empty array clears them); use enchant_add_ticket_labels to keep existing ones. Enchant REST: PATCH /tickets/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Ticket id. |
| state | string | no | New state. |
| user_id | string/null | no | Assign to this user id; null unassigns the ticket. |
| inbox_id | string | no | Move to this inbox id. |
| subject | string | no | New subject. |
| label_ids | array | no | The full new set of label ids (replaces existing labels). |
| spam | boolean | no | Mark as spam. Cannot be true together with trash. |
| trash | boolean | no | Send to trash. Cannot be true together with spam. |
WRITE: add one or more labels to a ticket without changing its other labels. Enchant REST: PUT /tickets/{id}/labels/{label_ids}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Ticket id. |
| label_ids | array | yes | Label ids to add. |
WRITE: remove one or more labels from a ticket; its other labels stay. Enchant REST: DELETE /tickets/{id}/labels/{label_ids}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Ticket id. |
| label_ids | array | yes | Label ids to remove. |
WRITE: send an outbound reply on a ticket. This SENDS A REAL EMAIL to the customer address in to. Use enchant_add_note for an internal note. Enchant REST: POST /tickets/{id}/messages (type reply, direction out).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Ticket id. |
| user_id | string | yes | Id of the user (agent) the reply is sent as; see enchant_list_users. |
| to | string | yes | Recipient address, normally the customer's email. |
| body | string | yes | Reply body. |
| html | boolean | no | True if body is HTML (default false: plain text). |
| attachment_ids | array | no | Ids of attachments already uploaded. |
WRITE: add an internal note to a ticket (not sent to the customer). Enchant REST: POST /tickets/{id}/messages (type note).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Ticket id. |
| user_id | string | yes | Id of the user (agent) the note is from; see enchant_list_users. |
| body | string | yes | Note body. |
| html | boolean | no | True if body is HTML (default false: plain text). |
| attachment_ids | array | no | Ids of attachments already uploaded. |
WRITE: create a customer with optional contacts (email, twitter, phone). Enchant REST: POST /customers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| first_name | string | no | — |
| last_name | string | no | — |
| summary | string | no | Short free-text summary shown on the customer profile. |
| contacts | array | no | Contacts of the customer. |
WRITE: update a customer's name or summary. If contacts is given, it REPLACES the contact list; use enchant_add_customer_contact to add one. Enchant REST: PATCH /customers/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Customer id. |
| first_name | string | no | — |
| last_name | string | no | — |
| summary | string | no | Short free-text summary shown on the customer profile. |
| contacts | array | no | The full new contact list (replaces the existing one). |
WRITE: add one contact (email, twitter or phone) to a customer. Enchant REST: POST /customers/{id}/contacts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Customer id. |
| type | string | yes | Contact type. |
| value | string | yes | Email address, Twitter screen name or phone number. |
WRITE, DELETES DATA: remove one contact from a customer. Enchant REST: DELETE /customers/{id}/contacts/{contact_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Customer id. |
| contact_id | string | yes | Contact id (from the customer's contacts). |
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 Enchant 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 Enchant 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.