For AI assistants
Run your page from your AI assistant
Connect Claude, Codex or any assistant that speaks MCP to your Happenings page. Ask about sales, draft posts and plan events in plain words, and you approve every change.
Works with Claude, Claude Code, Codex and other MCP clients
Your assistant
How many tickets did we sell for Friday bar this week?
Used Happenings
hap_read
You sold 184 tickets for Friday bar this week. That's 37 more than last week, and Thursday was your busiest day.
- Tickets sold
- 184
- vs last week
- +37
- Sales in DKK
- 11,040
Draft a post for next week's event
Used Happenings
hap_read
Here's a post for Friday bar on 2 October. Say yes and I'll publish it on your page.
Friday bar is back on 2 October. Doors at 15, the first 50 get a free drink, and tickets are in the app now.
Set it up in two minutes
Add Happenings to your assistant, sign in once and tick the pages it may use. Sign-in happens in your browser, so no key ever sits in a config file.
- 1
In Claude, open Customize and then Connectors.
- 2
Tap + and choose Add custom connector.
- 3
Paste this URL and name the connector Happenings Connect.
https://api.happenings.social/mcpName
Happenings Connect - 4
Start a new chat, switch on Happenings Connect under tools and ask it to show your pages.
- 5
Sign in to Happenings and tick the pages Claude may work on.
- Connectors you add on claude.ai show up in the Claude desktop and phone apps too.
- 1
Add the server from your terminal.
claude mcp add --transport http happenings https://api.happenings.social/mcp - 2
Then run this in Claude Code, pick happenings and sign in when your browser opens.
/mcp - 3
Tick the pages it may use, and you're set.
- 1
Add the server.
codex mcp add happenings \ --url https://api.happenings.social/mcp \ --oauth-resource https://api.happenings.social/mcp - 2
Sign in. Codex opens your browser for you.
codex mcp login happenings - 3
Tick the pages it may use, then ask away.
Not yet
ChatGPT can't sign in to Happenings yet, so its connectors won't reach your page for now. Use Claude or Codex in the meantime.
- 1
Your client needs remote MCP over HTTP with OAuth sign-in, and it has to run on your own computer.
- 2
Point it at the server URL. Most clients take a config like this.
{ "mcpServers": { "happenings": { "url": "https://api.happenings.social/mcp" } } } - 3
Sign in when it asks and tick your pages.
What it can do
The whole page toolbox, grouped by what you'd actually ask. Reading is instant, and Claude asks before it changes anything.
Events
Upcoming and draft events, sign-up forms, feedback and guest lists.
Try asking
- “What's on for the next two weeks?”
- “Set up next Friday like last Friday”
Tickets and check-in
Ticket types, availability, check-ins and waitlists.
Try asking
- “How many people checked in on Saturday?”
- “Add 50 more early bird tickets”
Orders and money
Sales, orders, coupons and deals. Bank accounts, payouts and fees stay in Connect.
Try asking
- “What did we sell this month?”
- “Make a 20 percent coupon for members”
Members and team
Members, plans, community titles and who has which role.
Try asking
- “How many members joined since August?”
- “Who on the board can edit the page?”
Analytics
Page stats, funnels, audience and member retention.
Try asking
- “Where do people drop off before buying?”
- “Compare this semester with the last one”
Posts and messages
Page posts, forums, polls, announcements and email reports.
Try asking
- “Draft a post for next week's event”
- “Remind members about the general meeting”
You stay in charge
An assistant only ever acts as you, on the pages you pick, and never beyond your role.
You choose the pages
Tick which pages it may reach when you sign in. That limit lives in the token itself.
Never more than your role
It can only do what your role on the page allows. An editor's assistant can't touch finance.
Changes wait for your yes
Claude shows you each change and waits for your yes. Bank accounts, payouts and fees are never changed this way.
Revoke anytime
Remove the connector or lose the role, and it's cut off on the very next request.
Every call is logged
Each tool call is recorded against your connection, so there's always a trail.
Connector, skill and plugin
One connector does it all. The skill and the plugin make Claude better at using it.
Happenings Connect
Asks before changes · limited by your role
The full Happenings page CLI for the pages you pick, with image upload. Claude reads freely and asks before every change, always within your role.
Setup guideEndpoint
https://api.happenings.social/mcpAgent skill
happenings-page
Teaches a coding agent the page commands, what your role allows and what to do when something is refused.
Download the skillOr install it from the terminal
mkdir -p ~/.claude/skills/happenings-pagecurl -fsSL https://happenings.social/skills/happenings-page.md \ -o ~/.claude/skills/happenings-page/SKILL.mdClaude plugin
happenings
The page connector, the skill and four ready-made commands in one file. Download it and add it in Claude under plugins.