Beep Boop MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Node environment setting (e.g., 'development' for debug mode) | |
| BEEP_BOOP_LOG_LEVEL | No | Log level for debugging (e.g., 'debug') | |
| BEEP_BOOP_INGRESS_ENABLED | No | Enable or disable the ingress/listener system for capturing messages from Discord and Slack | |
| BEEP_BOOP_SLACK_APP_TOKEN | No | Slack app-level token (xapp-*) for Socket Mode integration | |
| BEEP_BOOP_SLACK_BOT_TOKEN | No | Slack bot token (xoxb-*) with proper scopes for bot integration | |
| BEEP_BOOP_INGRESS_PROVIDER | No | Platform provider for ingress system ('discord' or 'slack') | |
| BEEP_BOOP_MANAGE_GITIGNORE | No | Whether to automatically manage .gitignore entries for coordination files | true |
| BEEP_BOOP_DISCORD_BOT_TOKEN | No | Discord bot token for Discord integration | |
| BEEP_BOOP_DISCORD_API_TIMEOUT_MS | No | Individual Discord API call timeout in milliseconds | 30000 |
| BEEP_BOOP_INGRESS_HTTP_AUTH_TOKEN | No | Optional authentication token for HTTP API endpoints (recommended for security) | |
| BEEP_BOOP_DISCORD_API_RETRY_ATTEMPTS | No | Number of retry attempts for Discord API failures | 3 |
| BEEP_BOOP_CONVERSATION_TIMEOUT_MINUTES | No | How long to wait for user responses in minutes | 5 |
| BEEP_BOOP_CONVERSATION_POLL_INTERVAL_MS | No | How often to check for responses in milliseconds | 2000 |
| BEEP_BOOP_DISCORD_API_RETRY_BASE_DELAY_MS | No | Base retry delay with exponential backoff in milliseconds | 1000 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_beepA | Creates a beep file to signal that work is complete and the directory is cleared for new work. Use this when work is finished but no boop file exists. |
| update_boopA | Creates or updates a boop file to claim a directory for work. This signals that work is in progress and prevents other agents from working in the same directory. |
| end_workA | Atomically completes work by removing the boop file and creating a beep file. This signals that work is complete and clears the directory for new work. |
| check_statusA | Checks the current work coordination status of a directory by examining beep/boop files, provides guidance on next steps, and can automatically clean up stale boop files older than a specified threshold. |
| update_userC | Sends a follow-up update back to the platform (Slack/Discord) for a captured message. |
| initiate_conversationB | Proactively starts a new conversation on Discord or Slack. For Discord, creates a thread automatically. |
| check_listener_statusC | Checks the status and connectivity of the HTTP listener service used for tool delegation. |
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/thesammykins/beep_boop_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server