add Paubox MCP server #2535
Merged
add Paubox MCP server #2535
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
olaservo
added
the
add-official-server
domdomegg
approved these changes
Aug 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a new server entry to the official MCP server list for the Paubox MCP Server. This entry introduces a MCP server enabling email sending functionality via Paubox's HITRUST certified Email API.
Description
Motivation and Context
Provide an MCP-native way to send email from LLM clients without exposing SMTP credentials.
Enable customers in regulated industries to send messages through a HITRUST CSF-certified email service.
Standardize email delivery workflows behind the MCP tool interface (sendEmail) so prompts/agents can reuse the same abstraction across clients.
How Has This Been Tested?
README previewed and checked for legibility.
Breaking Changes
None. This is an additive server entry in the list and does not modify existing server definitions or client configs.
Types of changes
Checklist
Additional context
The server uses API key authentication and never persists message bodies or keys beyond the request lifecycle.
Rate limiting and delivery semantics follow the Paubox Email API; callers should handle transient failures with retries/backoff.