Stumpy
Wire always-on AI agents into Slack, Telegram, SMS, or email so your product can reply and act without you at the keyboard.
Overview
Stumpy is an MCP server for the Build phase that connects persistent AI agents to Slack, Telegram, SMS, and email via remote HTTP/SSE endpoints.
What is this MCP server?
- Remote MCP over streamable HTTP and SSE at stumpy.ai endpoints
- Agents scoped to Slack, Telegram, SMS, and email channels
- Designed for continuous operation rather than single chat sessions
- Stumpy.ai website and v1.0.0 server manifest for Claude/Cursor registration
- 2 remote MCP endpoints (streamable HTTP + SSE)
- 4 channel families listed: Slack, Telegram, SMS, email
- Server version 1.0.0 in catalog manifest
What problem does it solve?
Solo builders cannot keep an agent online in customer inboxes and team chat without building and maintaining their own messaging bridge.
Who is it for?
Indie SaaS or agent products that need 24/7 replies on Slack, Telegram, SMS, or email with MCP-native tooling.
Skip if: Teams that only need in-IDE coding help with no outbound messaging or no desire to run hosted channel agents.
What do I get? / Deliverables
After registering Stumpy in your agent client, your agent can run continuously on the channels you configure instead of only inside a local IDE session.
- Registered remote Stumpy MCP connection in your agent
- Persistent agent presence on chosen messaging channels
- Ongoing message handling without a custom gateway you maintain
Recommended MCP Servers
Journey fit
Persistent channel agents are built and configured before you ship customer-facing automation—not a one-off research or launch-only task. Agent-tooling is where you connect MCP-capable models to real messaging surfaces and keep them running 24/7.
How it compares
Hosted channel-agent MCP bridge, not a local repo skill or generic web scraper.
Common Questions / FAQ
Who is Stumpy for?
Solo and small teams shipping agent-powered products who want Slack, Telegram, SMS, or email handled by a persistent MCP-connected agent.
When should I use Stumpy?
Use it during Build when you are wiring agent-tooling and need production-grade, always-on messaging instead of manual copy-paste from a chat UI.
How do I add Stumpy to my agent?
Add the remote MCP server from the manifest (streamable HTTP at https://stumpy.ai/mcp/message or SSE at https://stumpy.ai/mcp/sse) in Claude Code, Cursor, or another MCP-compatible client, then configure your agent and channel credentials per Stumpy’s docs.