Skysay launch: agent-native telephony over MCP + llms.txt
At a glance
Skysay’s launch post positions agent-native telephony—real numbers, calls, SMS—as MCP tools described in llms.txt, with client recipes for Grok Bot and other assistants. Pattern for builders: expose billable / regulated actions as scoped MCP tools with read-only first, quotes before spend, and carrier-review gates per country. This workflow is listed under Grok-Bot, MCP, telephony, llms.txt, monetize.
xAI gives each account one @mail.grokbot.com inbox for signups and outreach; Shipmail’s MCP connector + webhook lets the same Grok Bot send/receive from your domain and start a Grok automation when new mail arrives—better for customers who distrust mail.grokbot.com.
Skysay’s hosted Streamable HTTP MCP (https://api.skysay.ai/mcp) lets Grok Bot check coverage, request numbers, place approved outbound calls through a hosted voice agent, and send SMS—OAuth/PKCE, separate call vs SMS approval, no local Twilio bridge. Start read-only with account_overview; outside US/CA/UK/MX outbound often needs carrier review first.
Marc Lou’s MailCheap exposes Streamable HTTP MCP at https://mailcheap.ai/mcp so ChatGPT, Claude and Grok Bot connect with OAuth (no key to copy); Claude Code, Codex and Cursor use a bearer API key. Agents can draft campaigns, send tests, schedule issues and read stats; schedule/send tools are marked destructive and ask before sending. Open-source / self-host option; pay only for SES-style sends vs beehiiv-class plans.
Official xAI guide: Share as Template packages instructions, skills, routines and first-party plugins into an anonymized blueprint (team or public link)—no secrets, custom code, MCP servers, logins or history. Installers get a fresh bot that must re-approve plugins; encode setup steps for API keys and custom MCP so others can reproduce the workflow.