Partiful by Cotlet MCP server

Partiful API and MCP server, self-hosted

A Partiful API and a Partiful MCP server you run on your own computer, in Python, on the session of your own Google Chrome. All 14 Partiful tools we run in production at Cotlet: events, guest lists with questionnaire answers, the Export CSV file, check-in, Guest Approval, invites and Text Blasts.

Partiful has no public API and no official MCP server. This repo gives you both:

• MCP server for Claude Code, Claude Desktop, Cursor, Codex and any MCP client, over stdio or HTTP. Setup
• REST API on http://127.0.0.1:8787/api/v1/partiful, with OpenAPI docs at /docs. Setup
• Python: call("listguests", eventid="..."), plus 9 ready scripts in examples/.

It is for technical people who want to run it themselves, for noncommercial use only (license). If you want it running 24/7 on a server, kept working when Partiful changes its site, for a team or a business, use the hosted version at cotlet.dev.

git clone https://github.com/cotletdev/partiful-api-mcp-server.git && cd partiful-api-mcp-server
python3 -m venv .venv && . .venv/bin/activate && pip install -e .
partiful-mcp connect                                  # reads your Partiful session from Chrome
partiful-mcp call list_events
claude mcp add partiful -- "$PWD/.venv/bin/partiful-mcp" mcp

Contents

• How it works
• Requirements
• Install
• Connect your Chrome
• MCP server
• REST API
• Python and the example scripts
• All 14 tools
• Configuration
• Security and your Partiful account
• Errors
• Self-hosted or hosted

How it works

AI agent (MCP) / script (REST, Python) ──▶ partiful-mcp on your computer ──your Partiful sign-in──▶ api.partiful.com
                                                  ▲                                                 Firestore
                      partiful-mcp connect ───────┘ reads it once from your Chrome (DevTools Protocol)

1. You sign in to Partiful in your own Chrome, with your phone number and the code Partiful texts you.
2. partiful-mcp connect attaches to that Chrome through the Chrome DevTools Protocol. It reads the partiful.com cookies and, from a partiful.com tab, the signed-in user that the Partiful web app keeps in IndexedDB (Firebase, with its refresh token). If no Partiful tab is open, it opens one in the background and closes it again. Both are saved to ~/.config/partiful-api-mcp/session.json, readable by your user only.
3. Every tool call is a request to the endpoints the Partiful web app calls itself: its functions on api.partiful.com, and Firestore for guest lists and event edits. Requests go out with curl_cffi, which copies Chrome's TLS fingerprint. No headless browser runs.

Partiful's sign-in token lasts an hour. The server renews it from the saved refresh token at Google's securetoken.googleapis.com, the way the web app does, so you connect once and not every hour. When Partiful ends the session, the server reads it from Chrome again, if Chrome is open with remote debugging on.

Requirements

Shortened. The full README is on GitHub.