Skip to Content
Set up MCP

Set up MCP

MCP · Beta

Let an AI assistant read your organization’s events, with no code and no API key pasted into a chat. Stello runs a read-only Model Context Protocol  server. An organization admin adds its address in an AI client that supports remote MCP servers, signs in to Stello, and approves access.

Beta — access is switched on per organization by Stello. Client-specific instructions are published only for combinations we have tested, and none are listed yet. Any client that supports remote MCP servers with OAuth should be able to connect.

What you can ask

  • “Which of our events are coming up this month?”
  • “Give me the title, description, image and booking link for this event.”
  • “Show the ticket prices, including any membership requirements.”

Connect

  1. Add https://mcp.stello.no/mcp as a remote MCP server in your AI client.
  2. Sign in to Stello when asked. You return to an approval page.
  3. Choose the organization, and whether to include its sub-organizations. Review what is requested and approve.

Approval lasts 90 days. Connect again to renew it.

Tools

All tools are read-only. They use the same data, filters, pagination and field set as the Events API, and return the same objects.

ToolWhat it returns
list_organizationsThe organizations this connection can read. Only needed when you approved more than one.
list_eventsA page of events. Same filters as GET /v1/events: status, time, sort, starts_at_gte, starts_at_lt, limit, cursor.
get_eventOne event by event_id, which is the event ID or its ten-digit code.
list_ticket_typesAn event’s ticket types, with prices in NOK øre, sale windows, membership requirements and availability.

Amounts are NOK in øre: 10000 is 100 kr. Defaults match the API: published events that have not ended.

Who can read what

  • Only an admin of the organization can approve, and only if Stello has enabled API access for it. Both are checked again on every call, so removing the admin or switching API access off stops the connection immediately.
  • A connection reads one approved organization at a time. A tool argument can pick among the organizations you approved, never add another.
  • Sub-organizations are included only if you chose that, and only those with their own enabled API access.
  • Remove access, or disconnect an assistant, under Developers → MCP in the dashboard. It takes effect at once.

Not included: attendee, buyer and order data, ticket-holder lookups, webhooks, and anything that changes data. These need their own permissions and review before they can be offered.

Your AI provider and your data

What a tool returns is sent to the AI service you chose, including draft events if they are in scope. That provider’s retention and training settings apply, so review them before connecting. Event descriptions are written by the organization, and an assistant may treat text inside them as instructions. Stello returns them as plain data and cannot control what the assistant does with them.

Use is governed by the MCP terms and, where it reads through API access, the API terms. Acceptance occurs through use.

Limits

Each connection is rate limited per person and per organization. Responses are capped in size, so page through long lists with cursor.