BNDY MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_REGION | Yes | AWS region (e.g., eu-west-2) | |
| AWS_PROFILE | Yes | AWS profile name (e.g., default) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_venueA | Search for existing venues in BNDY database by name and city. Use this BEFORE creating a new venue to avoid duplicates. Confidence = (1 - levenshtein_distance/max_length) * 100. Thresholds: ≥90 high, ≥70 medium, <70 low. |
| create_venueA | Find or create a venue in BNDY. Automatically enriches with Google Places data and deduplicates via Place ID match. Returns existing venueId if matched, otherwise creates new. Safe to call without pre-checking via search_venue. |
| search_artistA | Search for existing artists in BNDY database by name. Pre-filters by name similarity, then scores by Levenshtein distance. Confidence = (1 - edit_distance/max_length) * 100. |
| create_artistA | Create a new artist in BNDY (with AI review flags). Only use if search_artist found no matches. Artist will be flagged for manual review. |
| create_eventB | Create an event in BNDY linking one or more artists to a venue on a specific date/time. |
| search_eventA | Search for events by artist ID or venue ID. Use this to find events for a specific artist so you can update them (e.g., change venue). |
| edit_artistA | Update an existing artist in BNDY. Use this to add location, genres, social media URLs, bio, etc. |
| list_artistsA | List artists with pagination and optional filters for missing data. Use this to find artists that need enrichment (missing location, genres, social URLs, etc.). |
| list_venuesA | List venues with pagination and optional filters for missing data. Use this to find venues that need enrichment (missing address, coordinates, social URLs, etc.). |
| edit_venueC | Update an existing venue in BNDY. Use this to add social media URLs, facilities, ticket info, etc. |
| edit_eventA | Update an existing event in BNDY. Can modify venue, title, date, time, description, ticket info, poster URL, etc. Only works for AI-created or community events. |
| delete_eventA | Permanently delete an event from BNDY. This REMOVES the event entirely (not marked as cancelled). Only works for AI-created or community events. Use search_event first to verify you have the correct event ID. |
| upload_event_posterA | Upload an event poster image to BNDY S3 bucket. Downloads from provided URL and uploads to S3. Use the returned s3Url with edit_event to set as event poster. |
| bulk_importA | Bulk import structured data (artists, venues, events) into BNDY with automatic deduplication. Uses Google Places for venue matching and name matching for artists. Handles the entire import server-side to avoid timeouts. Supports dry-run mode to preview what would be imported. |
| get_by_external_idA | Look up a venue, artist, or event by its external system reference. Use this to check if an entity already exists in BNDY before creating it, enabling idempotent imports across sessions. |
| get_by_idA | Fetch full venue, artist, or event record by bndy UUID. Returns ALL fields including phone, website, facilities, socialMediaUrls, nameVariants, externalIds, etc. Use before edit_* to inspect current state for merge decisions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.