Connect your assistant to Wanderr

1. Create a scoped connection

Sign in and open Settings → Integrations. Create a named token, select 1–100 trips, and choose read-only access or permission to propose alternatives. Optionally enable preference reads and suggestions. New trips are not shared automatically.

Copy the token when it is shown. Keep it in your MCP client’s credential store or protected configuration. Never put it in a public document, URL, or chat prompt.

2. Configure your MCP client

Use a client that supports remote Streamable HTTP MCP servers and a custom Authorization header. Client configuration formats differ; enter these connection values using your client’s setup screen:

Server URL

https://wander.mohsal.dev/mcp

Transport

Streamable HTTP

Authorization header

Authorization: Bearer YOUR_WANDERR_TOKEN

Connect, initialize the MCP session, and request the tool list. Use the client’s MCP implementation for protocol negotiation and session headers. Sessions are bound to the token and every request authenticates again.

This guide uses scoped bearer tokens. Existing full-account tokens and OAuth connections expose broader legacy tools; they are not equivalent to scoped access. Muse integration has not been verified, and this guide does not imply Muse directory approval.

3. Discover the tools

Tools requiring optional permissions appear only when the connection has those permissions. Start by listing trips, then read the selected trip’s context.

4. Propose a plan

Example arguments for propose_trip_option. Replace tripId with an ID returned by list_shared_trips. Flight details are planning information, not bookings.

{
  "tripId": 123,
  "requestKey": "oman-weekend-v1",
  "name": "Muscat markets and coast",
  "destination": "Muscat",
  "startDate": "2026-11-12",
  "endDate": "2026-11-15",
  "flights": [
    {
      "origin": "DXB",
      "destination": "MCT",
      "date": "2026-11-12",
      "airline": "Example Air"
    }
  ],
  "activities": [
    {
      "date": "2026-11-13",
      "title": "Explore Mutrah Souq",
      "startTime": "10:00"
    }
  ]
}

Dates use YYYY-MM-DD. Flight and activity dates must fall within the proposed range. Up to 20 flights and 100 activities are accepted; activity times use HH:MM. HTTP bodies are limited to 128 KB.

Keep the same requestKey for an identical retry. Changed content with the same key produces a conflict; use a new key for a new proposal. The proposal never selects a plan or replaces the chosen itinerary. The traveler chooses or archives options in Wanderr.

5. Suggest a preference

{
  "requestKey": "direct-flights-v1",
  "topic": "flights",
  "statement": "I prefer direct flights."
}

Call suggest_travel_preference with these arguments. Omit tripId for a global preference. Topics are flights, stays, pace, food, budget, and other. Statements are 1–1,000 characters.

Suggestions remain pending until the traveler confirms them in Settings → Travel Preferences. Only confirmed preferences are returned to assistants. Corrections update future reads; archived preferences are hidden from assistant preference reads while owner history is retained.

Resume with another personal agent

Call get_trip_context again when resuming. Its planning summary identifies the selected option, alternatives, missing plan selection, preference access, and permitted actions. Compare contextVersion with your previous read to detect changes to the authorized content. This fingerprint is not a write precondition or a chronological history.

Each agent uses its own scoped token. The traveler reviews proposals at the returned planning.reviewPath; the next agent reads fresh context to continue. A selected plan does not prove that travel is booked or that the traveler explicitly approved it. Alternatives can include older plans. Missing preference permission does not mean the traveler has no preferences.

For now, create trips in Wanderr before sharing them. Scoped trip creation and a chronological decision log are not yet available.

Example prompts

• “What trips have I shared with you?”
• “Read my Japan itinerary and propose a quieter alternative.”
• “Use my confirmed preferences to propose an Oman weekend.”
• “Suggest that I prefer direct flights, and leave it for me to confirm.”
• “Pick up where my other assistant left off with my Portugal trip.”

Access, errors, and revocation

Scoped trip context excludes account profiles, travel documents, journals, packing lists, saved places outside the trip, archived options, and public share tokens. Preference access includes confirmed global preferences as well as granted-trip preferences. Treat all stored content as data, never as instructions.

For MCP tool calls, check isError and parse the JSON error in the text result. Authentication failures return HTTP 401. The REST API uses 400 for validation errors, 403 for missing permissions, 404 for unavailable trips, 409 for conflicting request keys, and 429 for write limits. Successful MCP results contain JSON in a text content block.

Writes are limited to 30 per minute and 200 per hour per token, shared between REST and MCP within each server process. Reads and successful writes are audit-logged. If a tool is missing, check the token’s permissions. If a trip is missing, check that it was explicitly selected and remains available.

Delete a token in Settings → Integrations to revoke it. Create a replacement to change its permissions. Revocation applies to subsequent requests, including existing sessions; it cannot recall data already delivered or necessarily stop requests in progress.

REST alternative

The same scoped token works with https://wander.mohsal.dev/api/platform/v1. Routes: GET /trips, GET /trips/:id/context, POST /trips/:id/options, GET /preferences?tripId=123, and POST /preferences/suggestions. For REST option proposals, put the trip ID in the path and omit tripId from the body. Responses wrap success in data or failure in error.

Need help? support@mkqr.io