Festapp
Festapp MCP connection terms
Festapp MCP is an optional interface to supported Festapp operations, including Festapp Tickets. The provider is Michael Bujnovský, registration number 06455361. Support: [email protected]. These connection terms supplement the terms of the selected account environment and the event organizer's terms; they do not replace them or change statutory rights.
Use an account entitled to the selected environment and resources. Explicitly approve the organizers/events and functions for each client. Each operation remains subject to current account rights, approved OAuth scopes, the client data profile, supported capabilities and the application's domain rules. A connection provides no cross-tenant rights. Additional environments require separate connections and consent.
Only authorize clients you trust. Keep credentials private and use data only for purposes you are entitled to pursue. Client responses can contain personal data. The client provider's terms and settings govern what it does with returned data. Festapp does not promise a client's approval, availability or compatibility without demonstrated support for its OAuth and MCP protocol.
Read each operation's description before requesting changes. Supported writes may have application side effects such as changing records or requesting communications. Use the same command ID and payload to recover an uncertain result; do not assume that disconnecting a transport undoes a committed operation. Connecting an account alone neither buys a ticket nor executes a payment. Payment, refund and other restricted operations retain their ordinary application boundaries.
Account availability, event service fees and prices remain those agreed for the selected environment or organizer. The MCP listing does not create a new paid subscription or promise every account is free. Revoke connections in the selected environment's account settings. Current limitations include explicitly registered callbacks/approved client metadata and unsupported MFA session issuance, which fails closed. Contact support about a failed connection without sending passwords, tokens or customer data.
The source code's MIT license and retained dependency notices govern code distribution; these hosted-service terms are separate.