Categories › AI & Agents › Multi-agent, orchestration & workflows
Your AI rings your iPhone, speaks its question, and gets your spoken answer back as text.
Remote server: your requests and data go to callmemcp.com. Claude Code: claude mcp add --transport http call-me https://callmemcp.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
setup — Return first-setup instructions and clickable App Store and Google Play download links, for when you do not have the human's Call Me number call — Ring the human's phone (iPhone or Android), read `question` aloud word for word, and return what they say back as text. Waits up to ~30s. stpoll_result — Check on a call that came back "ringing", "in_call" or "playing". Waits up to ~25s for it to settle, then returns the same shape as `call`: play_audio — Bigger and longer audio goes here. Calls the human and plays a recording to them as a phone call: a podcast, a long narration you rendered, say — In a call whose result came back "open": true, speak `text` to the human and return what they answer, in the same shape as `call`. Only aftehang_up — End a call you placed. In an open conversation `goodbye` is spoken first; leave it empty to just hang up. A call that already ended reports text — Send a one-way text to the human's phone (a push notification, no ring). Use it for updates that need no answer, or as the fallback when a cwait_for_reply — Wait for the human to send something back to this session — texts and voicemail transcripts arrive here. Long-polls up to wait_s (max 30s); set_thread_title — Name this session's conversation thread on the human's phone (e.g. the project or task you are working on). Shown as the thread title in theNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.