mcpbeat Sign in

Call Me MCP Server

by getcallme Your server? Claim it
answering

Call Me is answering right now. Last checked 10 min ago.

Calls your phone when an AI task finishes or is blocked — hear it, say what's next.

Uptime history 91 days of history · worst day 99%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
329 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Call Me every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add call-me --transport http https://getcallme.app/mcp
Settings → Connectors → Add custom connector, then paste this address
https://getcallme.app/mcp
~/.codex/config.toml
[mcp_servers.call-me]
url = "https://getcallme.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "call-me": {
      "url": "https://getcallme.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "call-me": {
      "type": "http",
      "url": "https://getcallme.app/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://getcallme.app/mcp streamable-http sign-in 251 ms 10 min ago

Alternatives to Call Me

same job, measured the same way
CG
by callcg

A phone for your AI: CG rings or texts you when a job is done, and calls businesses for you.

answering
Final Check — A human checks your AI's work
by latentdatabank

A real person in Japan checks your AI's work and does what AI can't: phone calls, on-site photos.

answering
T
Twring
by twring

Your AI rings your phone or messages you on Twring when it needs you, and reads your reply.

answering
Heads-up
by abhishek207

Spoken voice alerts on Mac, Linux and Windows when your coding agent finishes a task or needs you.

670 installs/wk local only
MCP Voice Summary
by eduplopez

Reads a summary out loud when an AI coding task finishes. Offline or neural voices.

144 installs/wk local only
N
Next.js Architecture MCP
by hasimkilic

Indexes your Next.js project so an agent finds the file that owns a task in one call.

71 installs/wk local only
Cachejay
by cachejay

Memory for your AI: what you saw on screen, said in calls and worked on, searchable by agents.

answering
Kato
by manduks

What was said, shown and promised on your client's calls, filed by client. Needs the Kato app.

local only

Call Me — questions

Answers built from our own checks of this server.

Why is there no tool list for Call Me?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Call Me working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 329 ms. The bar chart above shows every period we have measured.
How do I connect Call Me?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Call Me?
No API key is involved. Call Me answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Call Me?
It answers our handshake in 329 ms on average, which is faster than 43% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.