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 |
|---|---|
| pumble_send_messageA | Send a message to a Pumble channel, as your own user by default. |
| pumble_list_messagesB | List messages in a Pumble channel. |
| pumble_edit_messageB | Edit the text of an existing Pumble message. |
| pumble_list_channelsA | List all Pumble channels visible to the API key, including DMs (channelType DIRECT) and group DMs. Use the channel's id with pumble_list_messages to read a DM conversation. |
| pumble_send_dmA | Send a direct message to a person in Pumble, as your own user. Use pumble_list_users to find their userId/email first if unknown. |
| pumble_list_usersA | List all people in the Pumble workspace (id, name, email). Use this to resolve a person's userId for pumble_send_dm, or find their DM channelId via pumble_list_channels (channelType DIRECT) to read a conversation with pumble_list_messages. |
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 6 tools
Each tool targets a distinct action: edit, list channels, list messages, list users, send DM, send message. Descriptions clearly differentiate between sending to a channel vs a DM, and note how to find DM channel IDs. No ambiguity.
All tools follow a consistent 'pumble_verb_noun' pattern in snake_case (e.g., pumble_edit_message, pumble_list_channels), making the set predictable and easy to navigate.
With 6 tools, the server covers essential messaging operations (read, send, edit) for both channels and DMs, plus user listing. The count feels well-scoped without unnecessary duplication.
Core workflows are covered: reading and sending messages to channels and DMs, editing messages, and listing users. Minor gaps like delete message or thread support are acceptable for a succinct tool surface.