Happenings Connect MCP

Happenings Connect provides an official MCP server that allows AI agents to interact with the Happenings page CLI. It enables users to read events, ticket sales, orders, members, and analytics, as well as create and update events, tickets, deals, and posts. The server respects user roles and requires approval for changes, ensuring that agents operate within the permissions granted by the page administrator.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-19Operated by Happenings Group A/S

MCP endpoint (Streamable HTTP)

https://api.happenings.social/mcp

Vendor documentation

What you can do with it

Check ticket sales and analytics for upcoming events
Create draft events with specific dates, times, and ticket limits
Find members who joined the platform recently
Upload photos or logos to serve as event covers

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add happenings-connect-mcp --url https://api.happenings.social/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable happenings-connect-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "happenings-connect-mcp": {
      "url": "https://api.happenings.social/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "happenings-connect-mcp": {
      "type": "streamableHttp",
      "url": "https://api.happenings.social/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start happenings-connect-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "happenings-connect-mcp": {
      "type": "http",
      "url": "https://api.happenings.social/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http happenings-connect-mcp https://api.happenings.social/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "happenings-connect-mcp": {
      "url": "https://api.happenings.social/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "happenings-connect-mcp": {
      "serverUrl": "https://api.happenings.social/mcp"
    }
  }
}

See all 493

Do you run Happenings Connect MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing