pumble-mcp
Allows AI agents to interact with the Pumble messaging platform via HTTP transport, enabling integration with n8n workflows through the MCP server's streamable HTTP endpoint.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@pumble-mcpsend a message to #general saying 'Hello everyone'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A standalone MCP server that gives AI agents complete access to the Pumble messaging platform. Built on the official Pumble SDK and the Model Context Protocol.
Getting Started · Tools · Real-Time Events · Architecture · Configuration · Development
Why pumble-mcp?
The existing Pumble MCP server wraps ~8 API endpoints with API-key auth. It can't touch files, receive events, manage channels, search messages, or schedule anything.
pumble-mcp exposes the entire platform — 33 tools across messaging, files, channels, users, search, scheduling, and real-time events — using OAuth2 and the full Pumble SDK for capabilities the REST API alone cannot provide.
Capability | Existing MCP | pumble-mcp |
Messages (send, read, edit, delete, threads) | Partial | Full |
File operations (upload, download, list) | — | SDK-exclusive |
Real-time events (subscribe, poll) | — | WebSocket |
Channel management (create, add/remove members) | — | Full |
Search with text/channel/user/date filters | — | Full |
Scheduled messages (create, edit, cancel) | — | Full |
User status and groups | — | Full |
HTTP transport for N8N / webhooks | — | Streamable HTTP |
Auth model | API key | OAuth2 |
Total tools | ~8 | 33 |
Related MCP server: CustomGPT MCP Server
Getting Started
Prerequisites
Node.js 22+ (LTS)
A Pumble workspace where you have admin access
1. Clone and install
git clone https://github.com/nitindermohan/pumble-mcp.git
cd pumble-mcp
npm install2. Register a Pumble app
npx pumble-cli login # Authenticate with your Pumble account
npx pumble-cli create # Register a new bot appThis creates .pumbleapprc with your app credentials (APP_ID, APP_KEY, CLIENT_SECRET, SIGNING_SECRET).
3. Configure environment
cp .env.example .envFill in the credentials from .pumbleapprc:
PUMBLE_APP_ID=your_app_id
PUMBLE_APP_KEY=your_app_key
PUMBLE_APP_CLIENT_SECRET=your_client_secret
PUMBLE_APP_SIGNING_SECRET=your_signing_secret4. Authorize and register events
Run once via pumble-cli to authorize the bot in your workspace and push event subscriptions to Pumble's platform:
npx pumble-cliWait for Websocket connected and App is updated, then Ctrl+C.
5. Build and run
npm run build
node dist/index.js6. Connect to your AI client
Add to .mcp.json in your project root:
{
"mcpServers": {
"pumble": {
"command": "node",
"args": ["dist/index.js"],
"cwd": "/path/to/pumble-mcp"
}
}
}Add to claude_desktop_config.json:
{
"mcpServers": {
"pumble": {
"command": "node",
"args": ["/absolute/path/to/pumble-mcp/dist/index.js"],
"cwd": "/absolute/path/to/pumble-mcp"
}
}
}Set MCP_TRANSPORT=http (or both) in .env, optionally set MCP_BEARER_TOKEN, then point N8N's HTTP Request node at:
POST http://localhost:3456/mcp
Authorization: Bearer YOUR_TOKEN🔧 Tools
Messaging — Read, write, and manage messages across channels and threads
Tool | Description |
| Send a message to a channel. Accepts |
| Reply to a specific message in a thread. |
| List recent messages in a channel with cursor-based pagination. |
| Fetch a single message by its timestamp ID. |
| Fetch all replies in a message thread. |
| Edit a message the bot previously sent. |
| Delete a message the bot previously sent. |
Direct Messages — Private conversations with individuals or groups
Tool | Description |
| Send a direct message to a user. Accepts email address or user ID. |
| Send a group DM to multiple users at once. |
Channels — Create and manage workspace channels
Tool | Description |
| List all channels the bot belongs to, with pagination. |
| Get channel details by |
| Create a new PUBLIC or PRIVATE channel. |
| Add one or more users to a channel. |
| Remove a user from a channel. |
Users — Workspace user information and bot identity
Tool | Description |
| List all users in the workspace with roles and status. |
| Get the bot's own user ID, display name, and workspace info. |
| List user groups and their members. |
| Set the bot's custom status with emoji, text, and optional expiration. |
Reactions — Emoji reactions on messages
Tool | Description |
| Add an emoji reaction (e.g. |
| Remove a previously added emoji reaction. |
Files — Upload, download, and browse files (SDK-exclusive)
Tool | Description |
| Upload a file (base64-encoded) to a channel with an optional message. |
| Download a file by URL and return its base64 content. |
| List files shared in a channel. |
Note: File operations are only available through the Pumble SDK with OAuth2 auth. The REST API alone does not expose file endpoints.
Search — Find messages across the workspace
Tool | Description |
| Full-text search with filters for channel, user, date range, and pagination. |
Scheduled Messages — Send messages at a future time
Tool | Description |
| Schedule a message for future delivery to any channel. |
| List all pending scheduled messages. |
| Edit the content or timing of a pending scheduled message. |
| Cancel a scheduled message before it sends. |
Real-Time Events — Subscribe and poll for live workspace activity
Tool | Description |
| Subscribe to one or more event types. Returns a subscription ID for polling. |
| Poll for events buffered since the last poll for a given subscription. |
| List all active event subscriptions with their types and cursor positions. |
| Remove a subscription and stop buffering its events. |
System
Tool | Description |
| Check server version, auth status, workspace name, and connection health. |
📡 Real-Time Events
pumble-mcp connects to Pumble via socket mode WebSocket and buffers incoming events in an in-memory ring buffer (1000 events, oldest evicted first). AI agents subscribe to event types and poll for new events at their own pace — no push endpoint or public URL required.
AI Agent pumble-mcp Pumble
│ │ │
│── subscribe(NEW_MESSAGE) ─▶│ │
│◀── subscription_id ───────│ │
│ │◀── WebSocket: NEW_MESSAGE ──│
│ │ (buffered in EventStore) │
│── poll(subscription_id) ──▶│ │
│◀── [event1, event2] ──────│ │Supported event types:
Event | Triggered when... |
| A message is posted in any channel the bot belongs to |
| A message is edited |
| Someone adds an emoji reaction to a message |
| A new channel is created in the workspace |
| The bot app is uninstalled from the workspace |
| A user revokes the bot's authorization |
| A new user joins the workspace |
Example flow:
// 1. Subscribe to events
pumble_subscribe_events({ event_types: ["NEW_MESSAGE", "REACTION_ADDED"] })
// → { subscription_id: "sub_a1b2c3d4", event_types: [...] }
// 2. Poll periodically
pumble_poll_events({ subscription_id: "sub_a1b2c3d4" })
// → { events: [{ eventType: "NEW_MESSAGE", payload: {...}, ... }], count: 3 }
// 3. Unsubscribe when done
pumble_unsubscribe_events({ subscription_id: "sub_a1b2c3d4" })
// → { unsubscribed: true }Architecture
┌──────────────────────────────────────────────┐
│ pumble-mcp │
│ │
Claude/CLI ──stdio──▶ McpServer ──▶ 33 Tools ──▶ PumbleClient ──▶── Pumble API
│ │ │ │
N8N/HTTP ───http──▶ McpServer EventStore ◀── SDK WebSocket ◀─── Pumble Events
│ (ring buffer) │
└──────────────────────────────────────────────┘Key design decisions:
Dual transport — stdio for Claude Desktop/Code, Streamable HTTP for N8N and remote consumers. Same 33 tools on both.
EventStore singleton — One ring buffer shared across all transports. Subscribe on stdio, poll from HTTP — it just works.
Socket mode — The Pumble SDK handles WebSocket connection, ping/pong keepalive, message ack, and automatic reconnection. No public URL or tunnel needed.
stderr-only logging — stdout is reserved exclusively for MCP JSON-RPC. The Pumble SDK's internal
console.logcalls are redirected to stderr at process start.OAuth2 with token mutex — Concurrent API calls serialize through a mutex to prevent race conditions on single-use refresh tokens.
Customizing the Bot Identity
Edit manifest.json to change how the bot appears in your Pumble workspace:
{
"name": "my-custom-bot",
"displayName": "My Custom Bot",
"botTitle": "Team Assistant"
}Then sync to Pumble:
npx pumble-cli # Pushes manifest changes to Pumble
# Wait for "App is updated", then Ctrl+CConfiguration
Environment Variables
Variable | Required | Default | Description |
| Yes | — | App ID from |
| Yes | — | App key for WebSocket authentication |
| Yes | — | OAuth2 client secret |
| Yes | — | Request signature verification secret |
| No |
| Path to OAuth2 token storage |
| No |
| Transport mode: |
| No |
| Port for HTTP transport |
| No | — | Bearer token for HTTP transport auth (strongly recommended) |
| No |
| Logging verbosity: |
Required Bot Scopes
These scopes are configured in manifest.json and registered during app creation:
messages:read messages:write messages:edit messages:delete
channels:list channels:read channels:write
users:list user:read
reaction:read reaction:write
workspace:read files:write attachments:write status:writeDevelopment
npm run dev # Run with tsx (hot reload)
npm run build # Compile TypeScript
npm test # Run all 175 tests
npm run test:watch # Watch mode
npm run test:coverage # Code coverage report
npm run typecheck # Type check without emittingTesting
Suite | Tests | Coverage |
Unit | 39 | EventStore, event listeners, auth, config, logger |
Integration | 128 | All 33 tools via in-process MCP server + InMemoryTransport |
Live | 8 | End-to-end against a real Pumble workspace |
npm test # Unit + integration (no network)
npx tsx tests/live/run-live-tests.ts # Live tests (requires credentials)Project Structure
src/
index.ts Entry point — boot sequence, console.log redirect
server.ts MCP server setup (stdio + Streamable HTTP transports)
config.ts Environment validation with Zod schemas
logger.ts stderr-only logger (stdout reserved for MCP JSON-RPC)
main.ts pumble-cli entry point for event registration
pumble/
auth.ts OAuth2 setup, token mutex, SDK event handler wiring
client.ts PumbleClient — unified wrapper for all SDK operations
resolvers.ts Smart resolution: #channel-name → ID, email → user ID
events/
event-store.ts Ring buffer (1000 capacity) with subscription-cursor polling
event-listeners.ts Bridges SDK event callbacks → EventStore.push()
tools/
index.ts Tool registration hub (routes to all modules below)
health.ts pumble_health_check
channels.ts 5 channel management tools
users.ts 4 user and bot identity tools
messages.ts 5 message read tools
messages-mutate.ts 2 message write tools (edit, delete)
reactions.ts 2 reaction tools
dms.ts 2 direct message tools
files.ts 3 file operation tools (SDK-exclusive)
search.ts 1 search tool with multi-filter support
scheduled.ts 4 scheduled message tools
events.ts 4 real-time event subscription tools
tests/
setup.ts Mock PumbleClient and EventStore factories
unit/ Pure logic tests — no network, no SDK
integration/ Full MCP pipeline tests via InMemoryTransport
live/ Real Pumble workspace end-to-end testsTech Stack
Component | Technology | Version |
Runtime | Node.js | 22 LTS |
Language | TypeScript | 5.9 |
MCP Protocol |
| 1.29.x |
Pumble Platform |
| 1.1.x |
HTTP Transport | Express + | 4.x |
Schema Validation | Zod | 4.x |
Testing | Vitest | 4.x |
Auth | OAuth2 via | — |
Disclaimer
This project was largely vibe-coded with Claude Code (Anthropic's AI coding agent). The entire development lifecycle — architecture, implementation, testing, debugging, and documentation — was driven through conversational AI-assisted development. All code was reviewed, tested (175 automated tests), and validated against a live Pumble workspace.
License
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- 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/nitindermohan/pumble-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server