← AI integrations

FOR DEVELOPERS

MCP server and event discovery API

Read the HappenHop MCP and REST API documentation, explore the public schema, and learn how to request read-only integration access.

Build with public event data

Use the Model Context Protocol (MCP) server at /mcp for an assistant integration or the REST API at /api/v1 for a client that uses HTTP. Both support event search and details, cities, categories, and event relationships.

  1. Resolve the city and event type to their catalog identifiers.
  2. Search by keyword or by a local date range and follow the returned event links.
  3. Keep unavailable prices, ages and end times marked as unknown. Send visitors to the organizer to confirm booking details.

Authentication and limits

Tool and API calls need authorized credentials. Keep credentials in your client’s secret settings. The API guide describes authentication, response fields, pagination and rate limits. The API exposes public catalog data and offers no booking or editing operations.

Ask about integration access ↗

Understand event coverage and missing fields.