
Kiosk Builder
io.github.pirumpiPublished by GitHub account pirumpiv1.0.0Updated Oct 24, 2026
Build and manage airline self-service kiosk apps — styling, pages, CMS, and CUSS2.
Overview
Lets an assistant build and manage airline self-service kiosk apps, covering styling, pages, CMS content, and CUSS2.
- What you can do
- Kiosk Builder is a remote MCP server for creating and managing airline self-service kiosk applications. According to its registry description, it covers styling, pages, CMS, and CUSS2, the standard interface used by airport check-in kiosks. No individual tools are listed in the manifest, so the exact operations are not documented here.
- When to use it
- Consider it when you work on airline or airport self-service kiosk applications and want an assistant to help assemble or manage their styling, pages, CMS content, or CUSS2 integration. It is not aimed at general software projects.
- Requirements
- A remote streamable HTTP endpoint at It requires the elevated-auth header, a secret token generated from the Connect panel in the kiosk app configuration editor, described as a base64-encoded JWT. No packages or environment variables are declared.
Installation
In SourceWeft
- Open Kiosk Builder in the dashboard and add it to a workspace.
- Connect elevated-auth credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.pirumpi%2Fkiosk-builder/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"kiosk-builder": {
"type": "http",
"url": "https://ai-elevation.azurewebsites.net/mcp",
"headers": {
"elevated-auth": "<YOUR_API_KEY>"
}
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.