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 | |
TDQS
Scored across 7 tools
Tools have overlapping purposes that could cause confusion, particularly around work coordination. For example, 'create_beep' and 'end_work' both handle work completion with beep files, and 'check_status' includes cleanup functionality that overlaps with 'end_work'. However, descriptions help clarify specific use cases, preventing complete misselection.
Most tools follow a consistent verb_noun pattern (e.g., 'check_status', 'create_beep', 'update_boop'), which aids predictability. Minor deviations exist with 'initiate_conversation' using 'initiate' instead of a more common verb like 'start', but overall naming is coherent and readable.
With 7 tools, the count is well-scoped for the server's dual purposes of work coordination and platform communication. Each tool appears to serve a distinct role, avoiding bloat while covering necessary operations like status checks, file management, and messaging.
The tool set covers core workflows for work coordination (initiate, update, complete, check) and platform communication (initiate, update), with no major gaps. A minor gap exists in lacking a tool to delete or manage stale beep files, but agents can work around this using existing cleanup in 'check_status'.