Developer documentation · English

Waydone MCP server

Give AI agents access to your Waydone trip engine and your agency's client data through the Model Context Protocol. Any MCP client that supports remote HTTP servers can connect: Claude Code, Cursor, Windsurf, the official MCP SDKs, or an agent you build yourself. Usage is metered in credits per tool call.

What it is

The MCP server is part of Waydone for Agencies. Your organisation is the tenant: every API key belongs to one organisation, and every tool call is scoped to that organisation's trips and clients. An agent connected with your key can read and create trips and CRM clients, search live flights and hotels, and ask the planning engine for itineraries and destination knowledge.

Endpoint (Streamable HTTP, JSON-RPC 2.0 over POST):

https://lxfebcjlhkerngwhyrbc.supabase.co/functions/v1/mcp
Coming soon · Beta

Run your agency from your AI assistant

Waydone is becoming accessible to AI agents through the Model Context Protocol (MCP). Connect Claude or ChatGPT to your Waydone workspace and ask it to find a client, plan the trip, build the quote and send it, with your branding and your margins.

  • • Available today: API keys for developer tools such as Claude Code and Cursor.
  • • Coming soon: one-click sign-in from Claude and ChatGPT, no key to copy.
  • • Your organisation’s data only, with the same permissions as in the app.

1. Create an API key

  1. Sign in as an owner or admin of your organisation and open Agency → Studio.
  2. In API access (MCP), name the key after the client that will use it (for example “Claude Code — Sarah”) and click Create key.
  3. Copy the wd_live_… secret immediately. It is shown once and never stored: Waydone keeps only a hash. Revoke a key from the same card at any time.

The first key you ever create adds 250 trial credits to that organisation (once per user account, not per organisation).

2. Connect your agent

Claude Code

claude mcp add --transport http waydone https://lxfebcjlhkerngwhyrbc.supabase.co/functions/v1/mcp \
  --header "Authorization: Bearer wd_live_…"

Cursor, Windsurf and most JSON-configured clients

Add this to the client's MCP configuration (for Cursor: .cursor/mcp.json):

{
  "mcpServers": {
    "waydone": {
      "url": "https://lxfebcjlhkerngwhyrbc.supabase.co/functions/v1/mcp",
      "headers": {
        "Authorization": "Bearer wd_live_…"
      }
    }
  }
}

Claude.ai and Claude Desktop custom connectors

The claude.ai connector UI authenticates remote servers with OAuth and does not send a custom bearer header, so an API key alone cannot be pasted there yet. Until the OAuth sign-in below ships, use Claude Code, or bridge through a local proxy such as mcp-remote that injects the Authorization header.

Smoke test from a terminal

curl -s -X POST "https://lxfebcjlhkerngwhyrbc.supabase.co/functions/v1/mcp" \
  -H "Authorization: Bearer wd_live_…" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Supported methods: initialize, tools/list, tools/call, ping. The server answers each POST with a single JSON response; no SSE stream is needed.

Tools and credits

ToolCreditsWhat it does
usage_summary0Current credit balance and the last 10 usage events
list_trips1List your organisation's trips
get_trip1One trip with its bookings
create_trip1Create a trip under your organisation
list_clients1Your agency CRM clients
create_client1Add a CRM client
search_travel2Live flights and hotels (Duffel), or AI-curated activity ideas
ai_assist3Summarise, translate, extract, classify, rewrite or answer over text (20k chars max)
explore_destination5Structured insider knowledge about a destination
plan_trip10Full day-by-day itinerary

A key can be restricted to a subset of tools (scopes). Keys created from the Studio tab currently allow every tool.

Credits and billing

  • Credits are debited before a tool runs. With no credits left the call fails with JSON-RPC error -32002 and the tool does not run.
  • A tool call that fails on our side is refunded automatically.
  • usage_summary is free and returns your balance and recent usage.
  • Rate limit: 60 requests per minute per organisation.
  • Beyond the 250 trial credits, credit packs are not yet self-serve. Contact us from the contact page and we will top up your organisation while the credit store is being built.

Security and tenancy

  • Keys are stored as SHA-256 hashes with a short display prefix; the secret is shown once.
  • Every data tool filters on your organisation id. A key can never read another tenant's rows.
  • Only organisation owners and admins can create, list or revoke keys.
  • Text you send to the LLM tools is wrapped as untrusted input and length-capped; it never changes the engine's instructions.
  • Send the key only in the Authorization header. Tokens in the query string are rejected.
  • Treat a key like a password: one key per client, revoke it when the client is retired.

Authentication status and roadmap

Today: organisation API keys (wd_live_…), designed for headless agents and developer tools.

Next: OAuth 2.1 sign-in with your Waydone account, so you can add Waydone from the claude.ai and ChatGPT connector directories without handling a key. It is built and in final setup; request beta access to be among the first agencies to use it. API keys keep working unchanged.