原型 · 预览版：收录官方注册中心里的全部服务器，每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚
新手模式 关
配色跟随系统浅色深色
语言ไทยEnglish中文日本語한국어EspañolDeutsch
☰ 菜单设置
新手模式 关
配色跟随系统浅色深色
语言ไทยEnglish中文日本語한국어EspañolDeutsch

Evite MCP

作者：chrischall版本 1.4.0i★ –i在你的电脑上运行
注册名称io.github.chrischall/evite-mcp

安装

概览

作者提供的说明（英文原文）

Evite for Claude — list events, guest lists & RSVPs, RSVP, message guests, and create/edit events

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他
  • 你需要填写：EVITE_PASSWORD, EVITE_SESSION_COOKIE

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

  • 基础检查：1 项中通过 1 项
  • 在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
  • 需要你自己填写： EVITE_EMAIL, EVITE_PASSWORD, EVITE_SESSION_COOKIE, EVITE_SESSION_CACHE, EVITE_SESSION_FILE, EVITE_DISABLE_FETCHPROXY, EVITE_UPLOAD_DIR, FETCHPROXY_WS_PORT, FETCHPROXY_WS_HOST, FETCHPROXY_IDENTITY_DIR

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

  • npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "evite": {
      "command": "npx",
      "args": [
        "-y",
        "evite-mcp"
      ],
      "env": {
        "EVITE_EMAIL": "your-value",
        "EVITE_PASSWORD": "your-value",
        "EVITE_SESSION_COOKIE": "your-value",
        "EVITE_SESSION_CACHE": "your-value",
        "EVITE_SESSION_FILE": "your-value",
        "EVITE_DISABLE_FETCHPROXY": "your-value",
        "EVITE_UPLOAD_DIR": "your-value",
        "FETCHPROXY_WS_PORT": "your-value",
        "FETCHPROXY_WS_HOST": "your-value",
        "FETCHPROXY_IDENTITY_DIR": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add evite --env EVITE_EMAIL=your-value --env EVITE_PASSWORD=your-value --env EVITE_SESSION_COOKIE=your-value --env EVITE_SESSION_CACHE=your-value --env EVITE_SESSION_FILE=your-value --env EVITE_DISABLE_FETCHPROXY=your-value --env EVITE_UPLOAD_DIR=your-value --env FETCHPROXY_WS_PORT=your-value --env FETCHPROXY_WS_HOST=your-value --env FETCHPROXY_IDENTITY_DIR=your-value -- npx -y evite-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "evite": {
      "command": "npx",
      "args": [
        "-y",
        "evite-mcp"
      ],
      "env": {
        "EVITE_EMAIL": "your-value",
        "EVITE_PASSWORD": "your-value",
        "EVITE_SESSION_COOKIE": "your-value",
        "EVITE_SESSION_CACHE": "your-value",
        "EVITE_SESSION_FILE": "your-value",
        "EVITE_DISABLE_FETCHPROXY": "your-value",
        "EVITE_UPLOAD_DIR": "your-value",
        "FETCHPROXY_WS_PORT": "your-value",
        "FETCHPROXY_WS_HOST": "your-value",
        "FETCHPROXY_IDENTITY_DIR": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "evite": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "evite-mcp"
      ],
      "env": {
        "EVITE_EMAIL": "your-value",
        "EVITE_PASSWORD": "your-value",
        "EVITE_SESSION_COOKIE": "your-value",
        "EVITE_SESSION_CACHE": "your-value",
        "EVITE_SESSION_FILE": "your-value",
        "EVITE_DISABLE_FETCHPROXY": "your-value",
        "EVITE_UPLOAD_DIR": "your-value",
        "FETCHPROXY_WS_PORT": "your-value",
        "FETCHPROXY_WS_HOST": "your-value",
        "FETCHPROXY_IDENTITY_DIR": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

  • EVITE_EMAIL env
    Your Evite login email address. Optional — if omitted, the server falls back to a raw session cookie or the fetchproxy browser bridge (requires being signed in to evite.com).
  • EVITE_PASSWORD 机密 env
    Your Evite password. Optional — see EVITE_EMAIL.
  • EVITE_SESSION_COOKIE 机密 env
    A raw `cookie:` header copied from a signed-in evite.com tab (alternative to email/password). Used verbatim. Optional.
  • EVITE_SESSION_CACHE env
    Set to false to disable the on-disk session cache and re-authenticate on every process start. Defaults to enabled.
  • EVITE_SESSION_FILE env
    Absolute path for the session cache file. Defaults to $MCP_DATA_DIR/.evite-mcp/session.json.
  • EVITE_DISABLE_FETCHPROXY env
    Set to true to disable the fetchproxy browser bridge. With the bridge disabled you MUST provide EVITE_EMAIL/EVITE_PASSWORD or EVITE_SESSION_COOKIE. Defaults to false.
  • EVITE_UPLOAD_DIR env
    Optional. Restrict evite_upload_photo to image files inside this directory (several may be separated by the path delimiter, `:` on macOS/Linux; `~` allowed). A path outside it is refused before anyth…
  • FETCHPROXY_WS_PORT env
    Localhost port of the fetchproxy concentrator the ContextMint Bridge extension connects to (default 37149). Every MCP on one machine shares it, so move it for all of them or not at all.
  • FETCHPROXY_WS_HOST env
    Bind interface for the fetchproxy concentrator, a literal IP only (default 127.0.0.1). Keep on loopback; it exists for hosted deployments that run each MCP in its own network namespace.
  • FETCHPROXY_IDENTITY_DIR env
    Absolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/).

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 chrischall 验证，该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行，没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行，改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 18323 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 18323 个服务器的 93% 更新
  • 基础检查结果等于或优于此分类中其他 18323 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Evite MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：EVITE_PASSWORD, EVITE_SESSION_COOKIE

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.4.0）于3天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Date Math

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新
安装

Date Math

作者：JowenDelaPena

Exact date/time math for agents: business days, holidays, time zones, cron, RRULE, SLA. x402 paid.

在云端运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

evite-mcp

A Model Context Protocol 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. Built on @chrischall/mcp-utils.

Status: read + write tools live. The five read tools work against Evite's internal API, authenticating from email/password (tier-1, POST /ajax_login), a raw cookie env var, or a signed-in browser tab (fetchproxy bootstrap). The thirteen write tools ask you to confirm first — nothing is sent until you approve (see Confirmations) — and their endpoints are live-verified (see docs/EVITE-API.md); a couple of request *bodies* are still assumed rather than captured (#3).

Tools

Six read tools (all read-only), thirteen confirmed write tools, evite_upload_slots (read-only: upload links for photos on the hosted connector), plus evite_healthcheck:

ToolEndpointReturns
evite_list_eventsGET /services/events/v1/your events + a totals breakdown (filterBy = all/host/others, repeatable status, offset/numResults paging)
evite_get_eventGET /services/event/v1/{id}single-event detail (event, settings, location)
evite_list_guestsGET /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_messagesGET /services/event/v1/{id}/posts/the event's Messages thread
evite_list_templatesscrapes /invites/{category}/invitation template slugs (the template_name evite_create_event needs) + display names
Write tools (confirmed)

Every write tool asks you to confirm before it sends anything. A client that can show a confirmation prompt (Claude Code) shows one with the exact values that would be sent (unless MCP_CONFIRM_ELICITATION=off). Elsewhere (claude.ai, Claude Desktop) the first call performs no write (at most a read-only lookup — e.g. evite_update_guest reads the draft guest list to build an exact preview) and returns that preview plus a confirmToken; only a repeat call with the token performs the write. The token is single-use, expires, and is bound to the tool and the exact values — change anything and it is refused (DRAFT_CHANGED) with a fresh preview. See Confirmations. Endpoints are verified; the CSRF token (X-CSRFToken, read fresh per request as it rotates) is attached centrally.

ToolEndpointAction
evite_rsvpPUT /services/event/v1/{id}/guests/{guestId}RSVP for a guest (response + adult/kid head counts + optional note)
evite_send_messagePOST /tsunami/v1/services/event/{id}/guest/{gid}/messagessend a private message to one guest (body assumed)
evite_broadcastPOST /tsunami/v1/services/event/{id}/broadcast/broadcast a message to whole RSVP segments (virtual_groups) at once
evite_upload_photoPOST …/photos/v1/{id}/upload/request/ → GCS → finish → shared-galleryupload a photo to the event's shared photo album (4-step GCS signed upload) — from a local path, inline base64, or an upload-slot blob_key (see Photo uploads)
evite_create_eventPOST /services/event/v1/ ({event:{…}})create an event draft (needs template_name; the API 500s even on success)
evite_update_eventPATCH /services/event/v1/{id} ({event:{…}})edit an event (only the fields you pass change)
evite_add_guestPOST /ajax/event/{id}/guestlist/draft/add guests to the draft (un-sent) list — [{name,email}]
evite_update_guestPATCH /ajax/event/{id}/guestlist/draft/edit a draft guest's name/email/phone
evite_remove_guestDELETE /ajax/event/{id}/guestlist/draft/{gid}remove a draft guest
evite_sendPOST /services/event/v1/{id}/send/"Send now" — emails the ready-to-send guests
evite_cancel_eventPOST …/actions/cancel/cancel an event / delete a draft (destructive; reversible)
evite_reinstate_eventPOST …/actions/reinstate/reinstate a cancelled event
evite_duplicate_eventGET /plus/create/{id}/copy/ (→302)copy an event into a fresh draft; returns the new event id

The authoring flow is evite_create_event → evite_add_guest → evite_send. evite_send, evite_send_message, evite_broadcast, and evite_cancel_event have real-world effects (emails / cancellation notices), so their confirmation matters.

Confirmations

variabledefault
MCP_CONFIRM_MODEask-userWhat 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_ELICITATIONonoff 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_SECONDS600How long a token stays valid.
MCP_CONFIRM_SECRETrandom per processSigning key; set it only if tokens must survive a server restart.

Photo uploads

evite_upload_photo takes the image as exactly one of three inputs (JPEG/PNG/GIF/WebP/HEIC, max 20 MB; the bytes must really be that image type, whatever the name says):

  • `path` — local installs only. A file inside EVITE_UPLOAD_DIR (below).
  • `inline` — { filename, content_base64 }. Works anywhere; meant for a small photo, since every byte rides inside the tool call.
  • `blob_key` — the hosted connector's way in. It cannot read files on your machine, so a path is refused there with directions. Instead, call evite_upload_slots with the filenames; each slot has a signed uploadUrl and a ready curl command that PUTs the file with the exact Content-Type. Then pass the slot's blobKey as blob_key. The upload is read on the preview and again on confirm, and its SHA-256 is bound into the confirmation, so a file replaced in between is refused (DRAFT_CHANGED). It is deleted only after Evite accepts the photo (the result's blob says whether that delete worked). If the upload fails it is kept, so a retry can reuse the same blob_key. evite_upload_slots refuses on a local install, which has no blob store.
variabledefault
EVITE_UPLOAD_DIR~/Downloads/evite-mcpThe directories evite_upload_photo may read from — one or more, separated by the platform path delimiter (: on macOS/Linux, ; on Windows); ~ is allowed. A relative path is resolved against the first one. A path outside them (symlinks included), or a hidden file or directory inside them, is refused before the file is even looked at. Put photos to upload in ~/Downloads/evite-mcp, or point this elsewhere.

Architecture

Fetchproxy-archetype MCP. Evite has no public API, so the server calls Evite's *internal* /services/ web API using your session. src/auth.ts resolves that session in priority order:

  1. `EVITE_EMAIL` + `EVITE_PASSWORD` (tier-1, preferred) — headless email/password form login: POST the creds to https://www.evite.com/ajax_login, then build the session from the response Set-Cookie jar (x-evite-session, evtsession, csrftoken, x-evite-features). No browser bridge, no hand-copied cookie. Both vars must be set, or the resolver falls through. *(Live.)*
  2. `EVITE_SESSION_COOKIE` — a raw cookie: header copied from a signed-in evite.com tab (or set in CI). Used verbatim. *(Live.)*
  3. Fetchproxy bootstrap (fallback) — lift the session cookies (x-evite-session, evtsession, x-evite-features, csrftoken) from a signed-in evite.com browser tab via @fetchproxy/bootstrap, which needs the ContextMint Bridge browser extension (Chrome: load the chrome zip from the releases page unpacked. Safari isn't available yet — it will ship inside the ContextMint app, which has no public download — so use Chrome for now). ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README points to it. Its source is public at nullnet-app/contextmint-bridge: build it yourself, or check a release zip against the .sha256 file published beside it (shasum -a 256 -c contextmint-bridge-chrome- .zip.sha256). Bootstrap runs once; every API call then goes out via plain Node fetch() with the cookies attached. Opt out with EVITE_DISABLE_FETCHPROXY=1. *(Live.)*

One tier is intentionally deferred (the resolver is shaped to slot it in):

  • Fetchproxy as transport (bot-wall retry through the browser bridge) — a fallback only needed if plain fetch trips a wall; not observed during discovery.

The thirteen write tools (rsvp, add/update/remove-guest, send, send-message, broadcast, upload-photo, create/update/cancel/reinstate/duplicate event) ask you to confirm first (a prompt, or a preview + single-use confirmToken; see Confirmations). The single private client.write() helper attaches the CSRF token via one centralized header (CSRF_HEADER = X-CSRFToken; the csrftoken cookie rotates mid-session, so it's read fresh per request). Endpoints span three bases — REST /services/…, the legacy /ajax/event/{id}/… guest list, and the /tsunami/… messaging service — all live-verified; a couple of request bodies remain assumed (#3).

Development

npm install      # resolves @chrischall/mcp-utils from a local tarball (see issue #4)

npm run build npm test

Docs & roadmap

  • Design spec: docs/superpowers/specs/2026-05-31-evite-mcp-design.md
  • Plan 1 (scaffold + spike): docs/superpowers/plans/2026-05-31-evite-mcp-scaffold-and-spike.md
  • Plan 2 (auth + read tools): docs/superpowers/plans/2026-05-31-evite-mcp-auth-and-reads.md
  • Internal API reference (verified from a live session): docs/EVITE-API.md

Open work: #3 — write endpoints + CSRF are now live-verified; only a couple of request *bodies* (send / send-message) remain assumed. #4 tracks publishing the shared lib. (Discovery #1, tier-1 email/password login #2, and the read tools are done.)

License

MIT

问 PopNx