PristineSend exposes a remote Model Context Protocol server so an AI agent can send email, check deliverability, manage contacts, design campaign drafts, and observe what happened after a send — all as native tools. It's a thin doorway over the same API the SDK uses — every tool runs the identical deliverability, suppression, idempotency, and scope logic as the REST endpoints. Authenticate with a scoped API key; hand an agent a Send-only key and that's the only thing it can do.
The AI is your own, Claude for example, on your own account with it: PristineSend doesn't provide one. You connect it to PristineSend once, then ask it in your own chat with it, and it works through these tools.
| Endpoint | https://pristinesend.com/api/mcp |
| Transport | Streamable HTTP |
| Auth | Bearer API key (ps_live_… or ps_test_…) |
| Tools | send · deliverability · contacts (read/write) · email status · events · suppression check · campaign drafts · templates · CRM · meetings |
The server lives at https://pristinesend.com/api/mcp. Authenticate exactly like the REST API — a Bearer API key from Settings → Developer. Each tool enforces its own scope, so a key's scopes decide which tools it can call (see Least-privilege keys). A missing or invalid key is rejected before any tool runs.
The fastest way to use PristineSend from Claude Code is the plugin: one install wires up the MCP server and bundles a deliverability skill — guidance that loads automatically when you're sending email, so the agent scores content before sending, sends from an authenticated domain, respects the suppression list, and confirms delivery.
PRISTINESEND_API_KEY environment variable on your machine — the plugin is public, but it does nothing without a valid key, which only your PristineSend account provides. Use a least-privilege key and start in the sandbox with a ps_test_ key.Prefer to connect the server directly (or using another client)? Any client that speaks remote MCP over Streamable HTTP with a Bearer header works — the same server, no plugin required. The common ones:
The in-app custom-connector UI accepts OAuth connectors only — there is no API-key field — and PristineSend supports OAuth, so no key is involved. Add https://pristinesend.com/api/mcp as a custom connector and sign in. Your credentials stay on your side: nothing is pasted into a conversation.
add_picture needs too, the signup form tools need Read forms and Edit form drafts, and the CRM tools need Read the CRM and Edit the CRM, and the meeting tools need Read meetings and booking pages and Cancel meetings and send busy times. Other clients read the list of tools when they connect, so reconnect PristineSend in them.| Tool | Required scope | What it does |
|---|---|---|
send_email | email:send | Send a transactional email — deliverability, suppression, and idempotent retries handled for you. |
send_bulk | email:send_bulk | Draft a campaign to a segment and hold it for a human to approve. Sends nothing on its own; see the Bulk send reference. |
create_segment | segments:write | Build an audience from a filter and read back the recipient count plus a masked sample, so the filter can be checked before anyone approves a send. |
check_deliverability | deliverability:check | Score an email against the editor's deliverability rules before sending. Pure check — sends nothing, logs nothing. |
add_contact | contacts:write | Add a contact to the workspace audience (idempotent on email). With double_opt_in, the person is emailed a confirmation and added only once they confirm, in one of nine languages. |
list_contacts | contacts:read | List audience contacts, newest first, with filters + cursor pagination. |
get_email_status | emails:read | Look up a sent email by id: its status plus the delivered / opened / clicked / bounced / complained timeline. |
list_events | events:read | Read the delivery & engagement event log (delivered, opened, clicked, bounced, complained, failed). A pull log — no webhook needed. |
check_suppression | suppressions:read | Check whether an address is on the do-not-send list before you send to it. |
list_clicked_links | campaigns:read | Rank the links a campaign's readers clicked. Unsubscribe links are counted, never named. |
get_design_kit | campaigns:read | Read what an email for this account needs: its brand, pictures, starters, the design format, senders, topics, merge tags and the rules. Read once per conversation that designs. |
list_campaign_drafts | campaigns:read | List the account's campaign drafts, each with its version, the notes left for your AI and its link in PristineSend. |
create_campaign_draft | campaigns:write | Create a draft from a design, one of the four starters, or Markdown. Sends nothing; answers the draft and its check. |
get_campaign_draft | campaigns:read | Read a campaign's design or Markdown (never the HTML), its version and the notes its team left for your AI. |
update_campaign_draft | campaigns:write | Change a draft at the version it read: edits by part id, a whole design, or Markdown. A draft changed since is refused, never overwritten. |
check_campaign_draft | campaigns:read | Check a campaign as the editor does: the score, colours that cannot be read and unfinished parts; with links, every link and picture opened. Writes and sends nothing. |
send_campaign_test | campaigns:write | Send a [TEST] of a campaign to someone on the account's team, or to the person who connected the agent. At most 100 a day per account. |
resolve_campaign_note | campaigns:write | Resolve a note the team left on a draft, with a reply saying what changed. The person sees the reply beside their note in the editor. Changes nothing in the email. |
add_picture | campaigns:write | Add a picture to the account's library from its web address, so a draft can show it: drafts show only library pictures and the built-in backgrounds. It shows in the library like an upload, and anyone on the team can remove it there. |
list_templates | campaigns:read | List the account's templates, newest first, without their email: name, subject, how each is built, version, and its address in PristineSend. |
get_template | campaigns:read | Read one template, with its email as written: the design, the Markdown or the HTML. |
save_template | campaigns:write | Create a template, or change one at the version it read. From a design, a starter, Markdown or HTML: an HTML email's pictures from other sites are copied into the library. Start a draft from a template with create_campaign_draft's template_id. Sends nothing. |
list_forms | forms:read | List the account's signup forms: where each stands, its page address and its confirmed signups in the last 30 days. |
get_form | forms:read | Read a signup form: its draft, what Publish would still refuse, its numbers once live, and the topics and properties its draft may name. |
save_form | forms:write | Create a signup form, or change a form's draft at the version it read. Never publishes: a person presses Publish in PristineSend, and the form is checked before it goes live. |
search_crm | crm:read | Find companies, deals and contacts in the CRM by name, domain or address, at most 8 of each. |
get_crm_record | crm:read | Read one contact, company or deal with its timeline: emails, replies, signups, deal history, notes and tasks. |
get_pipeline | crm:read | Read the pipeline's stages in order and the team, which save_deal and save_crm_task name. |
list_crm_tasks | crm:read | List tasks, the open tasks to answer a reply included, with who wrote, when and the email they answered. Never the reply's words. |
save_company | crm:write | Create a company, or change one's name, domain or property values. |
save_deal | crm:write | Create a deal, change one at the version it read, or move it to another stage. A deal entering a stage can start an automation. |
add_crm_note | crm:write | Write a note, call, meeting or email on a contact, company or deal. |
save_crm_task | crm:write | Create a task, finish or reopen one, or change its title, due date or assignee. |
list_meetings | meetings:read | List meetings booked on your booking pages or through Calendly or Cal.com, upcoming or past, with the guest and the host. |
get_free_times | meetings:read | List your booking pages, or the times one page offers, each with the page's own link for that time to send to the person booking. It books nothing. |
set_busy_times | meetings:write | Send a team member's busy times from their calendar, which keep those times off their booking pages. |
cancel_meeting | meetings:write | Cancel a meeting booked on one of your booking pages. The guest is emailed, with the message given, and the host is told who cancelled. |
send_email is always idempotent: pass a stable idempotency_key per logical send for full retry safety, or omit it and an identical send within a short window is de-duplicated automatically. A well-behaved agent calls check_deliverability before sending, and holds on a DANGER verdict — it means something in the email is unfinished.
A tool takes only the fields it lists. A field it does not take, a misspelling for example, is refused before the tool runs and nothing is changed. The answer names the field and the fields the tool does take, as the REST API does for an unknown field.
An agent connected here is always held to the account's emails-per-recipient limit: 5 a day and 15 a week per address unless the account changes it, and never a third near-identical email to one address within 10 minutes. A refused send says why and sends nothing; the agent should not retry it straight away.
An account can also turn on strict mode for its connected agents (Settings → Developer). Then an email with a placeholder link, an empty picture spot or no subject, or to an address that is misspelt, throwaway or likely to bounce, is refused instead of sent, and send_email returns the reason.
The draft tools let an AI you connect design a campaign in the format PristineSend's Design editor uses. It reads get_design_kit once, writes a draft with create_campaign_draft, fixes what the draft's check reports with update_campaign_draft, and gives you the draft's app_url to open in PristineSend. Nothing it does sends the campaign: a person presses Send. PristineSend asks no AI model for any of this; the thinking is your AI's own. See the Campaign drafts reference.
The CRM tools let your AI work in your CRM with you: find a company, read a deal's timeline, log a call, move a deal, or help answer the people who replied. They are listed only once your account has the CRM turned on, and none of them deletes anything.
The meeting tools let your AI find a time with someone for you: it reads a booking page's free times and sends the person the page's own link for the time they agree on, where they book it themselves. It can also cancel a meeting booked on one of your pages, and send your busy times (next section). They are listed only once your account has a booking page, or Calendly or Cal.com connected.
The read tools close the send → observe → react loop. After send_email returns an id, call get_email_status with it to see whether the message was delivered, opened, clicked, bounced, or marked as spam; list_events is the same signal across all your sends as a pull log (no webhook endpoint required); and check_suppression tells the agent up front whether an address is on the do-not-send list, so it can skip a send PristineSend would block. These are the same projections behind the Emails, Events, and Suppressions REST endpoints.
PristineSend never reads a calendar. Your booking pages offer the hours you set in Meetings → Your hours, without the meetings already booked on them and the time you blocked. For everything else in your calendar, your AI tells us when you're busy.
set_busy_times.”Your busy times show in Meetings → Your hours, read only, with when and by whom they were last sent, and you can clear them there. An AI sends its own person's busy times unless it names a team member; set_busy_times needs Cancel meetings and send busy times, ticked for the connection in Settings → Connected agents (MCP). See also the Busy times reference.
Build and test your agent against a ps_test_ key. Test keys capture sends — send_email returns a normal success with a test_ id, but nothing is delivered and nothing is metered. Swap to a ps_live_ key when you're ready to send for real. See Test mode.
Scopes are the safety story. Create a key in Settings → Developer with only the scopes the agent needs — e.g. a Send only key (email:send) can call send_email and is refused every other tool with a clear insufficient-scope error. A key with every scope can use every tool. This bounds the blast radius of a leaked or rogue key to exactly what you granted. See Authentication.