Everything, one plan
$59
per month
14-day free trial
Cancel anytime
- ✓ Mac app + menu bar connector
- ✓ Hosted MCP server
- ✓ Web dashboard + cloud sync
- ✓ REST API + webhooks
- ✓ HubSpot & GoHighLevel connectors
- ✓ Deliverability health panel
Your device.
Your number.
A real uncapped iMessage API.
autoMessage installs the full automation stack — MCP server, REST API, webhooks — on the Mac you already own. The same infrastructure device farms run. You're just not locked out of it.
14-day free trial, then $59/mo. Cancel anytime.
Try it now
This is our sales line. It's a bot.
Not a sandbox — the actual number we do business on, answered by an n8n workflow running on autoMessage. Text it anything. You'll get a reply from a real iMessage number, in a real thread, exactly the way your own automations will.
If you want to know whether this works, the most honest answer we can give is to let you talk to the thing we built it for.
No signup, no form, nothing to install. You text us, so we never collect your number.
Text me
Scan to open it on your phone
Works with every AI you already use.
Plus 7,000+ platforms and CRMs. Automated iMessage in five minutes.
The loop is the point: a text arrives on your phone, reaches your stack, something drafts a reply, and it goes back out from your own number into the same thread. autoMessage ships a native MCP server, a REST API, and webhooks to close it. Claude Desktop, Claude Code, Cursor, ChatGPT Desktop, Cline, Codex, and n8n plug in with one config line. HubSpot, GoHighLevel, Salesforce, Zapier, and Make connect through the API.
- Claude
- ChatGPT
- Cursor
- n8n
- Zapier
- Make
- HubSpot
- HighLevel
- Salesforce
- Slack
- Notion
- Webhooks
How it works
- 1
Install the Mac app
Download the menu bar app, grant Full Disk Access, sign in. Two minutes, no dev setup.
- 2
Connect your AI or CRM
Add the autoMessage MCP server to your AI client, or point a webhook / REST call from your CRM. One config line either way.
- 3
Blast blue bubbles
Your AI reads, drafts, and sends iMessages from your number. Track everything from the dashboard.
Already on your phone
The thread doesn't move. Everything else does.
Apple delivers iMessage to every device signed in to your Apple ID — independently, not as a forward. So the conversation genuinely lives on your iPhone and on your Mac at the same time. autoMessage reads from the Mac, which means the texts you already send by thumb show up in your dashboard, your CRM and your AI tools without you doing anything differently.
Inbound
A reply lands on your phone. It syncs, fires a webhook, and reaches your CRM or your agent — no copy-paste, no screenshots.
Outbound
An API call, a CSV, or an AI agent queues the message. It sends from your number, into the thread your contact already has with you.
Either device
Answer from your phone on the road or from the dashboard at your desk. It's one conversation, not two.
Pick up your phone mid-conversation and keep typing.
Try that with a number someone rented you. Hosted platforms send from an Apple ID in their rack — there's no phone in your pocket to continue on, and your existing threads aren't there. See how this plays out in real estate →
Not just plain text
Group chats, tapbacks, attachments, voice notes.
A thumbs-up is an answer. A threaded reply is answering something specific. An unsent message is one your CRM should stop showing. autoMessage syncs what Messages actually stores, so your automation reads the conversation instead of a stripped-down transcript — and you can send straight into a group thread you are already in.
- Group chats
- Tapbacks
- Attachments & stickers
- Voice notes
- Threaded replies
- Edits & unsends
- Read receipts
- SMS & RCS
Why it costs $59 and not $150
The same stack. You just own it.
Most platforms make you choose: keep control, or get automation. autoMessage gives you both.
A hosted iMessage platform is two products on one invoice — the automation infrastructure, and a device with an Apple ID sitting in a farm. The infrastructure is what you came for. The hardware is what makes it $150 a line.
autoMessage is the infrastructure on its own: the Mac connector, the hosted MCP server, the REST API, webhooks, the dashboard, the deliverability panel — installed on the Mac already under your desk, signed in to the Apple ID you already use.
The hardware was never the product.
Your throttle. Scale at your own pace.
You set your own send limit. It lives in Settings — raise it, lower it, or clear it whenever you like. It counts only cold outreach, so conversations that have already replied to you always go through, and hitting it fails nothing: messages queue and send themselves as the window rolls forward.
Everywhere else that number is set for you — most often capped near 50 new conversations a day. That figure isn't Apple's law — it's what a freshly provisioned Apple ID in a farm can safely do. Yours has history, real two-way traffic, and years of normal use behind it. Different account, different headroom.
Apple still enforces its own limits, and they tighten on a number that reads as bulk outreach rather than conversation. Ramp up gradually and keep an eye on your reply rate — the deliverability panel flags trouble early. Running serious volume is what Enterprise is for: it spreads sending across multiple numbers.
One price. Everything included.
No per-message fees. No setup fees. No annual contracts.
Need multiple lines or a completely managed service? Talk to the team.
How autoMessage compares
Public pricing from each vendor's site as of October 2026. We are the only iMessage platform with a native MCP server, and the only one that runs on hardware you already own — so there's no setup fee, and nothing of yours held by us.
| autoMessage | Tuco | Sendblue | Linq | Zernio | |
|---|---|---|---|---|---|
| Starting price | $59 per month | From $149 per month + $335 setup | $100 per month | ~$167 per month + $500 setup (annual only) | $200 per sender/month, non-refundable once activated |
| Free trial | 14-day free trial | No trial | No trial | No trial | No trial on iMessage |
| Native MCP server | Yes | No | No | No | Yes |
| Who holds the device | You | Vendor | Vendor | Vendor | Vendor |
| Send limit | You set it adjustable any time, in Settings | 50 new conversations/day per line, vendor-enforced | 50 new contacts/day per line; 15/hour, max 6 messages before a reply | 50 new conversations/day hard cap, per line | 1,000 new conversations/day the highest published ceiling — but a new sender is paced from 2/day to 50 over three weeks first |
FAQ
Do I need a dedicated Mac?+
No — but the Mac app has to be running for messages to send. Most customers run it on their daily-driver Mac, or on an older Apple computer they already had sitting around. Outbound messages queue when the Mac is offline and send the moment it wakes up.
What happens if I turn my Mac off?+
Nothing is lost in either direction. Outbound messages sit in the queue and send themselves when the Mac comes back — you do not have to re-send anything. Inbound is handled by Apple, not by us: iMessage is delivered to every device signed in to your Apple ID independently, so replies still arrive on your iPhone while the Mac is off, and the Mac catches up on everything it missed the moment it wakes. Close the lid for the weekend and it sorts itself out on Monday.
Can I still use my Mac normally?+
Yes. autoMessage runs in the background as a menu bar app — you keep using your computer exactly as before. Two things to know: Messages.app needs to be running, since that is what actually sends, and autoMessage keeps your Mac from sleeping while it is active so queued messages can go out.
Can it text Android phones (green bubbles)?+
Yes, through Apple's own Text Message Forwarding. Turn it on once on your iPhone — Settings → Apps → Messages → Text Message Forwarding → enable your Mac. Your iPhone only has to be switched on and online; it does not need to be anywhere near the Mac. Messages to other Apple users need nothing extra. Without forwarding, sends to Android numbers fail and their replies never reach your Mac.
How many messages can I send per day?+
You set it. The send limit lives in your Settings and you can raise, lower or clear it at any time — it is not something we decide for you. The real ceiling is Apple's, and it is not a fixed number: it scales with your account's history, so a long-standing Apple ID with real conversation traffic has more headroom than a brand-new one. Start conservative and scale gradually.
Which AI clients work with autoMessage?+
Claude Desktop, Claude Code, Cursor, ChatGPT Desktop, Cline, Codex, n8n, and any client that speaks stdio or Streamable HTTP MCP. If it can call an MCP tool, it can text.
Will Apple ban my account for using this?+
It is your Apple ID on your Mac, and the connector is engineered so the traffic reads as the texting you already do. Several independent safeguards run at once: an adaptive pacing layer that spaces every message on a randomised, load-aware interval rather than a fixed one — applied to replies as well as new outreach — plus a sliding-window burst detector that stands the connector down on its own when activity spikes, and resumes it automatically. On top of that you get a new-conversation ceiling you control, set to 50 per rolling 24 hours by default and adjustable or removable in Settings; anything past it is queued and drains as capacity frees, never rejected. Opt-outs are enforced for you at both the connector and the API, and no message is ever sent twice — every send is reconciled against a dispatch record first, including the awkward case where Messages is slow to confirm something it already sent. None of this is a guarantee, because the limits are Apple's and Apple does not publish them. What it does is keep the shape of your traffic ordinary: real conversation from an established account, not a burst from a number created last week.
Send blue bubbles now.
Your Mac. Your number. Your AI. $59/mo, 14 days free.