To send company email from Claude, add Banger as a custom connector and complete OAuth. Claude can then use Banger’s MCP tools to prepare email, operate company mailboxes, and check delivery status. Sends gated by workspace policy and all Journey activations require a person to decide an Approval in Banger’s web app.
Start with one company mailbox and one message you can inspect. After that works, you can ask Claude to help with a launch announcement, a welcome sequence, contacts, or the email setup for your new domain.
The connector to use
Use Add Banger to Claude to open Claude’s custom-connector dialog with Banger’s name and server URL filled in. The server is https://api.bangermail.com/mcp.
The link opens setup. Complete the connection and OAuth steps in Claude to authorize access. Check the Banger MCP guide if you need the server details or instructions for another MCP client.
Steps: prepare and send a test email
1. Authorize the intended workspace
During OAuth, review the workspace and scopes. Grant the permissions needed for the work you intend Claude to perform. If the first task is inspection, begin there before expanding into mailbox changes or sending.
Avoid putting credentials into a prompt. Use the authorization flow for the connection. Your product description, writing preferences, and message purpose belong in the conversation; secrets used to connect accounts belong in the relevant secure setup flow.
2. Ask Claude to inspect the sender
Start with: “Use Banger to find the mailbox for my product and inspect whether its domain is ready. Report the mailbox address and anything that prevents sending.” Confirm that the result names the company you intended.
On a fresh domain, there may still be DNS records to publish or verification to complete. Claude can help prepare and inspect that work through Banger. Follow the domain setup article if the first session begins before email is configured.
3. Give a bounded writing brief
Provide the recipient, message purpose, sender identity, and facts to include. For a first send, use an address you control. Specify which links are real and which names are examples so the assistant does not carry placeholders into the message.
Try: “Prepare a test email from my company mailbox to this address. Say that the product preview is ready and include only the preview URL I provide. Show me the subject, body, sender, and recipient before proceeding.”
If you ask Claude to rewrite the message, inspect the final version. Small revisions can change a date, a promise, or a call to action. A good draft is one you can verify against the product, not one that merely sounds polished.
4. Decide the Approval when policy requires it
Sends that workspace policy gates become Approvals. Open the proposal in the Banger web app and decide there. Claude can prepare the work and explain its status, but it cannot approve.
Check the sender and recipient before reading the copy. Then check links, product claims, and any sensitive details. The review should cover the actual operation, including its audience, rather than only whether the writing matches your tone.
A request for review in the conversation does not create a Banger Approval. Configure workspace policy for sends that must wait for your review. Our safe agent access guide explains the distinction between scopes, policy, and human approval.
5. Ask for evidence of the outcome
Have Claude inspect delivery status and logs after sending. If the message remains pending or was refused, ask for the reason and the appropriate next action. A tool request and a successful outcome are separate things.
Read the received test email too. Check the From name, the reply destination, the appearance of the body, and whether the destination links work. This small test gives you a reference before you involve actual subscribers.
Use Claude for more than a single draft
Banger gives Claude tools for company email setup and operation: domain records, mailboxes, product email, Broadcasts, Journeys, contacts and consent, signup forms, and delivery checks. Start by asking it to inventory what exists instead of assuming a new product has every resource ready.
For a launch Broadcast, provide confirmed subscribers and the announcement facts. For a Journey, ask it to prepare all steps and explain the audience and timing. Activating a Journey always requires a person’s Approval in Banger. The welcome-sequence walkthrough shows how to make that review manageable.
For application-triggered messages, use the API reference to implement the software integration. Claude can help prepare the surrounding setup, but the application should supply the actual event and recipient data rather than relying on a conversational guess.
Keep capacity and consent visible
Inboxes are free and unlimited on every plan. Sending has allowances: Free includes 3,000 emails a month, up to 100 a day, and sends beyond the daily cap go out the next day. Paid plans refuse sends beyond the monthly allowance until renewal or upgrade.
There are no overage or usage fees. Check pricing before choosing the audience and timing for a launch. An assistant should report a capacity problem rather than hide it behind a general “working on it” response.
Hard bounces, complaints, and unsubscribes create workspace-wide suppressions. Marketing requires consent and the required sender information. Read the acceptable-use policy before importing a list, and never ask Claude to work around a suppression by changing the sender.
FAQ
Does the one-click link grant Claude access immediately?
No. It opens the custom-connector dialog with Banger’s details. You still complete setup and authorize the connection through OAuth.
How do I revoke Claude’s access?
In the Banger app, open Settings → Connected apps, find the Claude connection, and choose Revoke. Confirm the revocation.
Can Claude activate my welcome Journey on its own?
No. It can prepare the Journey, but a person decides the activation Approval in Banger’s web app.
Can I use the same Banger server with another assistant?
Yes. The remote MCP endpoint is shared across supported MCP clients. Complete each client’s connection flow and review the permissions granted to that connection.
