Kiosk Builder
Build and manage airline self-service kiosk apps — styling, pages, CMS, and CUSS2.
Build and manage airline self-service kiosk apps — styling, pages, CMS, and CUSS2.
https://ai-elevation.azurewebsites.net/mcpHeaders: elevated-auth
Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-pirumpi-kiosk-builder": {
"url": "https://ai-elevation.azurewebsites.net/mcp"
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Paste an API key, bearer token, or session value from the provider. It is used once to list inventory and discarded after the request.
Authentication token generated from the Connect panel in the kiosk app configuration editor (base64-encoded JWT)
Kiosk Builder is an MCP server for Build and manage airline self-service kiosk apps — styling, pages, CMS, and CUSS2.. It supports HTTP transport.
Use the generated config in Install. It points your client at the advertised remote endpoint shown on this page.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://ai-elevation.azurewebsites.net/mcp.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://ai-elevation.azurewebsites.net/mcp.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://ai-elevation.azurewebsites.net/mcp.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://ai-elevation.azurewebsites.net/mcp.
Kiosk Builder uses HTTP transport. Endpoint: https://ai-elevation.azurewebsites.net/mcp.
Kiosk Builder inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
Kiosk Builder is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.