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