Grok
Add a custom connector in the Grok app, or point the Grok CLI at the Relivo server.
Set up GrokRelivo MCP · Beta
Work your event photos,
right from your AI chat.
Connect Relivo to Grok, Claude or ChatGPT. Ask for the finish-line shots, who already has a match, or how the gallery email performed.
Beta. A company admin creates the key in the events dashboard. The gallery stays in Relivo.
Night Run· Relivo
Example
Which photos show the finish line, and how many guests already have a match?
42 photos match “finish line”. 1,184 of 1,500 attendees have at least one photo. The gallery email has been delivered. I can open the campaign stats next.
Example reply. Grok, Claude and ChatGPT call the same gallery.
Connect Relivo to your favorite AI assistant.
Each one talks to the same server. You create a key once, then add Relivo where that assistant keeps its connectors.
Claude
Claude Code and Claude Desktop take the server URL and your key as a header.
Set up ClaudeChatGPT
Add a custom connector and attach your key when ChatGPT can send a bearer token.
Set up ChatGPT
Cursor uses the same config as Claude Desktop. See the reference
What your AI can do now
It works on the same Events tab you already use: galleries, photos, attendees and campaign stats.
finish line
- Finish-line widePhoto
- Medal momentPhoto
- Crowd at the archPhoto
Search a gallery in plain language.
Ask for the finish line, the keynote, or a tag you already use. Relivo searches that event’s photos and descriptions and brings the matches back into the chat.
Matched attendees
1,184
of 1,500 guests · example
See who already has their photos.
Ask how many attendees have at least one matched photo, or which gallery is the largest. Face matching stays opt-in. The assistant reads the counts. It does not replace the consent step guests see.
Gallery email · example
- Delivered
- 1,462
- Opened
- 68%
- Clicked
- 41%
Read the gallery email.
Delivery, opens, clicks and bounces are available as soon as a campaign has run. Sending the campaign stays in the Campaign tab of the event.
Added to Night Run
finish linekeynotevip
Face indexing queued
Add a photo and tag it.
Hand the assistant a photo and a tag. Relivo stores the file, adds it to the gallery and queues face indexing. Billing and event settings stay in the dashboard.
Try a prompt
- “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?”
- “How many MCP calls do we have left this month?”
How it works.
01
Create a key.
In the events dashboard, open Team settings and the API Keys panel. A company admin names the key and chooses the whole team, or a single event.
02
Add Relivo to your AI.
Paste the server URL into Grok, Claude or ChatGPT and send the key as a bearer token. It takes a minute once you have the key.
03
Just ask.
Type what you want in plain language. Your assistant calls Relivo and answers from the gallery, the attendee list and the campaign stats.
Set it up.
The server is the same for every assistant. Copy the URL, then follow the path for the one you use.
https://events.relivo.app/api/mcp
App, CLI or API
Grok
- Create a key at the events login, under Team settings → API Keys. Copy it when it appears. It starts with
relivo_. - In the Grok app, open grok.com/connectors, choose New Connector, then Custom, and paste the server URL. If Grok asks for a token, paste the key. Relivo does not show an OAuth consent page.
- On Grok Business or Enterprise, an admin may need to add the connector before members can use it.
Grok CLI
grok mcp add --transport http relivo https://events.relivo.app/api/mcp \
--header "Authorization: Bearer $RELIVO_API_KEY"xAI API · authorization is the key alone
{
"type": "mcp",
"server_url": "https://events.relivo.app/api/mcp",
"server_label": "relivo",
"authorization": "<your Relivo API key>"
}The xAI API sends that value as Authorization: Bearer. Pass the key by itself.
Claude Code and Claude Desktop
Claude
Put the key in RELIVO_API_KEY before the app starts. The config below reads it from the environment.
Claude Code
claude mcp add --transport http relivo https://events.relivo.app/api/mcp \
--header "Authorization: Bearer $RELIVO_API_KEY"Claude Desktop or Cursor · mcp.json
{
"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. Claude Desktop uses the same JSON in its MCP config.
Custom connector
ChatGPT
- Open ChatGPT settings and find Connectors, Apps, or Developer mode.
- Add a custom connector and paste the Relivo server URL.
- Attach the API key as a bearer token when the connector offers a header.
A connector that only offers OAuth cannot sign in yet. Use Claude, the Grok CLI, or Cursor for that account. The full request shape is on the API reference.
FAQ
The server is in beta. Tool names and quotas can change. The reference is checked against the live endpoint.
What is the Relivo MCP?
It is a beta connection between Relivo and an AI assistant. Once connected, the assistant can list your events, search photos, read attendee match counts and campaign analytics, and upload or tag photos. Recording the event and sending email still happen in Relivo.
Which assistants work with Relivo?
Grok, Claude and ChatGPT, plus any client that can call a remote MCP server with a bearer token. Claude and Cursor are the setups spelled out in the reference. Grok works from the Grok app, the Grok CLI, or the xAI API. ChatGPT works when the custom connector can attach a bearer token.
Is the Relivo MCP free?
It is part of the events workspace, on the plan you already have. Calls are metered against that plan. A Free workspace reports 500 tool calls a month. Other plans return their own number. Ask the assistant to call get-mcp-usage for the live allowance.
Do I still use the Relivo dashboard?
Yes. Uploading in bulk, the guest consent step, sending a campaign, billing and settings edits stay in the dashboard. The assistant reads that same event and can add or tag individual photos.
How do I connect Relivo to Grok?
Create an API key, then open grok.com/connectors, choose New Connector, then Custom, and paste the Relivo server URL. If Grok asks for a token, paste the key. Relivo does not show an OAuth consent page. The Grok CLI and the xAI API can send the key directly as a bearer token.
How do I connect Relivo to Claude?
In Claude Code, add the Relivo HTTP server and an Authorization: Bearer header that carries your key. Claude Desktop uses the same JSON as Cursor: the server URL plus that header. Set RELIVO_API_KEY in the environment so the file never contains the key.
How do I connect Relivo to ChatGPT?
Open ChatGPT settings, find Connectors, and add a custom connector with the Relivo server URL. Attach the key as a bearer token when the connector offers that. A connector that only offers OAuth cannot sign in yet. Use Claude, Grok or Cursor for that account.
How do I disconnect an assistant?
Remove Relivo from the assistant’s connectors, or revoke the API key in Team settings. Access ends immediately. Photos, attendees and campaigns stay in Relivo.
What can my AI see?
The events on that key: galleries, photos, attendees (including names and email addresses), campaign analytics and the company profile the API returns. An event-scoped key sees only that event. There is no billing tool. Treat attendee data as personal data, the same way the Events tab does.
Can my AI email every guest?
Sending a campaign stays in the Campaign tab. The assistant can read delivery, opens, clicks and bounces after a campaign has run.
From a question to the gallery.
Create a key, connect the assistant you already use, and ask about the photos.