Happenings Page CLI MCP server
Commit Nov 12, 2026Connects AI clients to Happenings pages to manage organizer commands and page content through a remote MCP server.
Also known as happenings-dk/happenings-ai, page-cli
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.1.0
- Last commit
- Nov 12, 2026
- License
- —
What is Happenings Page CLI MCP?
Happenings Page CLI connects AI clients to Happenings pages to manage organizer commands and page content through a remote MCP server.
Summary generated from the project's README
About Happenings Page CLI MCP server
Managing community pages and organizer commands through AI clients is what Happenings Page CLI enables. It connects various MCP-capable tools like Claude, ChatGPT, Cursor, and VS Code to Happenings pages via a remote MCP server. This setup uses a streamable HTTP transport and requires OAuth 2.1 with PKCE for secure authentication, ensuring that every command executed by the AI remains strictly limited by the user's specific role on each page.
Developers and organizers can integrate this service using a remote URL rather than a local stdio fallback. The system provides specific tools including hap_help, hap_read for read-only access, and hap_run for executing commands. Depending on the client, users might upload a skill zip file, copy instruction text, or use specific CLI commands to add the connector. This remote architecture allows for centralized management of page content and organizer actions directly from within an AI interface.
What you can do with it
- 1Execute organizer commandsAn organizer can use an AI client to run specific page commands through the hap_run tool.
- 2Read page contentA user can request the AI to retrieve information from a Happenings page using read-only access.
Written from the project's README. Every use case is checked against a quote from it.
How to install Happenings Page CLI MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Happenings Page CLI MCP in Claude Code
$ claude mcp add --transport http page-cli https://api.happenings.social/page/mcpInstall Happenings Page CLI MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"page-cli": {
"url": "https://api.happenings.social/page/mcp"
}
}
}Install Happenings Page CLI MCP in VS Code
.vscode/mcp.json
{
"servers": {
"page-cli": {
"type": "http",
"url": "https://api.happenings.social/page/mcp"
}
}
}Install Happenings Page CLI MCP in VS Code CLI
$ code --add-mcp '{"name":"page-cli","type":"http","url":"https://api.happenings.social/page/mcp"}'Install Happenings Page CLI MCP in Codex
$ codex mcp add page-cli --url https://api.happenings.social/page/mcpInstall Happenings Page CLI MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.page-cli] url = "https://api.happenings.social/page/mcp"
Install Happenings Page CLI MCP in Gemini CLI
$ gemini mcp add -s user --transport http page-cli https://api.happenings.social/page/mcpInstall Happenings Page CLI MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"page-cli": {
"url": "https://api.happenings.social/page/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablehappenings-dk/happenings-ai is public and reachablegithub.com/happenings-dk/happenings-ai ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-12github.com/happenings-dk/happenings-ai ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubHappenings 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 9207iss. 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_helpandhap_read(read-only) andhap_run. - The skill:
skill/happenings.mdis the single source.node build.mjsgenerates every client's copy from it; a backoffice test fails when one is stale.
Per client
| Client | Connector | Skill |
|---|---|---|
| Claude (web, Desktop, app) | URL: Customize, Connectors, Add custom connector. Team/Enterprise: an owner adds it under Organization settings, Connectors | Download happenings-skill.zip, upload under Customize, Skills |
| ChatGPT | URL: Settings, Apps and connectors, Advanced settings, Developer mode, Create (paid plans) | Copy chatgpt-instructions.txt into a project or custom GPT |
| Claude Code | claude mcp add --transport http happenings https://api.happenings.social/mcp |
mkdir -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 |
| Cursor | Install 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 serverUrl |
Append AGENTS.md |
| Gemini CLI | gemini mcp add --transport http happenings https://api.happenings.social/mcp |
Append GEMINI.md to ~/.gemini/GEMINI.md, or both in one: the extension below |
| Codex CLI | codex mcp add happenings --url https://api.happenings.social/mcp, then codex mcp login happenings |
Append 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.jsonandplugins/happenings(the.mcp.jsonconnector, 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.jsonandGEMINI.md.gemini extensions install https://github.com/<owner>/<repo> -
Claude plugin as a file:
happenings-plugin.zip, built bybuild.mjsfromplugins/happeningsand 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.mjscopies it at build time) and links it from/mcpand/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:
openssl genpkey -algorithm Ed25519 -out key.pem # OpenSSL 3, not LibreSSL
openssl pkey -in key.pem -pubout -outform DER | tail -c 32 | base64
# replace the p= value of the MCPv1 TXT record in Cloudflare with that output
mcp-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.json
rm key.pem
Editing the skill
- Edit
skill/happenings.md. node integrations/ai/build.mjs- 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.
Happenings Page CLI MCP questions
How do I add Happenings Page CLI MCP to Claude Code?
Run claude mcp add --transport http page-cli https://api.happenings.social/page/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Happenings Page CLI MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I add Happenings to Claude Desktop?
You can add it by using the URL under Customize, Connectors, and then Add custom connector.
What tools are available through the connector?
The connector provides hap_help, hap_read (which is read-only), and hap_run.
Does this require a local installation?
No, every client uses the remote URL with OAuth and none requires a local stdio fallback.