MCP server for interacting with your LINE Official Account
Nothing to run from here
Eztexting Com MCP 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.
18
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Official EZTexting MCP server: SMS/MMS messaging, contacts, workflows, and account administration.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mcp-eztexting-com-mcp https://mcp.eztexting.com/mcp/messaging
# 2 — ask your agent for something these tools do
# message_schedule_create_recurring, message_schedule_delete, message_get and 15 more
Eztexting Com MCP costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MEAll 1 server
mcp.eztexting.com1 server
1 category
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, read from the address; if the publisher says otherwise, swap that one word.
claude mcp add --scope user --transport http mcp-eztexting-com-mcp https://mcp.eztexting.com/mcp/messagingReconnect, 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
18 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.
Create a recurring SMS scheduled message (also known as a campaign). name, message, and contactListIds (a.k.a. contact group ids) are required; recurring sends use the first contactListId. start=true launches immediately; omit or false to save as draft. Recurring (recurringFrequency DAY/WEEK/MONTH/YEAR, recurringInterval, recurringOccurrences, recurringStopOn, recurringWeekDays, recurringStartOn y
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contactListIds | array | yes | Contact list ids (a.k.a. contact group ids) |
| fromNumber | string | no | Sending number, E.164 |
| labels | array | no | Labels |
| message | string | yes | Message text |
| name | string | yes | Campaign name |
| recurringFrequency | string | yes | Recurring frequency: DAY, WEEK, MONTH, YEAR |
| recurringInterval | integer | no | Recurring interval, e.g. 2 = every 2 weeks |
| recurringOccurrences | integer | no | Max occurrences before stopping; omit for never-ending |
| recurringStartOn | string | no | Recurring start date-time, yyyy-MM-dd or yyyy-MM-ddTHH:mm, wall-clock time in recurringTimeZone; the first occurrence must be in the future |
| recurringStopOn | string | no | Recurring stop date-time, yyyy-MM-dd or yyyy-MM-ddTHH:mm, wall-clock time in recurringTimeZone |
| recurringTimeZone | string | no | Recurring time zone, e.g. America/Chicago; required when recurringStartOn or recurringStopOn is set |
| recurringWeekDays | array | no | Week days for WEEK frequency, e.g. [MONDAY, FRIDAY] |
| start | boolean | no | true to start immediately, false/omit for draft |
Delete a scheduled message by id. Only DRAFT or SCHEDULED scheduled messages are accepted (irreversible). Pass confirmed=true to actually delete; otherwise returns a confirmation prompt (status is validated either way).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| confirmed | boolean | no | Set true ONLY when the user has explicitly confirmed deletion |
| id | integer | yes | Scheduled message id |
Get message details by id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Message id |
Get full details of a scheduled message (also known as a recurring message or campaign) by id: status, message, fromNumber, contact list ids (a.k.a. contact group ids), labels, delivery window schedule (dates, times, days of week, time zone), and recurring schedule if configured. Status values: DRAFT = created but not yet launched; SCHEDULED = has a future send time (recurring or non-recurring); S
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Scheduled message id |
Paged list of SMS scheduled messages (also known as recurring messages or campaigns) with filters. Use recurring=true to list recurring messages only. Max limit 200, default 10. Returns id, name, status, message preview, fromNumber, labels, recurring per result. Status values: DRAFT = created but not yet launched; SCHEDULED = has a future send time (recurring or non-recurring); START_PENDING = sta
| Parameter | Type | Required | Notes |
|---|---|---|---|
| label | string | no | Filter by label |
| limit | integer | no | Max results (capped at 200), default 10 |
| name | string | no | Filter by name (partial match) |
| offset | integer | no | Zero-based offset for pagination, default 0 |
| recurring | boolean | no | true=recurring only |
| running | boolean | no | true=running only, false=not-running (draft/finished) only |
| scheduled | boolean | no | true=scheduled only |
Paged list of messages with filters and sorting.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contactNumber | string | no | Contact phone, 11 digits |
| incoming | boolean | no | true=incoming, false=outgoing |
| page | integer | no | 1-based page |
| sentAtEnd | string | no | ISO 8601 sent before |
| sentAtStart | string | no | ISO 8601 sent after |
| size | integer | no | Page size: 10|20|50|100|200 |
| sort | string | no | Sort field; '-' prefix = desc |
| textQuery | string | no | Text content match |
| type | string | no | SMS|MMS |
| unread | boolean | no | Unread only |
| userNumber | string | no | Sending phone, 11 digits |
Send a one-off SMS/MMS immediately (or at a future deferred time via sendAt). Requires toNumbers (individual phones) or groupIds (contact groups). Returns message id, type, and recipient count.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fromNumber | string | no | Sending number; required if you have multiple |
| groupIds | array | no | Group ids |
| mediaUrl | string | no | Media URL for MMS, image|video|audio, ≤5MB |
| message | string | no | Text body |
| sendAt | string | no | ISO 8601 future send time for deferred delivery; omit for immediate |
| toNumbers | array | no | Recipient phones, 11 digits each |
Update a non-recurring scheduled message by id (must be in DRAFT or SCHEDULED state — cannot update a running, finished, suspended, or archived message). Updates basic fields (name, message, fromNumber, contactListIds, labels) and/or reschedules the send time (sendAt ISO 8601 with timezone offset, must be a future timestamp, e.g. 2026-09-09T23:50:00-05:00). To manage recurring schedules use messag
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contactListIds | array | no | Contact list ids (a.k.a. contact group ids) — replaces all existing recipients; empty list is ignored (use a non-empty list to change recipients) |
| fromNumber | string | no | Sending number, E.164 |
| id | integer | yes | Scheduled message id |
| labels | array | no | Labels — replaces all existing |
| message | string | no | New message text |
| name | string | no | New name |
| sendAt | string | no | Scheduled send time, ISO 8601 with offset, must be in the future, e.g. 2026-09-09T23:50:00-05:00 |
Update a recurring scheduled message by id (cannot modify ARCHIVED or FINISHED messages). Fetches current state and applies only supplied fields. contactListIds (a.k.a. contact group ids): when supplied, replaces all existing recipients and sets the recurring contactListId; when omitted and adding a new recurring schedule, falls back to the broadcast's existing recipients. labels replace all exist
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contactListIds | array | no | Contact list ids (a.k.a. contact group ids) — replaces all existing recipients; empty list is ignored (use a non-empty list to change recipients) |
| fromNumber | string | no | Sending number, E.164 |
| id | integer | yes | Scheduled message id |
| labels | array | no | Labels — replaces all existing |
| message | string | no | New message text |
| name | string | no | New name |
| recurringFrequency | string | no | Recurring frequency: DAY, WEEK, MONTH, YEAR |
| recurringInterval | integer | no | Recurring interval, e.g. 2 = every 2 weeks |
| recurringOccurrences | integer | no | Max occurrences before stopping; mutually exclusive with recurringStopOn |
| recurringStartOn | string | no | Recurring start date-time, yyyy-MM-dd or yyyy-MM-ddTHH:mm, wall-clock time in recurringTimeZone; the first occurrence must be in the future |
| recurringStopOn | string | no | Recurring stop date-time yyyy-MM-dd or yyyy-MM-ddTHH:mm, wall-clock time in recurringTimeZone; mutually exclusive with recurringOccurrences |
| recurringTimeZone | string | no | Recurring time zone, e.g. America/Chicago; required when recurringStartOn or recurringStopOn is set (or if the schedule has no zone yet) |
| recurringWeekDays | array | no | Week days for WEEK frequency, e.g. [MONDAY, FRIDAY] |
List messages in a conversation (user+contact). read=true marks them read.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contactNumber | string | yes | Contact phone, 11 digits |
| page | integer | no | 1-based page |
| read | boolean | no | Mark returned messages read |
| size | integer | no | Page size: 10|20|50|100|200 |
| userNumber | string | yes | Sending phone, 11 digits |
Paged list of conversations with filters (unread, from, archived, optType, query) and sorting.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| archived | boolean | no | Archived flag |
| from | string | no | Sending phone, 11 digits |
| optType | string | no | — |
| page | integer | no | 1-based page |
| query | string | no | Search contact name, phone, or last message text |
| size | integer | no | Page size: 10|20|50|100|200 |
| sort | string | no | Sort field; '-' prefix = desc |
| unread | boolean | no | Unread only |
Mark conversation messages by id. state=read|unread.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | Message ids |
| state | string | yes | READ|UNREAD |
Archive or restore a conversation. action=archive|restore.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | ARCHIVE|RESTORE |
| contactNumber | string | yes | Contact phone, 11 digits |
| userNumber | string | yes | Sending phone, 11 digits |
Delete message template by id (irreversible). Pass confirmed=true to actually delete; otherwise returns a no-op confirmation preview.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| confirmed | boolean | no | Set true ONLY when the user has explicitly confirmed deletion |
| id | string | yes | Template id |
Message templates (id, name, company, message text, media). Max 200. Omit id to list (filters: name exact, nameLike partial). Set id to fetch single.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | no | Template id; omit to list |
| name | string | no | Name, exact |
| nameLike | string | no | Name, partial match |
Create or update message template. Name and message required. Omit id to create.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| companyName | string | no | Company name |
| id | string | no | Template id; omit to create |
| mediaFileId | string | no | Media file id (MMS) |
| mediaFileUrl | string | no | Media file URL (MMS) |
| message | string | yes | Message body |
| name | string | yes | Name |
Delivery + engagement breakdown and link click stats for a message.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Message id |
Contacts + responses for a message. type=engagement|delivery|link drives valid status values.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fullUrl | string | no | URL-encoded full URL; link type only |
| id | string | yes | Message id |
| page | integer | no | 1-based page |
| size | integer | no | Page size: 10|20|50|100|200 |
| sort | string | no | Sort field; '-' prefix = desc |
| status | string | yes | engagement: replied|opted_out. delivery: delivered|bounced|queued|not_sent. link: clicked|not_clicked |
| type | string | yes | ENGAGEMENT|DELIVERY|LINK |
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 Eztexting Com MCP 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. 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.
1.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 Eztexting Com MCP 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.