Connect your AI agent
to Amigo Treks.

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

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.

[mcp_servers.amigo]
url = "https://www.amigotrekking.com/api/mcp/public"

See the official Codex MCP configuration guide.

Other AI agents

{
  "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.

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.

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.

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.

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

The older search and fetch tools remain available for existing clients. Prefer search_trips and get_trip for new integrations.

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.
• 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.

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.

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.