
Call Me
com.callmemcpv1.0.0更新於 Oct 4, 2026
Your AI rings your iPhone, speaks its question, and gets your spoken answer back as text.
概覽
讓 AI 代理撥打你的 iPhone,朗讀問題或更新,並把你的口頭回答以文字回傳,或改為傳送推播訊息。
- 功能
- Call Me 在 AI 代理與你的手機之間搭橋:call 工具會撥打你的 iPhone、朗讀指定文字,並把你的口頭回答轉成文字回傳;text 則只送推播通知,不響鈴。搭配的工具可輪詢仍在響鈴的通話、接收回覆與語音留言,並為手機上的會話執行緒命名。它本身不做推理、也不進行對話,只負責傳遞。除了 MCP,還提供 ring 與 text 兩個 HTTP 端點做同樣的事。
- 適用情境
- 適合代理在你離開鍵盤時需要向你確認或回報的情境,例如開車、通勤或走路時,用口頭回答比打字方便。也適合長時間執行的任務在完成或需要核准時,透過電話通知你。
- 執行需求
- 遠端 streamable-HTTP 端點 API 金鑰或 OAuth。需要安裝 callme iPhone 應用程式並取得你的 10 位數 callme 號碼;託管用戶端無法讀取本機配對檔,必須另外提供該號碼。本機整合會讀取同一台電腦上寫入的配對檔。需要能連線至該服務的網路。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Call Me,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"call-me": {
"type": "http",
"url": "https://callmemcp.com/mcp"
}
}
}README
callme — your AI can call you
Your AI agents ring your actual iPhone, read you a question, an update or your day ahead, and get your spoken reply back as text — or just text you. Works from any AI that speaks MCP; nothing to install.
Call Me is not a voice assistant and holds no conversation of its own. Your agent does the thinking; Call Me only carries its question to your phone and your answer back, so you can keep it working while you drive, train or walk.
1. Get the app
callme on the App Store. No registration, no email. Open it, tap Agree & Continue, and it shows your personal callme number: 10 digits, and all an agent needs to reach you.
2. Connect your AI (MCP)
Pairing is stored locally in ~/.aiphone/config.json. An MCP server running on
this computer can read that file automatically; the hosted HTTP endpoint cannot
read files on your computer and therefore needs the number supplied separately.
One server, every MCP client — no API key, no OAuth:
Claude Code
opencode — add to opencode.json (or ~/.config/opencode/opencode.json):
Codex CLI — use the local paired MCP server
The local callme MCP server reads ~/.aiphone/config.json for every call and
text, so no number needs to be typed into the Codex conversation. Use its
identity tool to verify the paired phone.
Gemini CLI
or, for the MCP server alone:
Grok
In the Grok app: grok.com/connectors → New
Connector → Custom → https://callmemcp.com/mcp. In Grok Build:
Cline — add to Cline's MCP settings (MCP Servers → Configure; CLI:
~/.cline/data/settings/cline_mcp_settings.json). Full agent-readable steps are
in llms-install.md.
Cursor — add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
Or install the plugin in plugin/, which adds a skill telling the
agent when to call and when to text. It is a standard
Agent Plugin with a Cursor manifest, so any client
that loads Agent Plugins can use it too.
ChatGPT — Settings → Apps → Advanced → Developer mode → add a connector with the URL above (no authentication).
claude.ai — Settings → Connectors → Add custom connector → the URL above.
Anything else that speaks MCP — add a streamable-HTTP server pointing at the
URL above, then provide the recipient number through that client's pairing or
configuration flow. A hosted MCP connection cannot see this computer's
~/.aiphone/config.json.
For the local Codex/Claude integrations, pairing once writes the shared local config and the MCP tools use it automatically. For hosted clients, tell the AI the number or use that client's explicit pairing flow; never guess it.
Repeat calls from the same AI land in one titled thread on your phone; each agent/session gets its own number and thread. Blocking a thread in the app silences that sender for good.
3. Or just curl it
No MCP client, no plugin, no token. Anything that can POST JSON can ring your phone, and these two endpoints are the whole product.
Ring and wait for the spoken answer (blocks until you answer or it gives up):
status is one of completed, missed, declined, timeout, failed.
transcript is what you said, already turned into text.
Text only, no ring:
Returns {"ok":true,"message_id":42,"delivered":true}. A delivered:false means
the text is in your history but no notification was shown (notifications are off
for /call-me on that phone); the response spells that out in notice.
Anything else
Both responses hand back a session_token, and that is a real session: the same
caller can use the rest of the API with it, all landing in one thread on your
phone.
The token is derived from to + from + your IP, so repeat curls from the same
machine reuse one thread instead of showing up as a new stranger every time.
Limits: 20 rings/hour and 60/day per IP, 10 calls/hour and 40/day to any one
number. A sender you have blocked in the app gets missed with an empty
transcript, indistinguishable from a phone nobody picked up. On purpose.
4. Optional: Claude Code plugin
On Claude Code, the plugin adds what MCP alone can't: replies you send from
the phone land in the live session, and if Claude ends a turn with a
question parked on you, a Stop hook + answer waiter wake it up to call or
text you instead of going to sleep.
Then restart Claude Code and say "set up /call-me for me" — it does the rest.
5. Optional: DeepSeek Harness plugin
On DSH, dsh-plugin-call-me adds what MCP alone can't there either: a turn ending or a tool waiting for approval can ring your phone on its own, and because DSH lets a plugin wake an idle run, the answer you speak picks the run back up.
6. Optional: herdr plugin
herdr is a terminal workspace manager that watches every
pane and marks an agent blocked the moment it puts a real approval or question
on screen. herdr-plugin-call-me
turns that moment into a call — and then puts your spoken answer back into the
pane as the keypress the agent was waiting for. It works for whichever of herdr's
~20 supported agents happens to be in that pane, so it needs nothing from the
agent itself.
7. Optional: Omarchy plugin
The Omarchy setup panel lives in its own repository so the marketplace installs only the panel: radres/omarchy-plugin-call-me.
Remove with omarchy plugin remove radres.call-me. Details, requirements and
what the panel sends over the network are in that repository's README.
How it works
callcreates a VoIP call (LiveKit WebRTC — no real telephony); your iPhone rings through CallKit like a real call, TTS reads your text, your spoken reply is transcribed and returned to the agent.- Your number is a bearer capability: anyone who knows it can reach you, nobody who doesn't can. Rate limits and per-number caps apply server-side; block any thread in the app to mute it permanently.
來源:README.md,提交 142b955
工具
0版本歷史
1- v1.0.0最新Oct 4, 2026
