Skip to main content
The Paubox MCP Server lets AI assistants send HIPAA compliant email and work with Paubox Forms by calling Paubox tools through the Model Context Protocol (MCP). Once connected, a client like Claude, Claude Desktop, Cursor, or any other MCP-compatible host can send encrypted email, check delivery status, fetch Paubox Form definitions, and submit form responses. The server runs the Paubox Email API and Paubox Forms calls on your behalf. Your API key stays with the server process and is never shared with the AI model.

​
What you can build with it

Healthcare teams use the Paubox MCP Server to:
  • Draft and send encrypted appointment reminders, follow-ups, and care instructions from inside a clinical AI assistant
  • Run an intake conversation that fetches a Paubox Form, collects answers, and submits the response without copying data between tools
  • Add email delivery and status checks to multi-step agent workflows that span scheduling, billing, or patient outreach

​
Available tools

ToolWhat it does
send_secure_emailSend a HIPAA compliant email through the Paubox Email API
check_email_statusCheck delivery status for a previously sent message
validate_credentialsVerify that the configured API key is valid
get_formRetrieve metadata for a Paubox Form
submit_formSubmit a response to a Paubox Form
See MCP tools for the full parameter reference for each tool

​
Compatible clients

Any client that follows the MCP specification can connect to the Paubox MCP Server, including:
  • Claude (via Settings > Integrations on claude.ai)
  • Claude Desktop
  • Cursor, Windsurf, and other MCP-aware IDEs
  • Custom agents and scripts built on the MCP specification
The server supports two transports, so clients can pick whichever they natively use:
  • HTTP at https://mcp.paubox.com: authenticate via the OAuth connector form, or set x-paubox-api-key and x-paubox-api-user headers
  • stdio via npx @paubox/mcp@latest with PAUBOX_API_KEY and PAUBOX_API_USER in the environment

​
How it handles HIPAA and credentials

Email sent through the Paubox MCP Server is encrypted by the Paubox Email API, the same HIPAA compliant transactional email service that Paubox provides to healthcare developers. Messages count against your Email API plan and appear in your Paubox dashboard alongside the rest of your API traffic. Your API key is held by the MCP server process. It is not sent to the AI model and does not appear in tool calls or model context.

​
Get started

Quickstart

Connect Claude, Claude Desktop, or any MCP client.

MCP tools

See parameters and responses for every tool.

Authentication

Generate a Paubox Email API key and configure credentials.

Email API

Learn more about the underlying Paubox Email API

​
FAQs

It is a Model Context Protocol server hosted at https://mcp.paubox.com that gives AI assistants access to the Paubox Email API and Paubox Forms. Agents can send HIPAA compliant email and submit secure intake forms as native tool calls.
Yes. Connect through Settings > Integrations on claude.ai, or add the server to claude_desktop_config.json for Claude Desktop. The Quickstart covers both setups.
No. It uses your existing Paubox Email API account. The Email API free tier covers 300 emails per month. 
No. The key is held by the MCP server process. The assistant calls tools by name and never sees the credentials.
HTTP at https://mcp.paubox.com, and stdio via the @paubox/mcp npm package.

​
Community & support

Q&A

Ask usage questions in GitHub Discussions.

Ideas

Propose features and improvements.

Bug reports

File reproducible bugs on GitHub Issues.
Never post PHI, recipient addresses, or message content in public threads. Account, billing, or anything sensitive goes to support@paubox.com.