MCP overview

The Evendo Location MCP exposes an agent-friendly interface to Evendo's World Model.

• Remote MCP endpoint: https://mcp.evendo.com/mcp
• Authentication: None currently required
• Current limit: 200 requests per minute
• Side effects: None; all six tools have readOnlyHint: true
• Tool inventory: resolve_place, find_venues, search_venues, list_subareas, get_venue, get_venues

MCP is a protocol for letting a compatible AI client discover available tools and invoke them with JSON arguments. It is not equivalent to sending a raw GraphQL query to the MCP URL.

The six-tool workflow

1. resolve_place: Convert “Madrid” to geographic container 27799.
2. find_venues: Get restaurants, bars, shopping, attractions or landmarks anywhere in that container's subtree.
3. search_venues: Use keyword lookup for things like “ramen”, “rooftop”, “flea market” while preserving geography as a separate constraint.
4. get_venue: Expand a selected result into detailed place knowledge.
5. get_venues: Fetch full details for up to 50 places in one call, such as every stop of an itinerary.
6. list_subareas: Explore immediate child geographic areas.

Do not assume that MCP exposes the underlying GraphQL root operations directly. MCP has six tools, while GraphQL has six root queries.

Read the quickstart, full tool reference and agent guide.