Claude Desktop
- Settings › Connectors › Add custom connector.
- Paste the address, give it a name, add it.
- Click Connect and sign in with your AirLST account in the browser.
AI integration · AirLST MCP Server
AirLST MCP server:your AI assistant works inside AirLST.
AirLST is MCP-ready: the AirLST MCP server connects your AI assistant, such as Claude, ChatGPT or GitHub Copilot, to your event account, and Microsoft Copilot through Copilot Studio as a custom setup. The assistant builds landing pages and registration forms in AirLST, with your permissions, and every step is logged.
Available in Airstage · rolling out to other modules
One addressAdd it to your assistant and sign in with your AirLST account.
Live in the builderEvery change shows up instantly in your open Airstage.
Your permissionsThe assistant only sees what you’re allowed to see.
01Connect
How to connect your assistant.
Connecting takes one address and one sign-in. You’ll find the address in Airstage under “Connect your agent”; sign-in runs through OAuth with your AirLST account, so there’s no key to copy.
Add the address
Add the AirLST MCP server to your assistant as a connector or MCP server.
Sign in with AirLST
The first time you connect, a browser opens and you sign in with your event account.
Get started
Tell the assistant which event to build for. You watch it work live in the builder.
Quick guides by assistant
As described in the product; Microsoft Copilot Studio per Microsoft’s documentation. Every assistant uses the same address.
Claude.ai
depends on plan- Connectors › Add custom connector › paste the address, then connect.
- On Team and Enterprise plans an admin adds the connector once for the organization; members then just click Connect.
Claude Code
- Add the server with one command in the terminal.
- Type /mcp in a session and sign in in the browser.
ChatGPT
beta, paid plan- Settings › Apps › Advanced › turn on developer mode.
- Apps › Create › paste the address › choose OAuth › Create.
- Sign in when prompted. Not available on the free plan.
GitHub Copilot in VS Code
- Command palette › “MCP: Add Server” › HTTP › paste the address.
- Sign in in the browser that opens automatically.
Cursor
- Settings › Tools & Integrations › New MCP Server, paste the address.
- Click “Needs Login” on the server and sign in.
Codex CLI
- Add the server with one command and sign in.
Microsoft Copilot Studio
custom setup- In your agent: Tools › Add a tool › New tool › Model Context Protocol.
- Enter a name, a description and the address; choose OAuth 2.0 with “Dynamic discovery”.
- Create the connection, add it to the agent and sign in with your AirLST account. Your IT team then publishes the agent, for example to Teams and Microsoft 365 Copilot.
Any other MCP client
- Point the client at the address using Streamable HTTP. Sign-in runs through OAuth, with no client ID or secret.
- If the client has no OAuth, connect it through the mcp-remote tool.
02Microsoft Copilot
Connect AirLST to Microsoft Copilot.
At work, Microsoft Copilot speaks MCP through Copilot Studio: your IT team adds the AirLST MCP server as a tool to a custom agent and publishes that agent to Teams and Microsoft 365 Copilot. It’s a Custom setup in your Microsoft tenant, not a one-click connection, and there’s no in-product guide for it yet.
| Topic | Copilot Studio (per Microsoft) | AirLST MCP server |
|---|---|---|
| Add it | Tools › Add a tool › New tool › Model Context Protocol; name, description, address. | One address, found in the Airstage builder under “Connect your agent”. |
| Transport | Streamable HTTP; SSE hasn’t been supported since August 2025. | Remote server over HTTPS using Streamable HTTP. |
| Sign-in | OAuth 2.0, type “Dynamic discovery”: the agent finds the endpoints and registers itself. | OAuth with discovery and dynamic registration, no client ID or secret. |
| Tools | Name, description, inputs and outputs come from the server; Copilot Studio picks up changes automatically. | The Airstage tools; other modules follow. |
| Permissions | With OAuth, each user signs in individually. | The agent only sees event sites the signed-in user can see; every tool call is recorded. |
| Requirements | Generative orchestration turned on; Power Platform data policies also govern MCP servers; admin approval for org-wide rollout. | An AirLST account with access to the event. |
Copilot at work
This runs through Copilot Studio and your work account in your Microsoft tenant, not the personal Copilot app. Your IT team manages licenses and channels.
Other systems
Connect your CRM, Power Automate, Power BI and Microsoft 365 through the REST API: AI agents and enterprise systems.
What it’s for
For the event tasks an assistant can take on, see AI in events.
03Tools
What the assistant can do in AirLST.
The server gives the assistant tools, not a copy of your data. Today these are the Airstage tools, the builder for landing pages and registration forms.
| Tool | What the assistant does | Status |
|---|---|---|
| Read pages | Find the event sites you’re allowed to edit and read the structure and content of a page. | Available |
| Build pages | Add, edit, move and remove sections, text, images and buttons, including several changes in one step. | Available |
| Manage pages | Add further pages such as a thank-you or info page, with their own SEO settings, and remove them. | Available |
| Registration form | Build the form from the event’s guest fields, with conditions and steps. The assistant only adds new guest fields after you confirm. | Available |
| Design | Set colors and fonts for the whole site, from checked presets or custom, including dark mode. | Available |
| Images | Upload logos and photos and reuse images already uploaded (with assistants that have a command line). | Available |
| Brief | Read and save the event’s brand voice, audience and things to avoid, so every page fits them. | Available |
| Your feedback | Work through notes you pin to elements and propose variants on request. Only what you pick is applied. | Available |
| Review | Render the page on mobile and desktop and check it: contrast, broken layout, form states. | Available |
| History | Undo or redo any step, including your own; the history shows who changed what. | Available |
| Publish | Publish a numbered release when you tell it to, and switch back to an earlier one instantly if needed. | Available |
Rollout status
Airstage is connected. The other Suite modules follow one by one; the order: .
| Module | Scope | Status |
|---|---|---|
| Airstage (landing pages and registration forms) | All tools above | Available |
| Other Suite modules | Rolling out module by module | Rollout |
04Examples
Three conversations with your assistant.
Illustrative examples; the assistant only uses tools from the list above.
“Build the registration page for Partner Day.”
The assistant reads the brief, adds the header, agenda and venue, and builds the form from the guest fields. Plus-one and menu choice only appear when a guest attends.
“Work through my notes.”
You pin notes to elements in the builder. The assistant applies them in order, reviews the page on mobile and desktop, and checks off each note.
“Show me three takes on the header.”
The assistant proposes clearly different versions. The one you pick is applied; then it publishes a new release when you say so.
05For IT
MCP security: what IT wants to know first.
The AirLST MCP server is a remote MCP server: your assistant connects over HTTPS, nothing is installed locally. Documentation on hosting and information security is in the Trust Center.
OAuth, not keys
Sign in with your AirLST account in the browser. The assistant registers itself, so there’s no client ID or secret to manage.
The user’s permissions
The assistant only works on event sites the signed-in user can see in AirLST.
Every action logged
Every tool call is recorded; the builder’s history shows each change, and each can be undone.
No sending, no export
Through the Airstage tools the assistant doesn’t send emails or export data. Publishing happens when you tell it to.
Data hosted in Germany
Event and guest data stay with AirLST on servers in Germany. What the language model processes is governed by your contract with its provider.
Your choice, any time
You choose the assistant and the model. You disconnect in the assistant.
06Assistants
Which assistants work.
There’s an in-product guide for Claude, ChatGPT, GitHub Copilot, Cursor and Codex. Microsoft Copilot connects through Copilot Studio as a custom setup. Any other client that speaks MCP over HTTP with OAuth connects with the same address.
- AI event managementWhat AI changes in event management, and where it saves the most work.
- MCP in the glossaryWhat the Model Context Protocol is, in short.
- API and integrationsREST API and connectors to CRM and IT, for developers, plus AI agents and enterprise systems.
- Event website builderLanding pages without AI, in the builder.
Part of AirLST
The AI works with the same data as every other feature.
An assistant connected over MCP works on the same guests, events and reports as every other feature of the platform.
Event CRMContacts across all events
Guest List ManagementOne source of truth for the whole team
Event Website BuilderLanding pages without code
Invitation EmailsDigital invitations in your brand design
Event RegistrationForms, RSVPs, plus-ones
Event TicketingTamper-proof QR tickets
Seating ChartsTables and seats from the guest list
Workflow AutomationAutomate workflows
Event AppAgenda and ticket on the phone
Event Check-inScan instead of search at the door
Access ManagementCheck-in, badges, gates: the whole entrance
Name BadgesPrinted on arrival
Lead RetrievalScan leads at the booth
Event SurveysPost-event feedback
Reporting & AnalyticsAttendance, no-shows, reporting
API & IntegrationsConnect CRM and IT- You are here
AI integration (MCP)Connect Claude, ChatGPT or Copilot
FAQ
AirLST MCP server: frequently asked questions
What is an MCP server?
An MCP server gives an AI assistant the tools of an application, following the open Model Context Protocol. The assistant sees which tools exist and uses them in the conversation. Today the AirLST MCP server offers the Airstage tools: build pages, registration forms, design, review, publish. More on the term in the glossary.
Do I need my own AI subscription?
Yes. You bring the AI: your assistant runs in your own account with Anthropic, OpenAI, GitHub, Cursor or Microsoft. AirLST provides the server, the tools and the controls, not a language model of its own. In ChatGPT, connecting custom servers is currently a beta feature of paid plans.
What data does the language model see?
Whatever the tools return: the structure and copy of your pages, the event brief, and the definitions of the guest fields and guest groups a form works with. The Airstage tools don’t hand out a guest list. The assistant only sees events the signed-in user can see in AirLST. What the language model processes itself is governed by your contract with its provider.
Can the assistant delete things or send emails?
It can remove elements and pages; the history brings elements back, an earlier release brings pages back. An event site’s home page can’t be deleted. It can’t send emails or export data through the Airstage tools. Publishing happens when you tell it to, and every release can be switched back to the previous one instantly.
Which modules are connected?
Today Airstage, the builder for landing pages and registration forms. The other Suite modules follow one by one. See the rollout status for what’s connected.
Does it work with Claude and ChatGPT Enterprise in a large company?
With Claude Team and Enterprise, an admin adds the connector once for the organization, and members connect with one click. In ChatGPT, the connection runs through developer mode on paid plans; whether it’s enabled in your company workspace is up to your admin. Developers connect GitHub Copilot in VS Code themselves; Microsoft Copilot at work runs through Copilot Studio.
How do I set up Copilot Studio with the AirLST MCP server?
As a custom setup in your Microsoft tenant, following Microsoft’s documentation: in your Copilot Studio agent, go to Tools › Add a tool › New tool › Model Context Protocol, enter the AirLST MCP server address with a name and description, choose OAuth 2.0 with “Dynamic discovery” for authentication, create the connection and sign in with your AirLST account. On the Microsoft side you need generative orchestration turned on for the agent, Power Platform data policies that allow the connector, and admin approval to roll the agent out to your whole organization. There’s no in-product guide for this yet; your IT team or our Integration Services handle the setup.
Does it work with pages built in the drag-and-drop editor?
Read and review, yes; edit, no. The assistant can only look at and assess pages built in the visual module editor. To keep building one with AI, switch the site to AI building in its settings; that’s a one-way step.