App

WeTravel integrations

Connect WeTravel to any other app, or use it from your AI client over MCP. WeTravel is an all-in-one operating system for multi-day travel businesses—build itineraries, manage bookings, collect payments, and pay suppliers effortlessly.

Connects with a tokenwetravel.com

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

Build solutions, not workarounds.

What do you want to automate with WeTravel?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

Set it up in your client
Claude Code

Run this in the directory you want to work in.

claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide (opens in a new tab)
Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

Setup guide (opens in a new tab)
Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide (opens in a new tab)
Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide (opens in a new tab)
Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

Setup guide (opens in a new tab)
Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

Setup guide (opens in a new tab)

Pair it

Connect WeTravel with another app

What your agent can do with WeTravel

Triggers and actions 3 triggers · 10 actions

  • Trigger
    Lead Updated

    Triggers when a WeTravel lead is created or updated (for example, when the person requests again or books).

  • Trigger
    New Lead

    Triggers when a new lead is captured for one of your WeTravel trips.

  • Trigger
    Transaction Updated

    Triggers when a WeTravel transaction is created or updated, such as a payment, refund or payout changing status.

  • Action
    Add payment link

    Creates a WeTravel payment link for a trip with its dates, currency, fee handling and price, optionally with a deposit and installment payment plan.

  • Action
    Add trip

    Creates a draft trip in WeTravel, which can then be built out and published.

  • Action
    Get order

    Returns a single trip order (booking), including amounts paid and due, packages and add-ons, participants and installments.

  • Action
    Get payment link

    Returns a WeTravel payment link by its UUID, including its trip and pricing details.

  • Action
    List leads

    Returns the leads (trip inquiries) in your WeTravel account, optionally filtered by trip, booking status, lead type and request date.

  • Action
    List orders

    Returns the orders (bookings) placed on a trip, with amounts paid and due, buyer and booked packages.

  • Action
    List transactions

    Returns the transactions (payments and refunds) on your WeTravel account, optionally filtered.

  • Action
    List trips

    Returns all trips in your WeTravel account, with their titles, destinations, dates and listing status.

  • Action
    Publish trip

    Publishes a draft trip so its booking page goes live on WeTravel, and returns the published trip.

  • Action
    Update trip

    Updates an existing draft trip's details, such as title, dates, group size, pricing currency and booking settings. Only the fields you fill in are changed.

Reviews

What our customers say

Questions

WeTravel, answered

Is there a WeTravel MCP server?

APIANT's MCP server at https://mcp.apiant.ai works with WeTravel. Add that address to any AI client that takes a remote MCP server and sign in once in your browser. Your client can then run WeTravel actions on demand, or have APIANT build, test and run automations that use WeTravel. Nothing to install.

What can start an automation from WeTravel?

Any of WeTravel's 3 triggers in the catalog, including Lead Updated, New Lead and Transaction Updated. Describe the moment in plain language and your agent picks the right one.

What can your agent do in WeTravel?

Any of WeTravel's 10 actions, including Update trip, Add payment link, Add trip and Get order. Your agent maps the data both ways and tests every scenario before it ships.

Can I use WeTravel directly from Claude, ChatGPT or Cursor?

Yes. Connect your AI client to APIANT once and it works with WeTravel two ways. Ask it to do something in WeTravel once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running on its own. A one-off action uses your plan's tasks the same way an automation step does.

Do I need to write code against the WeTravel API?

No. APIANT connects to the WeTravel API for you, with a token. Describe what you want in plain language and your agent builds it on the WeTravel triggers and actions in the catalog. If you need an endpoint that is not there yet, your agent reads the WeTravel API documentation and adds it.

Which apps can WeTravel connect to?

Any app in the catalog; the list on this page pairs WeTravel with each of them. If the other app is missing, point your agent at its API documentation and it builds the connector.

What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.