[](https://github.com/dealfluence/adeu) [![MCP
from $29/mo
Tools
message_schedule_create_recurring
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
ArgumentsA call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
—
p95 latency
—
call success
—
uptime 90d
0
calls last 7d
What it does
Official EZTexting MCP server: SMS/MMS messaging, contacts, workflows, and account administration.
Quickstart
# 1 — install (mcprush login holds a key from your dashboard)
npx mcprush@latest add mcp-eztexting-com-mcp
# 2 — ask your agent something
> Official EZTexting MCP server: SMS/MMS messaging, contacts, workflows, and account administration.
Mcp is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
MCAll 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 — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add --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 to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry pointing at the gateway. The server itself runs on the publisher’s own infrastructure, so 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
Takes no parameters.
Example callreturns →
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).
Takes no parameters.
Example callreturns →
Get message details by id.
Takes no parameters.
Example callreturns →
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
Takes no parameters.
Example callreturns →
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
Takes no parameters.
Example callreturns →
Paged list of messages with filters and sorting.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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
Takes no parameters.
Example callreturns →
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
Takes no parameters.
Example callreturns →
List messages in a conversation (user+contact). read=true marks them read.
Takes no parameters.
Example callreturns →
Paged list of conversations with filters (unread, from, archived, optType, query) and sorting.
Takes no parameters.
Example callreturns →
Mark conversation messages by id. state=read|unread.
Takes no parameters.
Example callreturns →
Archive or restore a conversation. action=archive|restore.
Takes no parameters.
Example callreturns →
Delete message template by id (irreversible). Pass confirmed=true to actually delete; otherwise returns a no-op confirmation preview.
Takes no parameters.
Example callreturns →
Message templates (id, name, company, message text, media). Max 200. Omit id to list (filters: name exact, nameLike partial). Set id to fetch single.
Takes no parameters.
Example callreturns →
Create or update message template. Name and message required. Omit id to create.
Takes no parameters.
Example callreturns →
Delivery + engagement breakdown and link click stats for a message.
Takes no parameters.
Example callreturns →
Contacts + responses for a message. type=engagement|delivery|link drives valid status values.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Mcp costs nothing to install and nothing to call, 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: $8.42
$16.58 left
—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 a hosted endpoint: the publisher runs it and we connect to it. The scanner reads packages and source, and neither exists to read here, so there is no grade — not a withheld one, an unmeasured one. What can be checked instead is on Installation: what it asks to reach and what it writes.
Release history
Pinned to 1.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Mcp in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
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 an account with 50 real tool calls against it.