> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paubox.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Paubox MCP Server

> The Paubox MCP Server gives AI assistants HIPAA compliant email and secure form tools through the Model Context Protocol.

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

| Tool                   | What it does                                              |
| :--------------------- | :-------------------------------------------------------- |
| `send_secure_email`    | Send a HIPAA compliant email through the Paubox Email API |
| `check_email_status`   | Check delivery status for a previously sent message       |
| `validate_credentials` | Verify that the configured API key is valid               |
| `get_form`             | Retrieve metadata for a Paubox Form                       |
| `submit_form`          | Submit a response to a Paubox Form                        |

See [MCP tools](/mcp-server/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](http://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

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/mcp-server/quickstart">
    Connect Claude, Claude Desktop, or any MCP client.
  </Card>

  <Card title="MCP tools" icon="file-text" href="/mcp-server/tools">
    See parameters and responses for every tool.
  </Card>

  <Card title="Authentication" icon="key" href="/mcp-server/authentication">
    Generate a Paubox Email API key and configure credentials.
  </Card>

  <Card title="Email API" icon="shield-check" href="/email-api">
    Learn more about the underlying Paubox Email API
  </Card>
</CardGroup>

## FAQs

<AccordionGroup>
  <Accordion title="What is the Paubox MCP Server?">
    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.
  </Accordion>

  <Accordion title="Does it work with Claude?">
    Yes. Connect through Settings > Integrations on claude.ai, or add the server to `claude_desktop_config.json` for Claude Desktop. The [Quickstart](/mcp-server/quickstart) covers both setups.
  </Accordion>

  <Accordion title="Does the Paubox MCP Server require a separate plan?">
    No. It uses your existing [Paubox Email API](https://www.paubox.com/products/paubox-email-api) account. The Email API free tier covers 300 emails per month. 
  </Accordion>

  <Accordion title="Is the API key ever shared with the AI model">
    No. The key is held by the MCP server process. The assistant calls tools by name and never sees the credentials.
  </Accordion>

  <Accordion title="Which transports does the server support?">
    HTTP at `https://mcp.paubox.com`, and stdio via the `@paubox/mcp` npm package.
  </Accordion>
</AccordionGroup>