TravelOwl

io.github.ameinnaqviPublished by GitHub account ameinnaqviv0.2.0Updated Nov 11, 2026

Plan and manage TravelOwl trips from ChatGPT, Claude and other MCP assistants.

The publisher's own server: travel.art

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

TravelOwl connects MCP assistants to TravelOwl so they can plan and manage trips from within a chat.

What you can do
  • Plan and manage TravelOwl trips from an MCP assistant such as ChatGPT or Claude.
  • No tool list, instructions or README was supplied, so the specific actions available are not documented here.
When to use it
Useful if you already use TravelOwl for trip planning and want an assistant to work with your trips directly instead of switching apps.
Requirements
A remote MCP endpoint at mcp.travel-owl.co.uk; no local package or environment variables. Authentication is OAuth and required, so you need a TravelOwl account and must complete the OAuth sign-in flow.
Before you install
OAuth access lets the assistant act on your TravelOwl account, and trip changes may be created or modified on your behalf. The exact scope of permissions and which data is shared with the assistant are not documented in the supplied material.

Installation

In SourceWeft

  1. Open TravelOwl in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.ameinnaqvi%2Ftravelowl-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "travelowl": {
      "type": "http",
      "url": "https://mcp.travel-owl.co.uk/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.2.0LatestNov 11, 2026
  2. v0.1.1Sep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Travel integrations