Pumble Mcp— agent skill

<div align="center">

<img src="image.png" alt="pumble-mcp — Full Pumble Platform Access for AI Agents" width="100%"/>

<br/>

A standalone MCP server that gives AI agents complete access to the Pumble messaging platform.<br/> Built on the official Pumble SDK and the Model Context Protocol.

Getting Started · Tools · Real-Time Events · Architecture · Configuration · Development

</div>

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.

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 install

2. Register a Pumble app

npx pumble-cli login     # Authenticate with your Pumble account
npx pumble-cli create    # Register a new bot app

This creates .pumbleapprc with your app credentials (APP_ID, APP_KEY, CLIENT_SECRET, SIGNING_SECRET).

3. Configure environment

cp .env.example .env

Fill 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_secret

4. 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-cli

Wait for Websocket connected and App is updated, then Ctrl+C.

5. Build and run

npm run build
node dist/index.js

6. Connect to your AI client

<details> <summary><strong>Claude Code</strong></summary>

Add to .mcp.json in your project root:

{
  "mcpServers": {
    "pumble": {
      "command": "node",
      "args": ["dist/index.js"],
      "cwd": "/path/to/pumble-mcp"
    }
  }
}

</details>

<details> <summary><strong>Claude Desktop</strong></summary>

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"
    }
  }
}

</details>

<details> <summary><strong>N8N (HTTP transport)</strong></summary>

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

</details>

🔧 Tools

Messaging — Read, write, and manage messages across channels and threads

Direct Messages — Private conversations with individuals or groups

Channels — Create and manage workspace channels

Users — Workspace user information and bot identity

Reactions — Emoji reactions on messages

Files — Upload, download, and browse files (SDK-exclusive)

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

Scheduled Messages — Send messages at a future time

Real-Time Events — Subscribe and poll for live workspace activity

System

📡 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:

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.log calls 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+C

Configuration

Environment Variables

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:write

Development

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 emitting

Testing

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 tests

Tech Stack

Disclaimer

This project was largely vibe-coded with [Claude Code](https://claude.ai/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

MIT