MCP server for interacting with your LINE Official Account
Nothing to run from here
Re Amaze 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.
17
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Manage Re:amaze conversations, messages, contacts and help articles.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http re-amaze-mcp https://re-amaze.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# reamaze_list_conversations, reamaze_get_conversation, reamaze_list_messages and 14 more
Re Amaze 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 re-amaze-mcp https://re-amaze.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
17 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/search conversations (support tickets). All filters optional; returns a page of conversations. Re:amaze REST: GET /conversations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | string | no | Restrict to a set of conversations. |
| for | string | no | Filter to conversations for this customer email. |
| for_id | string | no | Filter to conversations for this SSO user id. |
| sort | string | no | Sort order. |
| tag | string | no | Filter by tag(s) — comma-separated. |
| category | string | no | Filter by channel slug. |
| start_date | string | no | Filter to items on/after this ISO8601 date, e.g. 2026-01-31. |
| end_date | string | no | Filter to items on/before this ISO8601 date, e.g. 2026-01-31. |
| origin | string | no | Filter by conversation origin/channel type. |
| page | integer | no | 1-based page number to fetch (responses report page_size/page_count/total_count). |
Get a single conversation by its slug. Re:amaze REST: GET /conversations/{slug}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The conversation slug. |
List messages. If conversation (a slug) is given, list that conversation's messages (GET /conversations/{slug}/messages); otherwise list messages across the brand (GET /messages). All other filters optional. Re:amaze REST.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversation | string | no | Conversation slug — scopes to GET /conversations/{slug}/messages (goes in the PATH, not the query). |
| filter | string | no | Restrict to staff or customer messages. |
| tag | string | no | Filter by tag(s) — comma-separated. |
| origin | integer | no | Filter by numeric message origin. |
| page | integer | no | 1-based page number to fetch (responses report page_size/page_count/total_count). |
| sent_by | string | no | Filter to messages sent by this email. |
| category | string | no | Filter by channel slug. |
| start_date | string | no | Filter to items on/after this ISO8601 date, e.g. 2026-01-31. |
| end_date | string | no | Filter to items on/before this ISO8601 date, e.g. 2026-01-31. |
| include | string | no | Include extra fields, e.g. 'original_body'. |
List/search contacts (customers). All filters optional; returns a page of contacts. Re:amaze REST: GET /contacts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | string | no | Free-text filter, e.g. an email or name substring. |
| page | integer | no | 1-based page number to fetch (responses report page_size/page_count/total_count). |
Get a single contact (customer) by identifier (email or id). Re:amaze REST: GET /contacts/{identifier}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| identifier | string | yes | A contact email or id. |
List/search help-center (knowledge-base) articles. All filters optional. Re:amaze REST: GET /articles.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | string | no | Free-text filter, e.g. a title/body substring. |
| page | integer | no | 1-based page number to fetch (responses report page_size/page_count/total_count). |
Get a single help-center article by its slug. Re:amaze REST: GET /articles/{slug}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The article slug. |
List staff (agent) accounts on the brand. Re:amaze REST: GET /staff.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number to fetch (responses report page_size/page_count/total_count). |
List channels (inboxes: email, chat, social, etc.). Channel slugs are used as category filters. Re:amaze REST: GET /channels.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number to fetch (responses report page_size/page_count/total_count). |
Get a single channel by its slug. Re:amaze REST: GET /channels/{slug}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The channel slug. |
Get the conversation-volume report (counts over time). Both dates optional. Re:amaze REST: GET /reports/volume.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | no | Filter to items on/after this ISO8601 date, e.g. 2026-01-31. |
| end_date | string | no | Filter to items on/before this ISO8601 date, e.g. 2026-01-31. |
Get the response-time report (how quickly conversations were answered). Both dates optional. Re:amaze REST: GET /reports/response_time.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | no | Filter to items on/after this ISO8601 date, e.g. 2026-01-31. |
| end_date | string | no | Filter to items on/before this ISO8601 date, e.g. 2026-01-31. |
Create a new conversation (support ticket) with its first message. Re:amaze REST: POST /conversations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | yes | The conversation subject (required). |
| category | string | yes | The channel slug to open the conversation in (required). |
| message_body | string | yes | The first message body — markdown ok (required). |
| user_name | string | yes | The customer's display name (required). |
| user_email | string | yes | The customer's email (required). |
| recipients | array | no | Additional recipients (emails/phones) for the message. |
| tag_list | array | no | Tags to apply to the conversation. |
| status | integer | no | Initial status. Status integer: 0=Open, 1=Responded, 2=Done, 3=Spam, 4=Archived, 5=On Hold, 6=Auto-Done, 7=AI Agent Assigned, 8=AI Agent Done, 9=Spam (AI). |
| assignee | string | no | Staff email to assign the conversation to. |
Add a message to an existing conversation — a customer-facing reply or an internal note. Re:amaze REST: POST /conversations/{slug}/messages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The conversation slug to reply to. |
| body | string | yes | The message body — markdown ok (required). |
| visibility | integer | no | 0 = Regular reply (customer-facing), 1 = Internal Note. Default 0. |
| user_email | string | no | Email of the author (customer or staff). |
| user_name | string | no | Display name of the author. |
| recipients | array | no | Additional recipients (emails/phones). |
| attachment | string | no | URL of a file to attach. |
| suppress_notifications | boolean | no | If true, do not send notification emails for this message. |
Update fields on an existing conversation (subject, status, tags, assignee). Only provided fields change. Re:amaze REST: PUT /conversations/{slug}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The conversation slug to update. |
| subject | string | no | New subject. |
| status | integer | no | New status. Status integer: 0=Open, 1=Responded, 2=Done, 3=Spam, 4=Archived, 5=On Hold, 6=Auto-Done, 7=AI Agent Assigned, 8=AI Agent Done, 9=Spam (AI). |
| tag_list | array | no | Replace the conversation's tags. |
| assignee | string | no | Staff email to assign the conversation to. |
| hold_until | string | no | ISO8601 DateTime to hold the conversation until (used when status=5 On Hold). |
Create a new contact (customer). Re:amaze REST: POST /contacts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The contact's display name (required). |
| string | yes | The contact's email (required). | |
| data | object | no | Arbitrary key/value custom attributes for the contact. |
Update fields on an existing contact. Only provided fields change. Re:amaze REST: PUT /contacts/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The contact id to update (goes in the path, never the body). |
| name | string | no | New display name. |
| string | no | New email. | |
| data | object | no | Arbitrary key/value custom attributes for the contact. |
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 Re Amaze 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 Re Amaze 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.