Happenings

social.happeningsv1.1.0更新於 Oct 14, 2026

Run your Happenings page from your AI: events, tickets, sales, members, posts and articles.

發布方自己的服務：Happenings Page CLI

已驗證Streamable HTTP可網頁執行效率與工作流商業與電商

概覽

AI 產生的概覽

遠端 MCP 連接器，讓 AI 助理讀取並經營 Happenings 主辦方頁面：活動、票務、銷售、會員、貼文與文章。

可以做什麼
  • 透過唯讀工具檢視活動、票務、銷售、會員、貼文與文章等頁面資料
  • 透過 hap_run 工具執行頁面層級的 Happenings 指令，權限受使用者在各頁面的角色限制
  • 透過 hap_help 取得可用指令的說明
  • 可同時操作已登入主辦方管理的多個頁面
適用情境
適合已在 Happenings 經營頁面的主辦方，希望助理在對話中查看銷售、會員或活動狀況，或直接完成頁面操作。若沒有 Happenings 頁面則無需安裝。
執行需求
遠端 streamable HTTP 端點，不需本機套件或執行環境。登入採用 OAuth 2.1（PKCE 與動態用戶端註冊），用戶端需支援帶 OAuth 的遠端 MCP 連接器。需要具備目標頁面角色的 Happenings 主辦方帳號。
安裝前請注意
hap_run 工具不只讀取，也可能變更頁面資料，操作範圍受你在各頁面的角色限制。登入後助理可存取你選定的頁面，請確認所選頁面。README 指出此登錄項目已被新的 Happenings Connect 項目取代。

安裝

在 SourceWeft 中

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

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/social.happenings%2Fpage-tools/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "happenings": {
      "type": "http",
      "url": "https://api.happenings.social/mcp"
    }
  }
}

README

Happenings for your AI

Connects any MCP-capable AI to the Happenings pages an organiser runs, and teaches it how to run a page well (HAP-4513). Organisers set it up from Connect, under Settings, then AI (/beta/settings/ai).

The two parts

  • The connector: https://api.happenings.social/mcp. The page-level Happenings CLI as a remote MCP server (streamable HTTP), behind OAuth 2.1 with PKCE, dynamic client registration and RFC 9207 iss. Adding it takes only the URL; signing in picks the pages, and every command stays limited by the person's role on each page. Tools: hap_help and hap_read (read-only) and hap_run.
  • The skill: skill/happenings.md is the single source. node build.mjs generates every client's copy from it; a backoffice test fails when one is stale.

Per client

ClientConnectorSkill
Claude (web, Desktop, app)URL: Customize, Connectors, Add custom connector. Team/Enterprise: an owner adds it under Organization settings, ConnectorsDownload happenings-skill.zip, upload under Customize, Skills
ChatGPTURL: Settings, Apps and connectors, Advanced settings, Developer mode, Create (paid plans)Copy chatgpt-instructions.txt into a project or custom GPT
Claude Codeclaude mcp add --transport http happenings https://api.happenings.social/mcpmkdir -p ~/.claude/skills/happenings && curl -fsSL https://connect.happenings.social/downloads/ai/SKILL.md -o ~/.claude/skills/happenings/SKILL.md, or both in one: the plugin below
CursorInstall link cursor://anysphere.cursor-deeplink/mcp/install?name=happenings&config=…, or ~/.cursor/mcp.json.cursor/rules/happenings.mdc
VS Code (Copilot)Install link vscode:mcp/install?…, or .vscode/mcp.json with "type": "http"Append AGENTS.md
Windsurf~/.codeium/windsurf/mcp_config.json with serverUrlAppend AGENTS.md
Gemini CLIgemini mcp add --transport http happenings https://api.happenings.social/mcpAppend GEMINI.md to ~/.gemini/GEMINI.md, or both in one: the extension below
Codex CLIcodex mcp add happenings --url https://api.happenings.social/mcp, then codex mcp login happeningsAppend AGENTS.md to ~/.codex/AGENTS.md

Every client above uses the remote URL with OAuth; none needs a local stdio fallback. OAuth callbacks allowlisted for them: Claude (https://claude.ai/api/mcp/auth_callback), ChatGPT (https://chatgpt.com/connector_platform_oauth_redirect and /connector/oauth/{id}), VS Code (https://vscode.dev/redirect, https://insiders.vscode.dev/redirect), Cursor's fallback (cursor://anysphere.cursor-mcp/oauth/callback) and loopback (http://localhost:*, 127.0.0.1) for Cursor, Claude Code, Gemini CLI, Codex and Windsurf.

Bundles (one step for both)

This folder is laid out to be published as its own public repository, which serves two bundles at once:

  • Claude Code plugin marketplace: .claude-plugin/marketplace.json and plugins/happenings (the .mcp.json connector, the skill and four commands: /happenings:this-week, :sales, :new-event, :members). claude plugin marketplace add <owner>/<repo> && claude plugin install happenings@happenings

  • Gemini CLI extension: gemini-extension.json and GEMINI.md. gemini extensions install https://github.com/<owner>/<repo>

  • Claude plugin as a file: happenings-plugin.zip, built by build.mjs from plugins/happenings and served by Connect at /downloads/ai/happenings-plugin.zip. One download holds the connector (.mcp.json), the skill and the four commands, for adding in Claude without a terminal. It is hosted on our own site and does not depend on the public repository. Connect shows it as "Both in one step" when Claude is picked. The public site serves the same bytes at /skills/happenings-plugin.zip (web/apps/user-web/scripts/sync-skills.mjs copies it at build time) and links it from /mcp and /guide/mcp.

The monorepo is private, so the first two work only from the published copy of this folder. Set HAPPENINGS_AI_REPO=<owner>/<repo> on the backoffice Worker and Connect shows both commands; until then it shows the separate connector and skill steps.

A Claude Desktop extension (.mcpb) is not built: Desktop already takes the remote connector by URL, and .mcpb targets local servers.

MCP Registry

Happenings Connect is listed in the official MCP Registry (registry.modelcontextprotocol.io) as social.happenings/connect (https://api.happenings.social/mcp); the entry is registry/connect.server.json. Directories that read the registry pick it up from there. The earlier entries social.happenings/page-tools and social.happenings/page-cli are deprecated: /mcp became Happenings Connect on 2026-10-14 and /page/mcp is its former address. The operator connector is not listed.

The social.happenings namespace is proven by a TXT record on happenings.social (v=MCPv1; k=ed25519; p=…). The private key was not kept. To publish a change, bump version in the entry, then:

bash
openssl genpkey -algorithm Ed25519 -out key.pem   # OpenSSL 3, not LibreSSLopenssl pkey -in key.pem -pubout -outform DER | tail -c 32 | base64# replace the p= value of the MCPv1 TXT record in Cloudflare with that outputmcp-publisher login dns --domain happenings.social \  --private-key "$(openssl pkey -in key.pem -noout -text | grep -A3 'priv:' | tail -n +2 | tr -d ' :\n')"mcp-publisher publish registry/connect.server.jsonrm key.pem

Editing the skill

  1. Edit skill/happenings.md.
  2. node integrations/ai/build.mjs
  3. Commit the regenerated files (here and in web/apps/backoffice/public/downloads/ai/).

The same applies after editing a plugin command or manifest, since the plugin zip is built from them. A new command file must be added to PLUGIN_SOURCE_FILES in variants.mjs; a test fails if it is not. Bump version in plugins/happenings/.claude-plugin/plugin.json and .claude-plugin/marketplace.json together when the plugin changes.

來源：README.md，提交 e498045

工具

0
SourceWeft 尚未讀取此伺服器的工具。

版本歷史

1
  1. v1.1.0最新Oct 14, 2026

評分

已滿足適用檢查項的 40%

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

  • 近 30 天內可連通必需25 分

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

  • 已宣告認證方式必需10 分

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

  • 已列出工具15 分

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

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

    請在儲存庫或註冊中心條目中宣告授權條款。

其他 Happenings 整合

Happenings Page CLI

social.happenings官方發布者

遠端 MCP 連接器，讓 AI 助理使用 Happenings 頁面管理 CLI，僅限主辦方所選頁面及其角色權限。

Streamable HTTP可網頁執行驗證方式
效率與工作流需要憑證Oct 24, 2026

Happenings Connect

social.happenings官方發布者

遠端 MCP 伺服器，讓 AI 在使用者於各頁面的角色範圍內經營主辦方的 Happenings 頁面，涵蓋活動、票務、銷售與會員。

Streamable HTTP可網頁執行驗證方式
效率與工作流需要憑證Oct 24, 2026