Connect an AI assistant or application to Salsa Vida’s public Salsa and Bachata event listings and destination guides. The Model Context Protocol (MCP) gives compatible clients a standard way to search this information and link to its source.
Connect
Endpoint: https://mcp.salsavida.com/mcp
Transport: Streamable HTTP
Authentication: None. Public, read-only access.
Add this URL as a remote MCP server in a compatible client. Allow its four read-only tools when prompted. Clients decide which servers to connect to and when to use them. Having an MCP endpoint does not automatically connect Salsa Vida to every chatbot.
For Codex CLI:
codex mcp add salsa-vida --url https://mcp.salsavida.com/mcpFor Claude Code:
claude mcp add --transport http salsa-vida https://mcp.salsavida.com/mcpIn applications that support custom connectors, open their connector settings and add the endpoint above. Availability and account requirements depend on the client. Directory listings and reviews are separate from direct connections.
Available tools
search_locations: Find a city, region or country, including its stable location ID and geographic context.search_events: Find events by location, dates, dance, event type, Salsa style and language.get_event: Read an event’s essential details and scheduled occurrences within a date window.get_guide: Read an existing destination guide summary and its Salsa Vida links.
Use tool discovery for the current input and output schemas. Resolve ambiguous place names before searching. Prefer a stable location ID when several destinations share a name.
Example questions
- What Salsa socials are listed in San Francisco over the next two weeks?
- Find Bachata lessons in Tokyo and link to their details.
- Which festivals are scheduled in Spain during my travel dates?
- Show the Salsa Vida guide for Paris, France.
- When is this recurring event scheduled, and what information is still unknown?
Coverage and interpretation
The service covers Salsa Vida’s public locations, qualifying upcoming event listings and existing city, region and country guides worldwide. Event dates are searchable over a rolling year. Searches default to the next 14 days. The response gives the exact indexed date range. Instructor profiles, articles, Dancepedia and private research are outside this release.
The default date window starts on the current UTC calendar date. For “today” or “tonight,” pass the user’s local calendar dates explicitly. The index retains an extra preceding date to support places where the local date is still yesterday in UTC. Dates do not imply a timezone when the source has not provided one.
Responses include available titles, concise descriptions, venue and address, dates, known times, classifications, listed prices and Salsa Vida links. Missing information stays unknown. Published translations are used where available, with an explicitly labeled English fallback. A translated event shares the same source event and occurrence IDs.
Salsa style filters use only recorded classifications. Many listings do not yet have a style classification, so an empty style-filtered search does not prove that the style is unavailable in that destination.
Recurring dates are scheduled according to the recorded recurrence. They are not a claim that an organizer has confirmed every occurrence. Multi-day festivals are grouped as one event occurrence. A synchronization timestamp shows when our index was checked or updated, not when an organizer verified an event. Follow the event’s Salsa Vida page and organizer information before making travel plans.
Freshness and availability
The service checks for source changes about every five minutes. Responses identify source-check timestamps. A delayed source check is flagged after 15 minutes, degraded after one hour, and event results are withheld after 24 hours without a successful check. A synchronization failure produces a service error, not a false claim that no events exist.
The service is free to use. Adjustable usage and processing limits protect availability and operating costs. If a limit is reached, retry later or visit Salsa Vida directly. Public requests are never forwarded to live WordPress searches.
Usage limits
Initial limits are approximately 120 tool calls per minute per network IP, 20 results by default, 50 per page, and up to 10 pages per search. Requests are limited to 16 KB and responses to 128 KB. Pagination and truncation are explicit. Narrow broad searches when results are truncated. Shared networks can share a limit. Limits may change in response to demand or abuse.
Use normal MCP error handling and honor retry guidance. Avoid rapid retries, bulk replication and attempts to bypass access limits.
Attribution and visits
When using Salsa Vida results, identify Salsa Vida as the source and include the relevant event or guide link. Each result provides a clean canonical URL and a tagged visit URL. Use the canonical URL for source attribution and the visit URL for an optional “View on Salsa Vida” action. Do not represent incomplete or recurring information as independently verified.
Tool calls do not establish that an assistant cited a result or that a person visited the website. The tagged visit link helps us measure observable visits separately.
Privacy
We record compact usage measurements: tool, selected geography IDs, short normalized place-name searches, dance, Salsa style, event type, language, planning horizon, result count, response time, errors, cache status and self-reported client name. Client names are unverified. We do not store full conversations, full request or response bodies, or raw IP addresses in product analytics. Network addresses may be processed temporarily to apply abuse limits.
Cloudflare hosts the service and processes its analytics. Detailed tool analytics are retained for up to three months, and daily aggregates for 25 months. Provider sampling can make counts estimates. Tagged links use ordinary website analytics under the Salsa Vida Privacy Policy.
If you connect through Smithery, its gateway may proxy requests to Salsa Vida. That connection is also subject to Smithery’s privacy and usage policies; the direct endpoint above does not require Smithery.
Usage terms and support
The service is intended to help people discover dance events and destinations. Public access does not grant permission to republish the entire Salsa Vida database or reproduce protected descriptions at scale. Respect source attribution, published limits and the Salsa Vida Terms of Service. Event information may change, and availability is not guaranteed.
For integration questions, corrections or access issues, contact Salsa Vida. Include the tool name, approximate request time and a non-sensitive description of the issue. Please do not send private conversations or credentials.