by heyoncall
HeyOnCall sends automated phone notifications via a hosted paging service to alert on-call teams when long-running tasks
★ —
GitHub stars
Sends phone notifications through HeyOnCall's paging service to alert you when tasks complete or when you need to be notified.
HeyOnCall is an official MCP server published by heyoncall that provides AI assistants with tools and capabilities via the Model Context Protocol. HeyOnCall sends automated phone notifications via a hosted paging service to alert on-call teams when long-running tasks
You can install HeyOnCall in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server supports remote connections over HTTP, so no local installation is required.
MIT
HeyOnCall is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
HeyOnCall is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Useful MCP listing: HeyOnCall is the kind of server we cite when onboarding engineers to host + tool permissions.
HeyOnCall is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Strong directory entry: HeyOnCall surfaces stars and publisher context so we could sanity-check maintenance before adopting.
HeyOnCall has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We evaluated HeyOnCall against two servers with overlapping tools; this profile had the clearer scope statement.
According to our notes, HeyOnCall benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
HeyOnCall reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We wired HeyOnCall into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
According to our notes, HeyOnCall benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
showing 1-10 of 39
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
