EchoLoopMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ECHOLOOP_CHANNEL | No | Force channel selection: 'telegram' or 'discord'. Default: auto. | auto |
| ECHOLOOP_TIMEOUT | No | Default timeout in seconds for the 'ask' tool. Default: 240. | 240 |
| TELEGRAM_CHAT_ID | No | Chat ID for the Telegram channel. | |
| DISCORD_BOT_TOKEN | No | Discord bot token for the Discord channel. | |
| DISCORD_CHANNEL_ID | No | Channel ID for the Discord channel. | |
| TELEGRAM_BOT_TOKEN | No | Telegram bot token for the Telegram channel. | |
| DISCORD_WEBHOOK_URL | No | Discord webhook URL for the Discord webhook channel (notify only, ask returns error). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notifyA | Push a message to the user's phone (Telegram or Discord) and return immediately without waiting for an answer. Use it when a long task finishes, when a build or test run ends, or to report something the user should see while away from the terminal. |
| askA | Push a message to the user's phone and then block until they reply, returning their reply text. Use it instead of ending your turn when the user is away from the terminal and you need their next instruction or a decision. Treat the returned text as the user's next instruction. Replies sent before this call are ignored. |
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
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/aidevksh/EchoLoopMCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server