360 Secure SkillHub
360 安全技能中心

evite

封装 evite-mcp MCP 服务器,让用户以嘉宾或主办方身份浏览 Evite 活动、查看嘉宾名单与 RSVP 统计、回复邀请、给嘉宾发消息,以及创建/编辑/取消/复制活动。写操作先返回预览与一次性 confirmToken,需用户确认后再次调用才执行。需提供 Evite 邮箱密码或会话 Cookie。

chrischall
chrischall
热度 63.81
最近更新 2026-10-10 07:30:23
分类:生活依赖:MCP 服务 / 第三方 API / 代码执行应用场景:日程安排 / 任务管理

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add evite
Metadata
name
evite
description
This skill should be used when the user asks about Evite events or invitations. Triggers on phrases like "check Evite", "my Evite events", "who RSVP'd", "Evite guest list", "RSVP to the party", "message my Evite guests", "create an Evite invite", or any request involving event invitations, guest lists, RSVPs, or party/event hosting on evite.com.

evite-mcp

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

Setup

Option A — Claude Code (direct MCP)

Add to .mcp.json in your project or ~/.claude/mcp.json:

{
  "mcpServers": {
    "evite": {
      "command": "npx",
      "args": ["-y", "evite-mcp"],
      "env": {
        "EVITE_EMAIL": "you@example.com",
        "EVITE_PASSWORD": "yourpassword"
      }
    }
  }
}

Option B — global install

npm install -g evite-mcp

Auth

The server resolves a session in priority order (see the README for details):

  1. EVITE_EMAIL + EVITE_PASSWORD — headless email/password login (preferred).
  2. EVITE_SESSION_COOKIE — a raw cookie: header copied from a signed-in evite.com tab.
  3. Fetchproxy bootstrap — lifts session cookies from a signed-in evite.com browser tab. Opt out with EVITE_DISABLE_FETCHPROXY=1.

Tools

Read (6 + healthcheck): evite_list_events, evite_get_event, evite_list_guests, evite_rsvp_summary, evite_list_messages, evite_list_templates, evite_healthcheck.

Write (asks you to confirm first): evite_rsvp, evite_send_message, evite_broadcast, evite_create_event, evite_update_event, evite_add_guest, evite_update_guest, evite_remove_guest, evite_send, evite_cancel_event, evite_reinstate_event, evite_duplicate_event.

Every write tool asks the user to confirm before it sends anything: a confirmation prompt where the client supports one (unless the server sets MCP_CONFIRM_ELICITATION=off); otherwise the first call makes no write (at most a read-only lookup, e.g. evite_update_guest reads the draft guest list to build its preview) and returns a preview of exactly what would be sent plus a confirmToken (see MCP_CONFIRM_MODE). Show the user that preview and get their approval in chat, then call the same tool again with the same arguments plus confirmToken. The token is single-use and bound to those exact arguments — change anything and it is refused (DRAFT_CHANGED) with a fresh preview and token. The authoring flow is evite_create_event → evite_add_guest → evite_send.