BNDY MCP Server
OfficialRelated Servers
Alternatives to BNDY MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI agents to manage events, venues, songs, and users via the Sonic API, with integrated Spotify and Google Maps search.23MIT
- AlicenseBqualityDmaintenanceEnables natural language access to the Eventbrite API for creating, managing, and interacting with events, venues, and categories.136 npm4MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables MCP clients to interact with any OpenAPI-defined REST API through a serverless AWS Lambda deployment. Supports multiple authentication methods and provides cost-effective, scalable access to third-party APIs through natural language.Apache 2.0
- AlicenseBqualityCmaintenanceConnects AI assistants to the Spotify Web API, enabling playback control, search, and recommendations.8MIT
- AlicenseNot gradedqualityDmaintenanceBridges MCP clients and AWS Lambda functions, enabling generative AI models to invoke Lambda functions as tools without code changes.Apache 2.0
- AlicenseAqualityFmaintenanceEnables AI assistants to manage events, venues, organizers, and tickets on WordPress sites via CRUD operations.37 npm2ISC
TDQS
Scored across 16 tools
Each tool targets a specific resource and action (create, edit, delete, search, list, import, upload). For example, search_artist and search_venue are clearly distinct, and get_by_id and get_by_external_id serve different lookup purposes. No two tools have overlapping responsibilities.
All tool names follow a consistent snake_case verb_noun pattern (e.g., create_artist, edit_venue, search_event, list_artists). The only minor variation is 'get_by_id' and 'get_by_external_id,' which still adhere to the pattern. No mixing of styles.
16 tools cover the core domain of managing artists, venues, and events, including CRUD operations, search, list, bulk import, and poster upload. The number feels appropriate for the scope—neither too few to be useful nor too many to be unwieldy.
The set covers most common operations but has notable gaps: no delete_artist or delete_venue (only delete_event exists), and no list_events tool (only list_artists and list_venues). This means agents cannot list all events or remove artists/venues, which may cause workflow dead ends.