Wie installiere ich Evite?

Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.

Benötigt Evite einen API-Schlüssel?

In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.

Welchen Transport verwendet Evite?

Evite läuft lokal über stdio.

Wann wurde Evite zuletzt geprüft?

Zuletzt geprüft: 2026-11-13. Evite MCP server for Claude — list events, guest lists & RSVPs, RSVP, message guests, and create/edit events.

Evite MCP-Server

Agenten stärken

Diesen Server hinzufügen

Der eigene Befehl des Herausgebers. Kein PlugMCP-Endpunkt.

Zu Cursor hinzufügen Zu VS Code hinzufügen Auf PlugMCP ausführen

Host a copy with our keys and logs.

Lokaler Befehl

npx -y [email protected]

Claude Code hat keinen Installationslink für einen lokalen Befehl. Kopieren Sie den Befehl unten und führen Sie ihn in einem Terminal aus.

shClaude Code

1claude mcp add evite-mcp -- npx -y evite-mcp@1.5.0

In einem Terminal ausführen.

jsonClaude Desktop

1{2  "mcpServers": {3    "evite-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Lokal · npmInstallation vom HerausgeberSchritt für Schritt: in Claude hinzufügen

Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden

Auf PlugMCP ausführen

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Starten

Server-Details

Lokal

Transport: stdio
Version: 1.5.0
Zuletzt geprüft

Vom Herausgeber

Dokumentation

evite-mcp

A Model Context Protocol server for — read and act on your events as both (invitations received) and (events you created): list events, view guest lists & RSVP tallies, RSVP, message guests, and create/edit events. Built on .

Tool	Endpoint	Returns
`evite_list_events`	`GET /services/events/v1/`	your events + a totals breakdown (`filterBy` = all/host/others, repeatable `status`, `offset`/`numResults` paging)
`evite_get_event`	`GET /services/event/v1/{id}`	single-event detail (event, settings, location)
`evite_list_guests`	`GET /services/event/v1/{id}/guests/`	the guest list + RSVP responses (delivery status, views, short links)
`evite_rsvp_summary`	(derived from guests)	just the RSVP summary (yes/no/maybe/noReply + head counts)
`evite_list_messages`	`GET /services/event/v1/{id}/posts/`	the event's Messages thread
`evite_list_templates`	scrapes `/invites/{category}/`	invitation template slugs (the `template_name` `evite_create_event` needs) + display names

Tool	Endpoint	Action
`evite_rsvp`	`PUT /services/event/v1/{id}/guests/{guestId}`	RSVP for a guest (response + adult/kid head counts + optional note)
`evite_send_message`	`POST /tsunami/v1/services/event/{id}/guest/{gid}/messages`	send a private message to one guest (body assumed)
`evite_broadcast`	`POST /tsunami/v1/services/event/{id}/broadcast/`	broadcast a message to whole RSVP segments (`virtual_groups`) at once
`evite_upload_photo`	`POST …/photos/v1/{id}/upload/request/` → GCS → finish → shared-gallery	upload a local image to the event's shared photo album (4-step GCS signed upload)
`evite_create_event`	`POST /services/event/v1/` (`{event:{…}}`)	create an event draft (needs `template_name`; the API 500s even on success)
`evite_update_event`	`PATCH /services/event/v1/{id}` (`{event:{…}}`)	edit an event (only the fields you pass change)
`evite_add_guest`	`POST /ajax/event/{id}/guestlist/draft/`	add guests to the draft (un-sent) list — `[{name,email}]`
`evite_update_guest`	`PATCH /ajax/event/{id}/guestlist/draft/`	edit a draft guest's name/email/phone
`evite_remove_guest`	`DELETE /ajax/event/{id}/guestlist/draft/{gid}`	remove a draft guest
`evite_send`	`POST /services/event/v1/{id}/send/`	"Send now" — emails the ready-to-send guests
`evite_cancel_event`	`POST …/actions/cancel/`	cancel an event / delete a draft (destructive; reversible)
`evite_reinstate_event`	`POST …/actions/reinstate/`	reinstate a cancelled event
`evite_duplicate_event`	`GET /plus/create/{id}/copy/` (→302)	copy an event into a fresh draft; returns the new event id

variable	default
`MCP_CONFIRM_MODE`	`ask-user`	What a write does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). `ask-user`: two steps — the first call writes nothing and returns a preview plus a token, and the model must get your approval in chat before calling again with it. `auto`: the same two steps, but the model may use the token after reviewing the preview itself. `refuse`: writes are refused on such clients. A client that can show prompts (Claude Code) always gets the real prompt, unless `MCP_CONFIRM_ELICITATION=off`. An unrecognised value is treated as `refuse`.
`MCP_CONFIRM_ELICITATION`	`on`	`off` never shows a confirmation prompt, so every client gets the `MCP_CONFIRM_MODE` behaviour. Set it for a client that says it can show prompts but never does (the write hangs — opencode 2.0.x). Any other value is treated as `on`, with a warning on stderr.
`MCP_CONFIRM_TTL_SECONDS`	`600`	How long a token stays valid.
`MCP_CONFIRM_SECRET`	random per process	Signing key; set it only if tokens must survive a server restart.

Diesen Server hinzufügen

Host a copy with our keys and logs.

Server-Details

Dokumentation

evite-mcp

Tools

Write tools (confirmed)

Confirmations

Photo uploads

Architecture

Development

Docs & roadmap

License

Evite

Tools

Fragen

Wie installiere ich Evite?

Benötigt Evite einen API-Schlüssel?

Welchen Transport verwendet Evite?

Wann wurde Evite zuletzt geprüft?