Skip to main content

Cookie consent

We use essential cookies to keep the website working. With your permission, we also use cookies for analytics and personalised advertising.

Connect your AI agent
to Amigo Treks.

Give your agent access to Amigo’s published trips, itineraries and planning tools through Model Context Protocol (MCP).

Transport
Streamable HTTP
Authentication
None
Protocol example
2025-11-25

1. Connect without an API key

No account, developer registration or API key is required. Customers can explore published trips, submit enquiries and request bookings through their AI agent. Enquiries and booking requests require explicit consent.

2. Configure your MCP client

Production MCP endpoint
https://www.amigotrekking.com/api/mcp/public

Choose a remote MCP client with Streamable HTTP and no authentication.

Codex

Add this entry to your user-level ~/.codex/config.toml, then reconnect.

TOML · Codex MCP configuration
[mcp_servers.amigo]
url = "https://www.amigotrekking.com/api/mcp/public"

See the official Codex MCP configuration guide.

Other AI agents

JSON · Generic remote MCP settings
{
  "transport": "streamable-http",
  "url": "https://www.amigotrekking.com/api/mcp/public"
}

ChatGPT connection: add the MCP endpoint and select No Authentication. No API key or OAuth sign-in is needed. Your agent must ask for explicit consent before sending customer details or a booking request.

3. Verify your connection

Your MCP client normally handles this sequence. To troubleshoot from a terminal, send these requests in order. They only read data.

Bash · Initialize
curl 'https://www.amigotrekking.com/api/mcp/public' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json, text/event-stream' \
  --header 'MCP-Protocol-Version: 2025-11-25' \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"amigo-agent","version":"1.0.0"}}}'

A successful response contains result.protocolVersion, result.serverInfo and result.capabilities. For these examples, use the supported 2025-11-25 protocol. If negotiating another version, use the returned version for subsequent requests.

Bash · Notify that initialization is complete
curl 'https://www.amigotrekking.com/api/mcp/public' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json, text/event-stream' \
  --header 'MCP-Protocol-Version: 2025-11-25' \
  --data '{"jsonrpc":"2.0","method":"notifications/initialized","params":{}}'

The notification has no request ID and normally returns HTTP 202 without a body.

Bash · List available tools
curl 'https://www.amigotrekking.com/api/mcp/public' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json, text/event-stream' \
  --header 'MCP-Protocol-Version: 2025-11-25' \
  --data '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'

Read result.tools for the authoritative input schemas and safety annotations. The server is stateless; these examples do not require a session ID.

Bash · Search Everest trips between 10 and 16 days
curl 'https://www.amigotrekking.com/api/mcp/public' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json, text/event-stream' \
  --header 'MCP-Protocol-Version: 2025-11-25' \
  --data '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"search_trips","arguments":{"destination":"Everest","min_days":10,"max_days":16,"limit":3}}}'

Successful tool data appears in result.structuredContent. Check result.isError before using it: a tool validation error can arrive with HTTP 200. Use returned trip IDs and URLs rather than guessing them.

4. Plan using Amigo’s live data

search_trips

Find published trips by region, duration, season, difficulty or budget.

get_trip

Retrieve an exact trip’s itinerary, inclusions and published details.

recommend_trips

Rank trips against the traveler’s stated preferences.

compare_trips

Compare two to five trips as structured data.

render_trip_comparison

Open the interactive planner in a client that supports MCP Apps UI.

get_departures

Read published dates and their availability verification state.

get_trip_price

Get a server-calculated catalog estimate for the party size.

get_packing_options

Find packing routes, countries, activities and itinerary defaults.

generate_packing_list

Build a packing checklist with quantities, bags, guidance and a link to the website generator.

get_site_overview

Find official company, support and policy links.

For interactive trip planning, use search_trips and get_trip. Research clients can use the standard search and fetch tools described below.

Try these prompts after connecting

  • Find Amigo Everest region treks between 10 and 16 days.
  • Compare Amigo’s Everest Base Camp and Annapurna Circuit treks.
  • Create a packing list for my Everest Base Camp trek in October.
  • I have 12 days in Nepal in October and want a moderate trek. Which Amigo trips fit?

Use published data for prices, difficulty, itinerary and altitude. A suitable travel month does not prove a departure exists. Claim availability only when the returned data explicitly verifies it. Clients without MCP Apps UI can use compare_trips for a text comparison.

Make a packing list in chat

Ask your agent for a packing list for your trip and travel month. It can use get_packing_options to find the route, then generate_packing_list to prepare gear quantities, bag assignments and practical notes from the same catalog as our website.

Bash · Generate an October Everest Base Camp packing list
curl 'https://www.amigotrekking.com/api/mcp/public' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json, text/event-stream' \
  --header 'MCP-Protocol-Version: 2025-11-25' \
  --data '{"jsonrpc":"2.0","id":5,"method":"tools/call","params":{"name":"generate_packing_list","arguments":{"route":"everest-base-camp","month":10}}}'

These two tools need no contact details and do not submit an enquiry. Your agent should use the duration, overnight altitude and luggage arrangements from your confirmed itinerary. For a combined holiday, add the countries and activities you plan to visit.

The result includes a settings link to the packing list generator. It leaves out personal care preferences and checklist progress. You can adjust those choices and save the list in your browser. Website download, print and share actions use the website’s contact form.

Confirm rental availability, equipment provided by your package and airline baggage allowances before departure. For a climb or expedition, use your leader’s final equipment list.

Research with official sources

Use search to find published trips by a natural-language query, then pass a returned ID to fetch. The result includes readable trip information and the official page URL to cite. This interface supports compatible research clients; your client controls how citations appear.

Bash · Fetch a trip document for research
curl 'https://www.amigotrekking.com/api/mcp/public' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json, text/event-stream' \
  --header 'MCP-Protocol-Version: 2025-11-25' \
  --data '{"jsonrpc":"2.0","id":4,"method":"tools/call","params":{"name":"fetch","arguments":{"id":"trip:everest-base-camp-trek"}}}'

Cite the returned url when using trip information. Treat catalog_updated_at as the source record’s update date. Recheck prices with get_trip_price and dates with get_departures before presenting them as current.

Connecting Amigo’s MCP server gives your agent access to Amigo’s catalog. It does not make Amigo appear automatically in general ChatGPT search results. Website discovery and connected-agent access are separate.

Travelers can also read the company background, meet the team, and check published company documents and memberships on the website.

Enquiries and booking requests

submit_trip_enquiry stores a private enquiry and queues a staff email notification. Recap the necessary contact and trip details, obtain explicit permission to store and share them with Amigo, and use the tool’s documented retry key.

submit_booking_request needs the prior enquiry reference and its private continuation proof, the selected trip, explicit booking-request consent and acknowledgement that it is request-only. Keep the proof private. Follow the current schemas from tools/list and reuse an idempotency key only for retries of the same submission.

A received request awaits staff review. It does not reserve seats, confirm availability, charge a card or confirm a booking. Do not collect passport details, payment credentials, passwords or medical records through these tools.

Read Amigo’s privacy policy

Troubleshooting

401 · Older deployment
This endpoint requires no credentials. Confirm the latest backend release is deployed and the URL is correct.
403 · Origin denied
For browser-based clients, ask Amigo to review the exact client origin. Use the supported frontend MCP endpoint.
400 · Protocol error
Check the JSON-RPC body and negotiated MCP-Protocol-Version. Include both application/json and text/event-stream in Accept.
429 · Rate limited
Respect Retry-After. Public access allows up to 120 requests per minute and 1,000 per hour per IP; enquiry and booking tools also have tighter limits.
502 / 504 · Unavailable
Retry read requests with backoff. For a write retry, preserve its original idempotency key and payload.
Tool or UI missing
Refresh tools/list, check the client’s enabled-tool settings and MCP Apps support. Use the structured comparison tool when UI is unavailable.

Need help connecting?

Send the client name, failing step and HTTP status to Amigo. Remove keys, continuation proofs and traveler contact details from any diagnostic example.