Paperless Post MCP Server
Guest lists, RSVPs and messages for Paperless Post events.
Hosted MCP Server
npx add-mcp 'https://cotlet.dev/mcp/v1/paperless-post'Installs into Claude Code, Codex, Cursor and more
Documentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Paperless Post API and MCP server: Let your AI agent handle your Paperless Post RSVPs.
Paperless Post has no public API, no webhooks and no MCP server (checked 27 Oct 2026). None of its 176 help articles mentions an API or Zapier. Cotlet runs 11 Paperless Post tools hosted, over MCP for agents and REST for scripts.
Guest lists, RSVPs and messages for Paperless Post events. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with Paperless Post
- Page: https://cotlet.dev/integrations/paperless-post-api-mcp-server
What can you automate in Paperless Post?
- Load guests from any spreadsheet
- Send or schedule the Card
- Remind guests who have not replied
- Tag guests and message each group
- Write to one guest privately
- Export the headcount for the venue
Does Paperless Post have an MCP server or an API?
- Paperless Pro integrations with Raiser's Edge (beta), Salesforce, HubSpot and Mailchimp (waitlist) are rolling out to annual subscribers only, and Paperless Post does not say what they sync.
- Zapier and n8n have no Paperless Post app. Guest lists come in through a template spreadsheet on a computer and go out as a CSV from the Tracking page.
- The AI in Paperless Post (Magic Art, Magic Pen) writes and draws inside the editor. It does not touch guests or RSVPs.
| What you need | By hand | Your own script | Cotlet |
|---|---|---|---|
| Load guests from any CSV or CRM export | Template file, desktop only | If you write it | Yes, cleaned first |
| Remind only guests who have not replied | Each round by hand | If you write it | Yes, after your OK |
| Tag guests from your own list | One guest at a time | If you write it | Yes, in one call |
| Runs with your computer off | No | If you host it | Yes, hosted |
| Allowed by Paperless Post's terms | Yes | No, scripts are banned | Web app, still automation |
Checked 27 Oct 2026. Sources: Does Paperless Post offer any integrations? (Help Center), Exporting your Tracking page and RSVPs (Help Center), Zapier: no Paperless Post app (404), Paperless Post Terms of Service
How does Cotlet connect to Paperless Post?
- Sign in to Paperless Post. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your Paperless Post password, and no invitation or message reaches a guest until you approve it.
Connect Paperless Post to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Enable Paperless Post for agents. Make a Cotlet account, log in to Paperless Post in its Cloud Browser, then press Enable for agents.
- Add the Cotlet address. Put https://cotlet.dev/mcp/v1 in the list of MCP servers or connectors your agent reads.
- Allow the connection. Chat apps send you to a Cotlet sign-in once. Editors, n8n and scripts pass an API key from the console.
Paperless Post shares the address https://cotlet.dev/mcp/v1 with every other app you enable. If you switch Paperless Post on after connecting, refresh the connector to load its tools.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-paperless-post \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet-paperless-post": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-paperless-post]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: paperless_post_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: paperless_post_write
How to use the Paperless Post REST API
Create your Cotlet API key
Create a Cotlet API key with access to Paperless Post and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect Paperless Post in Cotlet and enable it for agents. Account access: Your own Paperless Post account (the host or a co-host of the event).
Make your first Paperless Post API request
REST:
curl https://cotlet.dev/api/v1/paperless-post/events \
-H "Authorization: Bearer $COTLET_API_KEY"
Read events and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "paperless-post",
"tool": "list_events",
"result": {
"events": [
{
"event_id": "ev_8F3K2Q",
"title": "Summer Gala",
"type": "card",
"status": "sent",
"event_date": "2026-10-17T19:00:00-04:00"
}
],
"next_cursor": null
}
}
Returns the Cards and Flyers on your account, newest first. Use the event_id of each item in the other endpoints.
Drafts have no guests sent yet.
limit: Number of events to return. Default: 20.
cursor: Next page cursor from the previous call.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
Paperless Post workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Event details: title, host, date, time, location and the design type. Use get_event in your configured content report. |
| Make | HTTP > Make a request | The Tracking page: each guest or group with status, number attending and Guest Tags. Use list_guests in your configured content report. |
| Python or Node.js | REST API | One guest: status, number attending and the messages sent to them. Use get_guest in your configured content report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Paperless Post; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Paperless Post API endpoints and MCP tools
Cards, Flyers and sending
Sends go up to 5,000 guests at once, a scheduled send up to 2,000. Coins or Paperless Pro guest credits are spent by Paperless Post as usual.
- List events (
list_events, read): Your Cards and Flyers from My Events, with type, date and send status. - Get event (
get_event, read): Event details: title, host, date, time, location and the design type. - Add guests (
add_guests, write): Add guests to the unsent guest list of an event. Nothing is sent until send_invitation. - Send invitation (
send_invitation, write, asks first): Send the Card or Flyer to everyone on the unsent list, now or at a set time.
Guests, RSVPs and contacts
Read only. Guests who came through a Shareable Link appear only after they RSVP. The CSV link expires, so download it at once.
- List guests (
list_guests, read): The Tracking page: each guest or group with status, number attending and Guest Tags. - Get guest (
get_guest, read): One guest: status, number attending and the messages sent to them. - Export guest list (
export_guest_list, read): The Tracking page as a CSV download link, with each guest's RSVP status. - List contacts (
list_contacts, read): Your Address Book: names, emails and phone numbers saved for reuse.
Messages and Guest Tags
Messages are text only, up to 2,000 characters. Guest Tags need All Access, Paperless Post Plus or Pro, and only hosts and co-hosts see them.
- Send message (
send_message, write, asks first): Broadcast from Messages & Reminders to guests by status and Guest Tag. - Send private message (
send_private_message, write, asks first): Message one guest in their message log. - Tag guests (
tag_guests, write): Add a Guest Tag to guests. Tags are visible to hosts and co-hosts only.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/paperless-post-api-mcp-server#tools
Who can see my Paperless Post session, and how do I revoke it?
- What we store. Your logged-in Paperless Post profile, AES-256-GCM encrypted, in Finland. No password.
- What your agent gets. The 11 Paperless Post tools, never the cookie itself.
- What the session sees. Your events, guest emails and phones, RSVP answers, Address Book.
- What no tool touches. Coins, saved cards, Paperless Pro, co-hosts and your password.
- If Paperless Post asks to verify. A 6-digit code goes to your email or phone. You enter it, we never do.
- How to cut access. Disable for agents, reset the browser, or delete the API key.
Your first login from the Cloud Browser sends Paperless Post's new-device email to every address on your account; that one is you. Our site gets A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). There is no SOC 2 report or third-party pentest yet.
Is it against Paperless Post's terms? Account safety
Such license ... does not permit use of any data mining, robots, scraping or similar data gathering or extraction methods, and you agree not to engage in any other automated use of the Service, including using scripts to send comments or messages.
Paperless Post Terms of Service, Service content, software and trademarks, 26 Oct 2026
The words "using scripts to send ... messages" were added in August 2025 and describe what send_message does. The same terms let Paperless Post suspend an account "if we believe your account is being used by anyone else". So the risk is real and it sits with you as the account holder. We found no public case of a Paperless Post account closed for automation (checked 27 Oct 2026).
How we keep your account looking like you:
- Your own host account, logged in by you
- One Cloud Browser with a steady IP and cookies, so no new-device email on every call
- Every invitation and message waits for your OK
- No tool buys Coins or changes your plan
- If Paperless Post objects, we pause its tools for everyone within 24 h
The terms also ban junk mail and spam. Send to people who expect to hear from you, and space a big round of reminders over a few days.
What happens when Paperless Post changes?
- 12 h between tests of the Paperless Post reads and drafts
- 24 h between tests of sends a guest would see
- $0 for a call to a Paperless Post tool paused for repair
Paperless Post is rolling out new pricing bundles to some drafts and not others, so screens differ between accounts. When a button moves on the Tracking page, we fix the tool on our side. status.cotlet.dev checks the site, console and API every 3 minutes.
Approvals, undo and mistakes
- Reads the deadline. Past the RSVP date it stops, since replies are closed.
- Splits the list. Answered, still waiting, and bounced or unsubscribed.
- Waits for your OK. The reminder sits in your Cotlet console first.
- Reports the count. People attending, who got it, who needs a fix.
| Action | Undo |
|---|---|
| Send an invitation now | No. Delete guest takes away their access to the Card |
| Schedule an invitation | Yes, Edit or cancel scheduled sending before it goes |
| Send a broadcast or private message | No, it is in their inbox |
| Add guests to the unsent list | Yes, remove them before sending |
| Tag guests | Yes, remove the tag; guests never see tags |
3 of 11 tools ask first: send_invitation, send_message and send_private_message, the three that reach a guest. Adding guests and tagging them reach nobody, so they run at once. Switch the wait off per tool for a scheduled run.
Changing the date in Event Details keeps the RSVPs you already have. For a fresh round of replies, Paperless Post suggests a new invitation.
MCP call:
{
"name": "send_message",
"arguments": {
"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"
]
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/paperless-post/events/ev_8F3K2Q/messages \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"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"]}'
Response:
{
"event_id": "ev_8F3K2Q",
"broadcast_id": "bc_51290",
"status": "sent",
"recipients": 23,
"sent_at": "2026-10-10T18:42:00-04:00"
}
A script or cron job reaches the same tools over REST at /api/v1/paperless-post, with one key and one price. tag_guests on a design without Guest Tags fails, and a failed call costs nothing. The tools table lists the REST path of each tool.
How much does the Paperless Post MCP server cost?
About $14 a month for a wedding of 117 guests and a shower of 24 in one month, 2,370 credits. Coins or Paperless Pro are still paid to Paperless Post.
| Job | Calls | Credits |
|---|---|---|
| Clean a guest sheet, add it and send or schedule | 7 × 2 | 140 |
| Weekly headcount and RSVP reminder, per event | 6 × 8 | 480 |
| Tag a group and send it its own message | 3 × 3 | 90 |
| Private note to one guest | 2 × 6 | 120 |
| Final count and CSV for the venue | 2 × 2 | 40 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 2,370 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Works with free designs too
The month is our example. The average US wedding in 2025 had 117 guests (The Knot), and Peerspace puts an adult party at about 24. Paperless Post itself charges from $0.50 a guest on Basic, or $250 a year for 250 guests on Pro. Dollars at the $29 pack rate.
Paperless Post MCP server on GitHub or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| Paperless Pro integrations | Raiser's Edge in beta, Salesforce, HubSpot and Mailchimp on a waitlist. | Annual Pro plan only, from $250 a year. No agent, no reminders, and the sync is not documented. |
| Shareable Link from your own email | Send the Card link through Gmail, a CRM or any mail tool you already automate. | Guests show on the Tracking page only after they RSVP, so nobody can be reminded before that. |
| CarlyEvents | Another invitation app; its blog says every action is available over MCP for Claude and ChatGPT. | You move your guests and designs off Paperless Post. |
| chrischall/evite-mcp | Community MCP server for Evite, run on your own computer. | Evite only, 0 stars, last commit 26 Oct 2026. |
GitHub has no Paperless Post MCP server or CLI, only clones and a third-party profile with no endpoints. Stay on Paperless Post and want an agent to work the guest list: Cotlet. Ready to switch apps: an invitation tool with its own MCP.
Who runs Cotlet
Cotlet is made by Take Group sp. z o.o., a software company in Poland, EU (VAT PL6342984273), in business since 2019. Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing) founded it. Send questions about the Paperless Post tools to contact@cotlet.dev.
Paperless Post API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open Paperless Post under Integrations in the console and log in to Paperless Post in its Cloud Browser. The trial starts when you sign up, and no card is asked.
How do I connect Paperless Post to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Paperless Post once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Paperless Post account through Cotlet, in their phone apps too.
What can ChatGPT do in Paperless Post?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Paperless Post: send RSVP reminders to guests who have not replied; send invitations from a spreadsheet; export RSVPs to a spreadsheet. You ask in plain words, and anything that reaches other people waits for your OK first.
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.
Does Paperless Post have webhooks?
No. Paperless Post sends nothing out when a guest replies, and the host gets push notices only in the iOS app. Run your agent on a schedule instead, for example a list_guests pass every Monday until the deadline.
Can the agent buy Coins or pay for a design?
No. No tool spends money. If a send needs Coins you do not have, the call stops and you buy them in Paperless Post yourself.
Can it edit the design or the event details?
No. The tools work on guests, sends, messages and tags. You change the Card and Event Details in Paperless Post, then the agent reads them with get_event before it writes to guests.
Is the MCP server different from the REST API?
Only the entry point differs. Both carry the same 11 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST.
Is Cotlet affiliated with Paperless Post?
No. Cotlet is independent and has no tie to Paperless Post.
Can I use the Paperless Post API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.