lu

io.github.adelaidasofia由 GitHub 帳號 adelaidasofia 發布v0.1.0更新於 Oct 24, 2026

lu.ma events MCP server with draft+confirm safety, audit logging, and prompt-injection scrubbing.…

概覽

AI 產生的概覽

讓助理管理 lu.ma 活動:建立與更新活動、設定票價、發放優惠碼、查看報名名單並寄信給參與者,寫入採用草稿加確認機制。

可以做什麼
  • 檢查驗證狀態與草稿儲存狀況,並取消未確認的草稿
  • 讀取活動:依 ID 取得單一活動,或分頁列出某個日曆下的活動
  • 建立與更新活動,包含名稱、日期、時區、容量、會議連結、可見度與封面圖片
  • 設定票種與價格,發放日曆層級或活動層級的優惠碼,支援百分比或固定金額折扣
  • 依狀態篩選列出活動嘉賓與報名紀錄,並列出優惠碼
  • 起草並寄送給參與者的 Markdown 郵件,例如課前準備、當天提醒或後續追蹤
適用情境
適合在 lu.ma 上舉辦活動、希望助理在對話中準備活動頁面、定價與優惠碼、匯出嘉賓名單或寄送參與者郵件的情境。所有寫入都先進入草稿,適合需要人工逐項確認後才正式發布的流程。
執行需求
以本機程序執行,僅支援桌面端,可透過 MCP 打包檔或外掛市集安裝。所用日曆需要 Luma Plus 訂閱,因為公開 API 僅對 Plus 開放;另需在 Luma 設定中產生 API 金鑰,並以 LUMA_API_KEY 環境變數提供。需要連線至 Luma 公開 API 的網路,該 API 限制為每個日曆每分鐘 200 次請求。
安裝前請注意
需要一組對日曆有寫入權限的 Luma API 金鑰,從 LUMA_API_KEY 環境變數讀取並存放在本機 .env 檔案中。確認後的寫入會建立或修改活動、票價、優惠碼,並向參與者寄送真實郵件,請逐筆核對草稿後再確認。本機會記錄 API 呼叫稽核日誌,並對權杖做遮蔽處理。外掛首次載入時會向第三方網站送出一次匿名安裝訊號,除非設定 MYCELIUM_NO_PING。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 lu,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

luma-mcp

[License] [GitHub stars] [Last commit] [Open issues] [PyPI version] [PyPI downloads] [Built by Mycelium AI]

lu.ma events MCP server. Create events, set ticket prices, issue coupon codes, list RSVPs, and email attendees. All writes go through draft+confirm so nothing posts to Luma until you explicitly approve. Built on the official Luma public API.

What it does

  • Create + update lu.ma events (name, date, timezone, capacity, meeting URL, visibility, cover image)
  • Set ticket types and pricing
  • Issue coupon codes (calendar-scoped or event-scoped, percentage or fixed-cents discounts, redemption caps)
  • List event guests / RSVPs
  • Send markdown emails to attendees (pre-work, day-of, follow-up)
  • Audit log of every API call (JSONL with key/token redaction)
  • Prompt-injection scrubber on user-supplied free-text fields

Tools (v0.1.0)

Reads (call API directly):

  • luma_health — auth check + draft store size
  • luma_get_event — fetch one event by ID
  • luma_list_events — paginated calendar listing
  • luma_list_event_guests — RSVPs filtered by status
  • luma_list_coupons — calendar or event-scoped

Writes (draft+confirm pairs):

  • luma_create_event_draft / luma_create_event_confirm
  • luma_update_event_draft / luma_update_event_confirm
  • luma_create_ticket_type_draft / luma_create_ticket_type_confirm
  • luma_create_coupon_draft / luma_create_coupon_confirm
  • luma_send_event_email_draft / luma_send_event_email_confirm

Plus:

  • luma_cancel_draft — cancel an unconfirmed draft (idempotent)

14 tools total.

Architecture

luma-mcp/├── pyproject.toml├── README.md├── SETUP.md├── LICENSE├── .env.example├── luma_mcp/│   ├── __init__.py│   ├── server.py             FastMCP entry point + .env loader│   ├── client.py             HTTP wrapper around api.lu.ma/public/v1│   ├── drafts.py             Thread-safe draft store with TTL│   ├── audit.py              JSONL audit log with redaction│   ├── scrubber.py           Prompt-injection neutralizer│   ├── _shared/              Day-1 shared utilities│   │   ├── normalize.py      Timezone alias + datetime helpers│   │   └── types.py          Permissive typed shapes for API responses│   └── tools/│       ├── health.py         luma_health, luma_cancel_draft│       ├── events.py         create / update / get / list events│       ├── tickets.py        create ticket types│       ├── coupons.py        create / list coupons│       ├── guests.py         list event guests│       └── emails.py         send email to attendees└── tests/integration/    └── test_full_pipeline.py 10-step bare-runnable verification

Safety patterns

  1. Draft + confirm on every write. The draft tool returns a draft_id; nothing hits Luma until the matching confirm tool is called. Drafts expire after 1 hour and can only be confirmed once.
  2. Audit log. Every API call is logged JSONL with ts, tool, action, args (redacted), status, latency_ms. Path: ~/.claude/luma-mcp/audit.log.
  3. Token redaction. Strings matching long-key heuristics, or values under keys like api_key, token, cookie, secret, are masked before logging.
  4. Prompt-injection scrubber. User-supplied free-text fields (event name, description, email subject, email body) are passed through unicodedata.normalize("NFKC"), stripped of zero-width characters, and have role-spoof prefixes / fake fences wrapped in backticks (preserving operator visibility, neutralizing model effect on downstream reads).
  5. Zero LLM in the tool path. Every routing decision is rule-based.

Use cases

  • Workshops + paid events — set sticker price, issue community-specific 100%-off coupons, pull guest list, blast pre-work email.
  • Multi-event programs — one cohorte announcement, sub-events on Luma, pull RSVPs across sessions.
  • Recurring meetups — duplicate event template via update_event_draft, change date, ship.

Install

Open Claude Code, paste:

/plugin marketplace add adelaidasofia/luma-mcp/plugin install luma-mcp@luma-mcp

Two prerequisites for the server to authenticate:

  1. Luma Plus subscription on the calendar you'll use (the public API is gated behind Plus).
  2. API key generated from https://lu.ma/settings/api, dropped into ~/.claude/luma-mcp/.env as LUMA_API_KEY=....

After both steps, restart Claude Code. Tools appear under mcp__luma__*.

Legacy install

See SETUP.md for the manual .mcp.json registration path. The plugin install above replaces it.

Verification

bash
cd ~/.claude/luma-mcp && python3 tests/integration/test_full_pipeline.py# expected: PASSED — luma-mcp v0.1.0 integration test (10 steps green)

Then in a Claude Code session: mcp__luma__luma_health() → {ok: true, user: {...}}.

Rate limit

Luma's public API caps at 200 requests / minute / calendar. The client does not auto-retry on 429; it surfaces the error and lets the operator pace.

Related MCPs

Same author, same architecture pattern (FastMCP, draft+confirm on writes, vault auto-export where applicable):

Telemetry

This plugin sends a single anonymous install signal to myceliumai.co the first time it loads in a Claude Code session on a given machine.

What is sent:

  • Plugin name (e.g. slack-mcp)
  • Plugin version (e.g. 0.1.0)

What is NOT sent:

  • No user identifiers, names, emails, tokens, or API keys
  • No file paths, message content, or anything from your work
  • No IP address is stored after dedup processing

Why: Helps the maintainer know which plugins people actually install, so attention goes to the ones that get used.

Opt out: Set the environment variable MYCELIUM_NO_PING=1 before launching Claude Code. The hook will skip the network call entirely. Already-pinged installs leave a sentinel at ~/.mycelium/onboarded-<plugin> — delete it if you want to reset state.

License

MIT. See LICENSE.

來源:README.md,提交 9c9afdc

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.0最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分