Happenings
Get the appLog inCreate account

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.

Connect your assistantRead the docs

Works with Claude, Claude Code, Codex and other MCP clients

Your assistant

Happenings on

How many tickets did we sell for Friday bar this week?

Used Happenings

  • list_events
  • get_sales_summary

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

  • list_upcoming_events
  • propose_page_post_operation

Here's a draft for Friday bar on 2 October. It's waiting in Connect, so nothing goes out until you approve it.

Draft postWaiting for you

Friday bar is back on 2 October. Doors at 15, the first 50 get a free drink, and tickets are in the app now.

Ask about your page

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. 1

    In Claude, open Customize and then Connectors.

  2. 2

    Tap + and choose Add custom connector.

  3. 3

    Paste this URL and name the connector Happenings Backoffice.

    https://api.happenings.social/mcp

    Name

    Happenings Backoffice
  4. 4

    Start a new chat, switch on Happenings Backoffice under tools and ask it to show your pages.

  5. 5

    Sign in to Happenings and tick the pages Claude may work on.

  6. Connectors you add on claude.ai show up in the Claude desktop and phone apps too. Keep the name exactly Happenings Backoffice, because skills find the connector by that name.

What it can do

112 tools across your page, grouped by what you'd actually ask. Reading is instant, and changes show up as drafts.

  • 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, refunds, coupons, deals and payouts.

    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 you

    New events, posts and refunds land as drafts. Nothing happens until you confirm it in Connect.

  • 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.

Servers and tools

Two servers and a skill. Most people only need the first one.

  • Page tools

    112 tools · reads and drafts

    Tools made for chat. They read your page and draft changes for you to confirm.

    Endpoint

    https://api.happenings.social/mcp
    Setup guide

  • Page CLI

    Acts right away · limited by your role

    The Happenings command line as one tool, for the pages you pick. It reaches further and acts right away, always within your role.

    Endpoint

    https://api.happenings.social/page/mcp

    Claude Code

    claude mcp add --transport http happenings-page https://api.happenings.social/page/mcp

  • Agent skill

    happenings-page

    Teaches a coding agent the page commands, what your role allows and what to do when something is refused.

    Download the skill

    Or 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.md
Rather use the terminal yourself?Get the hap CLI and run your page from the command line.

Questions

Which assistant should I use?
Claude works best today, in the browser, the desktop app or Claude Code. Codex works too. Other clients need remote MCP with sign-in and have to run on your computer.
Can it change things without asking me?
Not with page tools. Every change arrives as a draft you confirm in Connect. The page CLI acts right away within your role, so only hand it to assistants you trust.
Page tools or page CLI?
Page tools are made for chat and only read and draft. The page CLI gives your assistant the Happenings command line for your pages, so it can do more and does it at once.
Who can connect?
Anyone with a role on a page. What the assistant sees and does follows that role.
How do I disconnect?
Remove the connector in your assistant. Losing your role on the page also cuts it off right away.
Does it work with ChatGPT?
Not yet. ChatGPT connectors can't sign in to Happenings today, so use Claude or Codex for now.

Analytics choices

Happenings can use optional analytics cookies to understand usage and improve the product. They stay off unless you allow them.

Read cookie policy