Evite कैसे इंस्टॉल करें?

इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।

क्या Evite के लिए API key चाहिए?

इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।

Evite कौन सा ट्रांसपोर्ट इस्तेमाल करता है?

Evite stdio पर लोकल चलता है।

Evite की पिछली जाँच कब हुई थी?

पिछली जाँच 2026-11-13 को हुई। Evite MCP server for Claude — list events, guest lists & RSVPs, RSVP, message guests, and create/edit events.

Evite MCP सर्वर

Power your agent

यह सर्वर जोड़ें

पब्लिशर की अपनी कमांड। PlugMCP एंडपॉइंट नहीं।

Cursor में जोड़ें VS Code में जोड़ें PlugMCP पर चलाएँ

Host a copy with our keys and logs.

लोकल कमांड

npx -y [email protected]

Claude Code में लोकल कमांड के लिए इंस्टॉल लिंक नहीं है। नीचे दी गई कमांड कॉपी करें और टर्मिनल में चलाएँ।

shClaude Code

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

टर्मिनल में चलाएँ।

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

लोकल · npmपब्लिशर इंस्टॉलचरण-दर-चरण: इसे Claude में जोड़ें

रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है

PlugMCP पर चलाएँ

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.

लॉन्च

सर्वर की जानकारी

लोकल

ट्रांसपोर्ट: stdio
वर्शन: 1.5.0
पिछली जाँच

पब्लिशर से

डॉक्यूमेंटेशन

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.

यह सर्वर जोड़ें

Host a copy with our keys and logs.

सर्वर की जानकारी

डॉक्यूमेंटेशन

evite-mcp

Tools

Write tools (confirmed)

Confirmations

Photo uploads

Architecture

Development

Docs & roadmap

License

Evite

टूल

सवाल

Evite कैसे इंस्टॉल करें?

क्या Evite के लिए API key चाहिए?

Evite कौन सा ट्रांसपोर्ट इस्तेमाल करता है?

Evite की पिछली जाँच कब हुई थी?