Use Relivo as an API and an MCP server

This is a beta

• Server relivo 1.0.0.
• Protocol 2025-03-26, JSON-RPC 2.0, streamable HTTP.
• A Free workspace reports a monthly allowance of 500 tool calls. Other plans return their own number.

Start from the Events tab

Sign in at events.relivo.app/login. The dashboard sidebar opens on Events, the list of photo galleries for the team. Open a gallery and the event has six tabs. The API follows those tabs.

1. Eventslist-events and get-event. The id in each row is the eventId every other call needs.
2. Photosget-event-images, search-images, upload-image, create-image-upload-url, download-image, and the tag tools.
3. Attendeeslist-attendees and get-attendee, including how many photos matched each person.
4. Campaignget-campaign-analytics reads delivery, opens, clicks and bounces. Sending a campaign stays in this tab.
5. Analyticsget-event-metrics for images, matches, registrations and processing.
6. Billing and SettingsStill edited in the dashboard. Event settings can be read at relivo://events/{eventId}/settings. There is no billing tool.

Create an API key

Keys live on the same dashboard, under Team settings, in the API Keys panel. Only a company admin can create them. The panel is the one that says it connects AI assistants and scripts to your galleries via MCP.

1. Choose a name you will recognize later, such as “Cursor” or “Night Run photographer”.
2. Choose access: the whole team, or a single event. An event key is the one to hand a photographer or a per-event script.
3. Copy the key when it appears. It starts with relivo_ and is not shown again.
4. The table then shows a masked key, the scope, calls this month, and Active or Revoked. Revoke or delete stops anything using that key immediately.

A key inherits the company plan quota. Every tool call is metered against that shared monthly allowance, not against the key alone. Keep the key in an environment variable. Do not put it in a browser bundle or a public repository.

Connect an MCP client

Point the client at https://events.relivo.app/api/mcp and send the key as Authorization: Bearer. The server also accepts X-Api-Key. After it connects, ask it to call list-events first.

{
  "mcpServers": {
    "relivo": {
      "url": "https://events.relivo.app/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:RELIVO_API_KEY}"
      }
    }
  }
}

Cursor reads ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one project. Set RELIVO_API_KEY in the environment before the app starts, so the file never contains the key. Claude Desktop uses the same JSON in its MCP config.

claude mcp add --transport http relivo https://events.relivo.app/api/mcp \
  --header "Authorization: Bearer $RELIVO_API_KEY"

What to ask

• “List my Relivo events and tell me which gallery has the most photos.”
• “Search the Night Run gallery for photos tagged finish line.”
• “How many attendees have at least one matched photo, and how many MCP calls do we have left this month?”

ChatGPT custom connectors can use this URL when the connector can attach a bearer token. A connector that only offers OAuth cannot sign in yet. Use Cursor, Claude, or the HTTP API below.

Call the HTTP API

There is one endpoint. MCP clients and scripts both POST JSON-RPC to it. GET returns 405. A missing key returns 401 with “pass your company API key as Authorization: Bearer”.

curl https://events.relivo.app/api/mcp \
  -H "Authorization: Bearer $RELIVO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "list-events",
      "arguments": { "limit": 20 }
    }
  }'

The response is server-sent events. Read the data: line. Tool results arrive as text whose contents are JSON:

{
  "events": [
    {
      "id": "evt_example",
      "name": "Night Run",
      "status": "PUBLISHED",
      "startDate": "2026-11-07T18:00:00.000Z",
      "endDate": null,
      "city": "Essen",
      "country": "DE",
      "eventPlan": "PREMIUM",
      "createdAt": "2026-10-01T12:00:00.000Z",
      "_count": { "images": 1200, "eventUsers": 480 }
    }
  ],
  "total": 1,
  "limit": 20,
  "offset": 0
}

That object is the shape list-events returns. The names in the sample are illustrative. Discover tools with method tools/list and resources with resources/list. Call one with method tools/call and params.name plus params.arguments.

Tools

Nineteen tools. A key only sees its company, and an event-scoped key only sees that event. Unknown fields are rejected.

Resources

resources/list returns one summary and one settings resource per event the key can see, plus the company profile. The URIs follow this pattern:

• relivo://company/info

  Company profile: name, tier, credits and configuration.

• relivo://events/{eventId}/summary

  Key metrics and configuration for one event.

• relivo://events/{eventId}/settings

  The event settings JSON. This is a read. Changing settings stays in the event Settings tab.

Errors and quota

Privacy

• A key cannot read another company’s events. An event-scoped key cannot read the rest of the team.
• Guest face matching stays opt-in. The API does not replace the consent step attendees see in the gallery. The selfie collection tools store private reference images for the company. They are not a way to identify people who did not take part.
• Attendee tools can return names and email addresses. Treat that payload as personal data, the same way the Events tab does. The privacy policy, DPA and GDPR notes are at /privacy, /dpa and /gdpr.
• Questions about the beta go to /contact.