watush-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WATUSH_CONFIG | No | Alternate path to config.yaml | |
| TELEGRAM_CHAT_ID | No | Your numeric Telegram ID (owner) for receiving messages and audit copies | |
| TELEGRAM_BOT_TOKEN | Yes | Telegram bot token from @BotFather | |
| TELEGRAM_RECIPIENTS | No | JSON array of recipients, each with name, chatId, and optional tags. Merged with config.yaml. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_telegram_messageA | Send a Telegram message to the user (yourself) or to a named/tagged person such as a partner, family member, or friend. Use whenever the user asks to be messaged, pinged, notified, texted, or alerted on Telegram, or to message someone like a partner or a named contact, or to deliver a result/reminder. Omit 'to' (or use 'me') to message the user themselves. The user (owner) always receives an audit copy of messages sent to other people. |
| list_recipientsA | List who can be messaged on Telegram: the owner (you) and configured recipients with their names and tags. Use this to map a phrase like 'my partner' to a valid 'to' value for send_telegram_message. Chat IDs are never returned. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikedelcastillo/watush-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server