# Banger [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/bangermail/banger-plugin  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/banger-3

## Description
All your company email, operated by agents and reviewed by you.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "banger": {
    "url": "https://api.bangermail.com/mcp"
  }
}
```

## Documentation

## What the Banger MCP server does

Banger MCP server gives compatible agent hosts access to BangerMail’s company-email workflows. Its accompanying skill explains how to onboard a workspace, configure a company domain safely, turn business context into a reviewable email growth plan, and work with Mailboxes, Journeys, Broadcast, Product email, Approvals, and Logs.

The service is intended for agent-assisted email operations rather than local email processing. Agents can prepare and operate supported email workflows, while people review actions according to the workspace’s approval settings. The repository describes governed actions such as sending, launching a Broadcast, and activating a Journey as subject to those policies.

## How it works

The plugin points an agent host to BangerMail’s hosted MCP endpoint at `https://api.bangermail.com/mcp`. Communication uses Streamable HTTP. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, so the host opens Banger’s authorization page on first use. The user signs in, selects a workspace, and approves the requested scope set.

Authentication is represented by a per-workspace OAuth grant issued to the agent. Grants can be revoked from the Banger app. The agent does not receive credentials through chat, and governed operations cannot bypass a required workspace approval.

## Setup and configuration

Install the plugin through a supported host when a marketplace or plugin directory entry is available. Claude Code can add the Banger marketplace and install the plugin; Grok Build and Grok Bot can install the repository with their plugin command; Codex can install Banger from its plugin directory or add the remote MCP URL directly; and Cursor can install it from the Cursor Marketplace.

Other MCP clients can connect to the same remote endpoint using Streamable HTTP and OAuth. The repository specifically mentions Cline, Docker MCP Toolkit, OpenClaw, Hermes, and other MCP clients. On first use, complete authorization in the browser and choose the relevant workspace. No local process, shell command, hook, or machine-side service is required for operation.

## Tools and capabilities

The Banger MCP server supports access to these documented operational areas:

- Mailboxes
- Journeys
- Broadcast
- Product email
- Approvals
- Logs

The shared `operate-company-email` skill provides procedural guidance for workspace onboarding, company-domain configuration, reviewable email growth planning, and evidence-based operation of those areas. The repository does not list individual MCP tool names or their parameter schemas, so tool-level behavior should be confirmed in the connected service.

## Limitations and notes

Banger is a hosted service: the plugin communicates with `api.bangermail.com` and its OAuth and discovery paths under `/oauth/*` and `/.well-known/*`. Nothing runs locally. Access depends on authorization for a workspace and the scopes approved during sign-in.

The repository identifies the software as proprietary and directs users to BangerMail’s terms for hosted-service use. It does not document local credentials, environment variables, self-hosting, or offline operation. Approval behavior is controlled by workspace policy, and required approvals remain in force for governed actions.

_Full upstream README: https://allmcps.com/mcp/banger-3/readme_