프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. 리뷰와 계정 기능은 다음 단계에서 열려요.
PopNx MCPAI를 쓰는 사람을 위한 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

비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.

필요한 것

  • npmNode.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는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

  • 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

  • 이 카테고리의 다른 서버 32683개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 32683개 중 92%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 32683개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

Evite MCP, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

입력해야 할 값: EVITE_PASSWORD, EVITE_SESSION_COOKIE

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.4.0)은 그저께 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, MCP Server Autocad Lisp Helper

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ 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그저께 업데이트
설치

MCP Server Autocad Lisp Helper

제작자: radwanalmsora

High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.

내 컴퓨터에서 실행오늘 업데이트
설치

제작자의 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에게 묻기