pumble-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUMBLE_API_KEY | Yes | Your Pumble API key for accessing the workspace |
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 |
|---|---|
| send_message_via_channel_name_or_idB | Send a message to a public or private channel. Resolves channel names natively. |
| list_messages_via_name_or_idB | List messages from a channel or direct message (DM) conversation. Resolves names natively. |
| edit_messageC | Edit a previously sent message by ID. |
| delete_messageB | Delete a message by ID in a channel. Destructive; requires confirmation code. |
| get_message_via_idC | Get full details of a specific message by ID and channel name or ID. |
| send_dm_via_name_email_or_idB | Send a 1-on-1 direct message. Resolves user names/emails natively. |
| send_group_dm_via_names_emails_or_idsC | Send a group direct message to multiple users. Resolves names/emails natively. |
| get_my_infoB | Get profile information of the authenticated user/bot. |
| list_user_groupsB | List workspace user groups. |
| update_my_custom_statusC | Update the custom status of the authenticated user. |
| search_messagesA | Search message history by text query (~15s indexing delay). Do not use for user/channel ID lookups. |
| reply_message_via_channel_name_or_idB | Reply to a message in a channel or DM thread using parent messageId. Resolves names natively. |
| list_thread_replies_via_channel_name_or_idC | List all replies in a message thread. Resolves names natively. |
| add_reactionB | Add an emoji reaction to a message by ID. |
| remove_reactionC | Remove an emoji reaction from a message by ID. |
| list_channels_only_when_user_callsA | List all visible channels. Use ONLY when the caller explicitly asks to view the channel directory. |
| get_channel_detail_via_channel_name_or_idA | Get details of a specific channel. Use ONLY when the caller explicitly requests channel metadata. |
| create_channelB | Create a new public or private channel. |
| add_users_to_channel_via_name_or_idC | Add users to a channel by names or emails. Resolves entities natively. |
| remove_user_from_channel_via_name_or_idB | Remove a user from a channel. Destructive; requires confirmation code. |
| list_users_not_for_id_lookupA | List all workspace users. Use ONLY when the caller explicitly asks to view the user directory. |
| list_scheduled_messagesB | List scheduled messages, optionally filtered by channel or user. |
| create_scheduled_message_via_name_or_idB | Schedule a message for future delivery to a channel or user. |
| edit_scheduled_message_via_name_or_idC | Edit text, target, or send time of a scheduled message. |
| delete_scheduled_message_via_name_or_idA | Delete a scheduled message before delivery. Destructive; requires confirmation code. |
| get_scheduled_message_via_name_or_idB | Get details of a specific scheduled message by ID. |
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 26 tools
Tools mostly target distinct resource+action pairs (send vs reply vs schedule vs edit vs delete message, channel vs DM vs group DM, reactions, threads). Some names awkwardly embed usage guidance (list_channels_only_when_user_calls, list_users_not_for_id_lookup), but this actually reduces misselection. Minor overlap between send_message_via_channel_name_or_id and send_dm/send_group_dm, but descriptions clarify.
Most tools follow verb_noun but with inconsistent long suffixes (via_channel_name_or_id, via_name_email_or_id, via_names_emails_or_ids, via_name_or_id), while others (edit_message, delete_message, add_reaction) drop the suffix entirely. Two tools embed conditional instructions in the name (only_when_user_calls, not_for_id_lookup), breaking the pattern. Still readable but mixed conventions.
At 26 tools it sits just over the heavy threshold, and the surface spans messages, channels, DMs, threads, reactions, scheduled messages, users, groups, and status. Each tool does map to a distinct operation, but the set feels large and could be consolidated (e.g. the via_name_or_id variants).
Strong coverage of the chat domain: full message lifecycle, threads, reactions, DMs/group DMs, channel create and membership management, and complete scheduled-message CRUD. Gaps remain (no channel delete/archive/update, no file/attachment handling, user groups are list-only), but core workflows are covered.