MCP quickstart

Connect

Point your MCP-compatible client at:

https://mcp.evendo.com/mcp

The server is public and does not currently require authentication. Configure the remote server URL according to your specific MCP client or SDK, since configuration syntax varies by client. Complete protocol initialization before requesting tools.

Discover tools

Once initialized, the MCP client can send:

{"jsonrpc":"2.0","id":1,"method":"tools/list"}

tools/list returns six tools. Their exact input JSON Schemas are reproduced in Tool reference and as schemas/mcp-tools-snapshot.json.

Resolve, discover, expand

Call 1 — resolve Madrid

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "resolve_place",
    "arguments": {"name":"Madrid","place_type":"Cities","country_code":"ES"}
  }
}

A successful tool payload returns Madrid with id: "27799".

Call 2 — discover attractions

{
  "jsonrpc":"2.0","id":3,"method":"tools/call",
  "params":{"name":"find_venues","arguments":{"place_id":"27799","venue_type":"Attractions","limit":10}}
}

Call 3 — expand a selected place

{
  "jsonrpc":"2.0","id":4,"method":"tools/call",
  "params":{"name":"get_venue","arguments":{"id":"3127593"}}
}

The tool payload examples here are unwrapped JSON results. Your actual MCP SDK may deliver those payloads inside an MCP CallToolResult content structure. Let an SDK handle the content-block envelope, session and protocol-version negotiation.

Place Score discovery

{
  "place_id":"27799", "venue_type":"Attractions",
  "min_place_score":80, "sort_by":"place_score", "limit":10
}

Place Score filtering and sorting are live. See the Place Score guide.

After your first query

Read tool parameters, pagination, agent best practices and rate limits.