Paperless Post has no public API (checked 10 Oct 2026). Cotlet is a hosted MCP server and REST API for Paperless Post with 11 endpoints (6 read, 5 write): your AI agent signs in as you and does the work.
Paperless Post has no public API (checked 10 Oct 2026). Guest lists, sending, RSVPs and messages live only in the website and apps, and guest lists and RSVPs move in and out as CSV files.
What Paperless Post's own tools do compared with Cotlet
Every Monday until the RSVP deadline, check the Summer Gala in Paperless Post, give me the headcount, and send a Reminder to RSVP to everyone who has not answered and was not reminded in the last 5 days. List anyone who bounced or unsubscribed so I can reach them myself. Your agent calls list_events, list_guests, get_guest, send_message and export_guest_list.
Take guests.xlsx from my planner, clean it up for Paperless Post (one contact per guest, families as groups, plus-ones in Total Invited), add everyone to the unsent list of my "Summer Gala" Card and schedule it for Friday at 9:00 New York time. Show me the rows you had to fix first. Your agent calls list_events, list_guests, list_contacts, add_guests and send_invitation.
Export RSVPs to a spreadsheet Runs: Weekly
Give me the current RSVP list for Saturday as a CSV and tell me how many are attending. Your agent calls list_events, list_guests and export_guest_list.
Announce a time or location change
The venue changed. Tell everyone attending about the new address. Your agent calls get_event and send_message.
Here are the out-of-town guests from my wedding planner sheet. Tag them "lodging" in Paperless Post, then send the ones who are attending the hotel room block link, and tell me who on the sheet is not on the guest list. Your agent calls list_guests, tag_guests, get_event, send_message and send_private_message.
Endpoints
What is the Paperless Post API?
Cotlet's Paperless Post API exposes 11 endpoints for your own Paperless Post account: list events, get event, list guests, get guest, export guest list, list contacts, add guests, send invitation, send message, send private message and tag guests. The list_events endpoint returns your Cards and Flyers from My Events, with type, date and send status. Each endpoint takes simple JSON inputs like event_id, status or cursor and works both as an MCP tool for agents and as a REST call for scripts.
Event details: title, host, date, time, location and the design type.
read
Returns what guests see on the invitation: title, host name, date and time, time zone and location. Use it before a time or location message so the text matches the invitation.
The Tracking page: each guest or group with status, number attending and Guest Tags.
read
Returns the rows of the Tracking page for one event, with each guest's status, how many are attending and their Guest Tags. Guest Tags show only if you are a host or co-host. Pass guest_id to get_guest or tag_guests.
POST /api/v1/paperless-post/list_guests
Input
Input: list_guests
Parameter
Type
Description
event_id required
string
Card or Flyer ID from list_events.
status
string
Only guests with this status as shown on the Tracking page, for example attending.
One guest: status, number attending and the messages sent to them.
read
Returns one row of the Tracking page with the broadcast and private messages sent to that guest. Use it to check what a guest already received before you write again.
The Tracking page as a CSV download link, with each guest's RSVP status.
read
Returns a link to the CSV the Export guest list button on the Tracking page downloads. The link works for a limited time, so download it right away. Reads only; nothing changes in Paperless Post.
Your Address Book: names, emails and phone numbers saved for reuse.
read
Returns the contacts saved in your Address Book, so your agent can add known people to a guest list without a file. Matching by search is case insensitive.
Add guests to the unsent guest list of an event. Nothing is sent until send_invitation.
write
Adds guests to the unsent list, the same list the spreadsheet upload fills. Each guest needs a name and an email or phone number. Nothing reaches the guests until send_invitation, and you remove a guest in the app, so this call needs no confirmation.
POST /api/v1/paperless-post/add_guests
Input
Input: add_guests
Parameter
Type
Description
event_id required
string
Card or Flyer ID from list_events.
guests required
object[]
List of { name, email or phone, group_name, total_invited }.
Send the Card or Flyer to everyone on the unsent list, now or at a set time.
asks first write
Sends the invitation to everyone on the unsent guest list. With send_at it is scheduled instead of sent now. Guests receive it as soon as it goes out. By default you confirm each call; you can switch that off for this tool.
Broadcast from Messages & Reminders to guests by status and Guest Tag.
asks first write
Sends a broadcast like the Messages & Reminders screen: pick a template or write your own, then recipients by guest status and optional Guest Tags. The text is limited to 2,000 characters and cannot carry attachments. By default you confirm each call; you can switch that off for this tool.
POST /api/v1/paperless-post/send_message
Input
Input: send_message
Parameter
Type
Description
event_id required
string
Card or Flyer ID from list_events.
template
enum
reminder_to_rsvp, event_reminder, time_location_change or write_your_own. Default: write_your_own.
message required
string
Message text, up to 2,000 characters. No attachments.
subject
string
Email subject.
statuses
string[]
Guest statuses to reach, as shown on the Tracking page, for example attending. Default: all guests.
Sends a private message to one guest, as the Private message option in Messages & Reminders does. The text is limited to 2,000 characters. By default you confirm each call; you can switch that off for this tool.
Add a Guest Tag to guests. Tags are visible to hosts and co-hosts only.
write
Adds one Guest Tag to the guests you list; the tag is created if it does not exist. Guest Tags need All Access pricing or Paperless Pro, otherwise the call fails. Tags reach no one and one call removes them, so this call needs no confirmation.
How do I connect Paperless Post to Claude Code, Codex or Cursor?
Connecting Paperless Post takes three steps: request access, sign in to Paperless Post once, then add one MCP server or call the REST API with the same key.
Connect Paperless Post over MCP
1
Create an account
Sign up and add Paperless Post in the console. Your API key is there too.
2
Sign in to Paperless Post once
Open the connect page from the console and sign in to Paperless Post the way you always do. We keep the session, never your password, and you can revoke it anytime.
Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.
4
Ask your agent
Prompt
Every Monday until the RSVP deadline, check the Summer Gala in Paperless Post, give me the headcount, and send a Reminder to RSVP to everyone who has not answered and was not reminded in the last 5 days. List anyone who bounced or unsubscribed so I can reach them myself.
Ask in plain words. Your agent finds the Paperless Post tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.
Call Paperless Post over REST
1
Export your API key
Shell
export COTLET_API_KEY="cotlet_..."
Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.
2
Call a tool
curl
curl https://cotlet.dev/api/v1/paperless-post/send_message \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"event_id":"ev_8F3K2Q","template":"reminder_to_rsvp","subject":"Please RSVP by Friday","message":"Hi! We are finalizing the headcount for the Summer Gala. Please reply by Friday.","statuses":["opened"]}'
Every tool is a POST endpoint at /api/v1/paperless-post/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.
You get plain JSON back, ready for your script. A failed call costs nothing.
Why Cotlet
Why use Cotlet for Paperless Post? Hosted, safe and kept working.
Built for agents
One MCP server for every app you connect.
The same tools as a REST API for scripts and cron jobs.
Works with Claude Code, Codex and Cursor.
Your login stays yours
You sign in to Paperless Post yourself. We keep only the session, encrypted with AES-256.
The model never sees a login.
No stored passwords, no CAPTCHA solving, no MFA bypass.
You stay in control
Pick read only, or read and write.
Anything that reaches other people waits for your OK, unless you switch it off per tool.
Revoke access in one click.
Kept working for you
We test every integration daily.
When Paperless Post changes, the tool pauses until we fix it.
Failed calls cost nothing.
Alternatives
Is there a Paperless Post MCP server on GitHub?
No Paperless Post MCP server or Zapier app exists today. Hosts upload a guest spreadsheet per event, export RSVPs from the Tracking page and write each reminder in Messages & Reminders by hand; Cotlet gives your agent the same screens as tools.
Cotlet compared with a By hand
By hand
Cotlet
Setup
None, you click through the website
Request access, sign in to Paperless Post once, add one MCP server or API key
Guest lists
Fill the spreadsheet template and upload it per event
Your agent adds guests from any file or CRM export
RSVPs
Export the guest list as CSV and merge it yourself
Your agent reads statuses and answers live, or fetches the CSV link
When Paperless Post changes
You find the new button yourself
Our team tests it daily and fixes it for you; failed calls are free
Your session
Your browser; you log in again when it expires
Encrypted in an EU vault, revoked in one click; if Paperless Post logs you out, your agent gets a link to sign in again
Where it runs
Your browser, while you sit at it
Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule
Price
Free, paid for with your time
Free 7-day trial with 5,000 credits, then credits per call
Which one fits you
Pick Cotlet if
you are not a developer, or you do not want to maintain a server
you need it to keep working when Paperless Post changes, without checking it yourself
your agent or a script should run it on a schedule, also while your computer is off
Pick an open-source server if
you are comfortable installing, updating and fixing it yourself
you want the session to stay on your own computer
you only need it now and then, from one MCP client
For AI agents
Cotlet for Paperless Post in plain text The facts on this page in one block: status, endpoints, access, pricing, contact.
Endpoint health
verified 2h ago
list_eventspassing
get_eventpassing
list_guestspassing
get_guestpassing
export_guest_listpassing
+ 6 more endpoints
11/11 passing latest checkself-healing
paperless-post.txt
Paperless Post has no public API (checked 10 Oct 2026). Guest lists, sending, RSVPs and messages live only in the website and apps, and guest lists and RSVPs move in and out as CSV files.
Cotlet provides a hosted MCP server and REST API for Paperless Post: 11 tools (6 read, 5 write).
Access Request access at https://cotlet.dev/app/signup?app=paperless-post; we email the API key.
MCP server https://cotlet.dev/mcp/v1
REST base https://cotlet.dev/api/v1/paperless-post
Auth Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools list_events, get_event, list_guests, get_guest, export_guest_list, list_contacts, add_guests, send_invitation, send_message, send_private_message, tag_guests
Confirm send_invitation, send_message, send_private_message (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown https://cotlet.dev/integrations/paperless-post-api-mcp-server.md
How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=paperless-post (Paperless Post is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Paperless Post once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.
Fits: people who want a hosted Paperless Post server that someone else maintains, including non-developers.
Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Paperless Post in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Paperless Post's terms; Cotlet is not affiliated with Paperless Post.
Can Paperless Post automations run on a schedule in n8n, Make or Zapier?
Yes. Cotlet does not replace your automation platform: it gives it a Paperless Post connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to send rsvp reminders to guests who have not replied, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.
Where to run Paperless Post automations through Cotlet, and how to schedule them
Where
How to connect
How to schedule
Your AI agent
Add https://cotlet.dev/mcp/v1 with your API key.
A scheduled agent run, for example a Claude Code routine.
n8n
MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/paperless-post/{tool}.
Schedule Trigger node.
Make
HTTP module: POST https://cotlet.dev/api/v1/paperless-post/{tool} with an Authorization: Bearer header and a JSON body.
Scenario schedule.
Zapier
Webhooks by Zapier: POST https://cotlet.dev/api/v1/paperless-post/{tool} with the same header and body.
Schedule by Zapier trigger.
Your own script
POST https://cotlet.dev/api/v1/paperless-post/{tool} with your API key.
cron or GitHub Actions.
Pricing & limits
How much does the Paperless Post API cost?
Free 7-day trial with 5,000 credits, no card needed. After that, the Paperless Post API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.
Cotlet plan sizes: price, monthly credits and price per credit
Size
Price
Credits / month
Per credit
Solo
$29/mo
3,000
about $0.0097
Pro
$99/mo
12,000
about $0.0083
Agency
$299/mo
40,000
$0.0075
Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the Authorization: Bearer header.
About Cotlet
How Cotlet holds your access
Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Paperless Post account.
Company details
The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. Terms
Your session
You sign in to Paperless Post yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Paperless Post tool you allowed. When it expires, your agent gives you a link to sign in again. Security
Revoking access
Disconnect Paperless Post in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
What we never do
Store passwords, solve CAPTCHAs or bypass MFA.
Paperless Post's terms
You use your own Paperless Post account and stay responsible for following Paperless Post's terms. Cotlet is independent and not affiliated with Paperless Post. Terms
Request access and pick Paperless Post. Cotlet reviews each request and emails you your API key.
Do I need to be technical?
No. You sign in to Paperless Post once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.
Is a hosted server safe? My Paperless Post session would leave my computer.
Cotlet keeps your Paperless Post session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.
Do Guest Tags work on every Paperless Post plan?
No. Paperless Post offers Guest Tags with All Access pricing or a Paperless Pro subscription (checked 10 Oct 2026), and tags are visible to hosts and co-hosts only. On other plans tag_guests fails and the other tools still work.
Can it attach a file to a reminder?
No. Paperless Post does not allow attachments in follow up messages and caps messages at 2,000 characters, so send_message takes text only. Put a link to a shared file in the message instead.
Can my agent post or send messages in Paperless Post without asking me?
No. Every call to send_invitation, send_message or send_private_message waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_guests, tag_guests runs without asking, because it sends nothing to anyone and one call undoes it.
Can I use the Paperless Post API in n8n?
Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/paperless-post/{tool} from the HTTP Request node.
