Developer Platform
Build with REST. Operate with agents. Ship iMessage workflows that can be driven by code or by chat.
Use signed webhooks, reusable workflow tools, CRM sync, inbox actions, reactivation, and the published `tuco-mcp` package for Claude, Cursor, Windsurf, and other MCP clients.
Last updated:
90 MCP tools.
Campaigns, inbox, Knowledge Base, CRM sync, line health, AI credits, and reactivation are already exposed.
One npm package.
Install `tuco-mcp` once and use the same server across Claude, Cursor, Windsurf, and future MCP clients.
Real workflow coverage.
This is not a toy wrapper around send-message. It reaches campaigns, KB approvals, inbox work, and CRM-aware logic.
API + agent surface.
Use REST when code should drive. Use MCP when a person or AI should operate the workspace by chat.
Quick Start
The MCP layer is real, published, and already broad enough to operate your workspace like a product operator.
Platform
The point is not just sending one message. It is operating campaigns, inbox, CRM, and AI workflows from one developer surface.
REST API
Send messages, manage leads, retrieve replies, and work the platform with predictable HTTP calls.
Signed Webhooks
Receive sent, failed, fallback, reply, and opened events without polling or brittle status checks.
tuco-mcp
Let Claude, Cursor, or Windsurf run the workspace with natural language across 90 live tools.
Custom Tools
Build reusable API tools once, test them on a real lead, then reuse them inside campaigns and AI bots.
CRM Write-Back
Sync HubSpot and GoHighLevel, map owners and properties, and push the right updates back after the reply.
Reactivation
Scan dormant conversations, tune reactivation rules, and trigger the next AI motion from code or MCP.
Send an iMessage in 5 lines
One REST endpoint. Authenticate with a Bearer token. Get a message ID back. That's it.
No A2P 10DLC. No carrier surcharges. Webhook payloads are HMAC-signed — verify them like Stripe. Copy-paste build guide → · Full reference in the docs →
MCP Prompt Lab
Campaigns, KB approvals, inbox work, CRM sync, reactivation, and ops checks are already agent-friendly.
16 campaign tools
Create campaigns, preview paths, test steps, and pause live motions without leaving Claude or Cursor.
FAQ
Apple does not publish a public iMessage send API. The only Apple-sanctioned program is Messages for Business, which routes gray-bubble customer-support conversations and is not available for marketing or transactional sends. The practical "iMessage API" developers integrate against today is provided by third parties running real Apple hardware behind a clean HTTPS surface. Tuco AI exposes a REST endpoint at api.tuco.ai that accepts {to, body, lineId} and returns delivery status via signed webhooks — no Apple developer account, no A2P 10DLC, no carrier registration required.
Developers can send iMessages programmatically, create and tune campaigns, approve or auto-send KB replies, manage inbox workflows, sync CRMs, scan dormant leads, and control the whole workspace through API or MCP.
Yes. Tuco AI exposes a REST API any language can hit — Python, Node.js, Go, Ruby, PHP. There is no language-specific SDK requirement; the API is just signed HTTPS calls. See the code samples above for a Python `requests` example sending an iMessage in a few lines.
Yes. Node.js apps hit the same REST endpoints with `fetch` or `axios`. Webhooks are signed with HMAC so you can verify them in any Node middleware. The tuco-mcp package itself is published on npm and ships TypeScript definitions.
POST to https://api.tuco.ai/v1/messages with a JSON body of {to, body, lineId} and your API key in the Authorization header. Full curl snippet is in the code samples on this page and in the docs.
API keys are scoped per workspace and sent as Bearer tokens. Webhook payloads are signed with HMAC-SHA256; verify the signature against your endpoint secret before trusting the body. Standard pattern, no surprises.
Yes. TLS in transit, encrypted at rest, scoped API keys, signed webhooks, and audit logs on every workspace mutation. Tuco AI does not require A2P 10DLC because iMessage uses Apple’s network rather than US carriers, so you avoid the brand-vetting paperwork while keeping a clean compliance posture.
tuco-mcp is the published npm package for Tuco’s official MCP server. It lets Claude, Cursor, Windsurf, and other MCP clients control your Tuco workspace through natural language instead of custom glue code.
The current published package exposes 90 tools across campaigns, Knowledge Base, inbox, leads, messaging, CRM sync, line health, workspace config, and reactivation workflows.
Use the REST API when your app or backend needs deterministic integration. Use MCP when a human or AI agent should operate the workspace conversationally from Claude, Cursor, or another MCP client.
Pricing starts at $149/mo on the Starter plan (plus a $335 one-time setup) with full API access and no A2P 10DLC carrier surcharges. There is no per-API-call fee — you pay for the line and credits, not for each request. See /pricing for the full breakdown.
Yes. Subscribe to message.sent, message.failed, message.fallback, message.reply, message.reaction, message.opened, message.ai_draft, message.ai_draft_approved, and message.ai_draft_rejected webhook events. Payloads are signed; retries follow exponential backoff. Configure endpoints in the workspace settings or via the API.
The best developer surface is the one that fits both your backend and your operator workflow. Tuco gives you both.