Why Tuco's MCP Server Is the Only Way to Control iMessage from AI Agents
iMessage automation that actually reaches your leads
Outbound iMessages from your stack—no A2P 10DLC limits, no spam filters. Integrate with your CRM or any API.
Why Tuco's MCP Server Is the Only Way to Control iMessage from AI Agents
If you use Claude Desktop, Cursor, or Windsurf to run your workflow, you already know the power of MCP (Model Context Protocol). It lets AI agents call external tools using natural language. You say what you want, and the agent handles the API calls.
The problem: no iMessage automation platform besides Tuco supports MCP.
What Competitors Offer (and Don't)
Linq Blue, Sendblue, and Blooio each provide their own way to interact with iMessage campaigns. Dashboards, APIs, CRM integrations. These work fine when a human is driving.
But none of them expose an MCP server. That means if you want an AI agent to check your sending line health, review replies, or send a follow-up, you have to leave your AI tool, open a separate dashboard, and do it manually.
| Feature | Tuco | Linq Blue | Sendblue | Blooio |
|---|---|---|---|---|
| MCP server for AI agents | Yes | No | No | No |
| Natural language iMessage control | Yes | No | No | No |
| Works with Claude Desktop | Yes | No | No | No |
| Works with Cursor / Windsurf | Yes | No | No | No |
| REST API | Yes | Yes | Yes | Yes |
| Dashboard | Yes | Yes | Yes | Yes |
This is not a knock on those platforms. MCP is a newer standard, and most tools haven't adopted it yet. But if AI agents are part of your workflow, Tuco is the only option that meets you where you already work.
CRM to iMessage in minutes
Send from your existing tools. No 10DLC, no content hashing. Better deliverability for iOS.
What MCP Enables
With the Tuco MCP server installed, your AI agent can manage your entire iMessage operation through conversation. No context switching, no tab juggling.
Here is a real example: a sales manager opens Claude Desktop in the morning and says:
"Check my line health, show me any unread replies from yesterday, and send a follow-up to +12125551234 saying 'Hey — just circling back on our conversation. Still interested in a quick call this week?'"
Claude handles all three tasks in sequence — calling lines-health, check-replies, and send-imessage — and confirms each action.
No dashboard opened. No API docs referenced. Just a conversation.
90 Tools Available via MCP
The current published package exposes 90 live tools across campaigns, inbox actions, Knowledge Base replies, leads, messaging, CRM sync, workspace config, line health, and dormant lead reactivation.
Who This Is For
The MCP server is not for everyone. It is specifically useful if you:
- Already use Claude Desktop, Cursor, or Windsurf as part of your daily workflow
- Manage iMessage campaigns and want to reduce dashboard time
- Want to build AI-powered sales workflows that include iMessage as a channel
- Are a developer building agent-based automations and need iMessage as a tool
If you run your outreach from a CRM and never touch an AI agent, the MCP server is not going to change your workflow. The REST API or native integrations are a better fit.
Setup Takes 2 Minutes
Add this to your Claude Desktop config:
{
"mcpServers": {
"tuco": {
"command": "npx",
"args": ["tuco-mcp"],
"env": {
"TUCO_API_KEY": "tuco_your_api_key_here"
}
}
}
}
Get your API key from app.tuco.ai/api-keys. The same server works with Cursor, Windsurf, and any other MCP-compatible client.
Get Started
Full documentation and source: tuco.ai/mcp
Published package: npmjs.com/package/tuco-mcp
Questions? support@tuco.ai
