Evite MCP Server
# Evite API and MCP server for ChatGPT and Claude
Evite has no public API, webhooks or official MCP server according to the live Cotlet.dev integration page (checked 27 October 2026). Cotlet.dev connects ChatGPT, Claude and other AI agents to your own Evite host account through a hosted MCP server with 13 workflow tools. Six tools ask for approval by default, including sends and changes guests would notice.
## What you can ask
> List my upcoming Evite events.
> Show guests who have not replied to my event.
> Draft an event and add guests from my spreadsheet.
> Draft a message to guests who have not replied and ask me before sending it.
> Log a guest RSVP received by phone.
> Export the guest list with RSVPs for the caterer.
## Connect in 2 minutes
Get your API key at https://cotlet.dev/app and export it as `COTLET_API_KEY`.
### ChatGPT
Settings > Apps & Connectors > Create. Use `https://cotlet.dev/mcp/v1/connect` with OAuth.
### Claude
Settings > Connectors > Add custom connector. Use `https://cotlet.dev/mcp/v1/connect`.
### Claude Code
```bash
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"
```
### Cursor
Copy `.cursor/mcp.json` from this repo into your project:
```json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
}
```
## Run it locally (stdio)
This repo is a real MCP server. It speaks MCP over stdio, lists its Evite tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.
Clone this repository and run `python3 evite_agent.py serve` with `COTLET_API_KEY` set.
Or with Docker:
```bash
docker build -t evite-mcp .
docker run -i --rm -e COTLET_API_KEY evite-mcp
```
The local server exposes seven browser helper tools, distinct from the 13 hosted workflow tools described on the live page.
Local tools: `evite_guide`, `evite_status`, `evite_open`, `evite_read`, `evite_click`, `evite_type`, `evite_close`. Without `COTLET_API_KEY` a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".
## Command line
Python 3.10+, nothing else to install. Run from this repo:
```bash
export COTLET_API_KEY="your-key"
python3 evite_agent.py connect # ready config for Claude Code, Cursor, ChatGPT
python3 evite_agent.py status # is Evite ready in your Cotlet.dev account
python3 evite_agent.py guide # Evite screens and sign-in link
python3 evite_agent.py read # open Evite, read the page, close the browser
python3 evite_agent.py tools # list Cotlet.dev tools
python3 evite_agent.py serve # start the stdio MCP server (same as no argument)
```
## Questions from Evite users
**Does Evite have an official API or MCP server?**
The live Cotlet.dev page, checked 27 October 2026, reports no public API, webhooks or official MCP server. Cotlet.dev provides an independent hosted connection to your own Evite host account.
**Which Evite account do I need?**
Use your own Evite account as the host of the events. Sign in through its Cotlet Cloud Browser and enable Evite for agents.
**Which actions ask for approval?**
Six of the 13 hosted tools ask first by default, including sends, changes guests would notice and cancellation. Drafts, copies and logging RSVPs run directly because they reach no one. Approval settings can be changed per tool.
**Can an agent RSVP to invitations I received?**
The Cotlet.dev Evite tools are for hosts managing their own events and guests. They do not RSVP to invitations you receive.
**Can an agent pay for a Premium invitation?**
No. Complete Premium purchases yourself in Evite. The agent can draft and send free invitations.
**Is this an official Evite integration?**
No. Cotlet.dev is independent and is not affiliated with Evite.
## Live integration
[Evite tools and connection guide](https://cotlet.dev/integrations/evite-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=evite)
---
More: https://cotlet.dev/integrations/evite-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=evite
Start free: https://cotlet.dev/signup?app=evite&utm_source=github&utm_medium=readme&utm_campaign=evite
TDQS
Scored across 7 tools
Each tool has a clearly distinct role in the browser lifecycle: readiness check, guide, open, read, click, type, and close. There is little risk of confusing page-reading with page interaction or session setup.
All tools use a consistent evite_ prefix and snake_case, with mostly action-oriented names. The minor deviation is that evite_status and evite_guide are noun-like while the rest are verbs.
Seven tools is well-scoped for a focused browser automation wrapper, with each tool earning its place. It avoids both a thin single-tool surface and excessive fragmentation.
The set covers the core browser interaction loop: open, read, click, type, and close, with status and guidance for setup. Minor gaps exist around explicit scrolling, waiting, selecting, or browser-back operations, but agents may work around many of these through read/click/type.