Self-Hosted Travel Planner TREK Draws Attention with Built-in MCP Server

TREK, a self-hosted real-time collaborative travel planner, has made its debut on GitHub Trending. Developed by mauriceboe, TREK is gaining attention as an all-in-one tool that integrates maps, budget management, packing lists, travel journals, and AI capabilities.

The standout feature of TREK is its built-in Model Context Protocol (MCP) server. With OAuth 2.1 authentication, the MCP server provides access to over 150 tools for AI assistants, enabling direct intervention in creating or modifying travel plans and retrieving information.

Overview of Features

TREK offers a comprehensive suite of features. For itinerary planning, it includes drag-and-drop scheduling and interactive maps powered by Leaflet and Mapbox GL, featuring 3D buildings, terrain, photo markers, clustering, and route visualization. Location searches can be conducted via Google Places (offering photos, ratings, and operating hours) or OpenStreetMap (free and API key-free).

Locations can be imported from shared lists on Google Maps or Naver Maps, as well as GPX, KML/KMZ, and GeoJSON files. Daily notes can be timestamped, tagged with icons, and rearranged using drag-and-drop functionality. The route optimization feature automatically organizes locations and exports them to Google Maps. Weather forecasts are provided by Open-Meteo, offering 16-day forecasts (no API key required) and fallback options using historical climate data.

Travel Management and Collaboration

The travel management features include handling flight, accommodation, and restaurant reservations. TREK supports status updates, confirmation numbers, file attachments, and imports from reservation confirmation emails or PDFs via KDE Itinerary. Expense management includes Splitwise-style cost splitting, detailed breakdowns per person or per day, settlements, and multi-currency support.

The packing list feature allows categorization, templates, member assignments, and progress tracking. Bag weight tracking is visualized in an iOS-style distribution chart. Document management enables attachment of tickets or PDFs to trips, locations, or reservations, with support for files up to 50MB. For documentation, users can export a comprehensive travel itinerary, including covers, images, and notes, as a PDF.

The collaboration functionality centers on real-time synchronization via WebSocket. Changes are instantly reflected across all connected users. Multi-user travel management includes role-based access control, with invite links that can be single-use or reusable, and expiration dates can be set for invitations.

Authentication and Security

Authentication supports Single Sign-On (OIDC) with providers like Google, Apple, Authentik, and Keycloak. Multi-factor authentication (TOTP with backup codes) and passwordless login via passkeys (WebAuthn, including fingerprint, face recognition, PIN, or security keys) are also supported. Administrators can enable or disable features as needed.

Mobile Compatibility and Add-ons

For mobile users, TREK can be installed via a browser on both iOS and Android. It includes offline support with Service Worker caching of tiles, APIs, and uploads (using Workbox), a native-style full-screen UI, a theme-compatible status bar, and a splash screen. The touch-optimized layout is compatible with safe-area guidelines.

Add-ons are available as toggleable features for administrators and include:

• Packing lists and To-Do items (with templates, member assignments, and bag tracking options)
• Expense tracker (split costs, multi-currency support)
• Document management (attaching files to trips, locations, and reservations)
• Collaboration tools (chat, shared notes, voting, daily check-ins)
• Personal vacation planner (calendars, public holidays for 100+ countries, rollover tracking)
• World map (visited countries, bucket lists, travel statistics, streak tracking)
• Travel journal (magazine-style records with photos, maps, and mood tracking)
• AirTrail integration (syncs with self-hosted AirTrail instances for flight booking management)

Technology Stack and MCP Server

While detailed technical specifications of TREK’s technology stack are not fully disclosed, its primary technologies include WebSocket-based real-time synchronization, offline support via Service Worker, and an MCP server authenticated with OAuth 2.1.

The MCP server provides over 150 tools, enabling AI assistants to directly execute tasks such as creating travel plans, retrieving reservation details, and optimizing routes. While the types of AI assistants supported and specific integration methods are not yet disclosed, it is presumed that any client compatible with the MCP protocol can utilize these features.

Value of Self-Hosting

TREK’s self-hosting foundation is significant for data privacy. Travel plans often involve sensitive information like passport details, credit card data, and personal location history. Self-hosting eliminates the risk of storing such data on third-party servers.

Additionally, self-hosting facilitates customization and feature expansion. The add-on toggle functionality allows for flexible configurations tailored to teams or families.

Comparison with Competitors

Existing travel planning tools include TripIt, Google Trips (now discontinued), and Trail Wallet. However, none of these support self-hosting, and they impose limitations on data ownership and privacy.

Open-source travel planning tools like OpenTripPlanner and GraphHopper focus on route optimization, particularly for public transit, but lack itinerary management, cost splitting, and collaboration features like those offered by TREK.

TREK differentiates itself by combining comprehensive functionality, self-hosting, and AI integration, setting it apart from existing tools.

Future Developments

Although TREK has just appeared on GitHub Trending, its extensive features and advanced design, including the built-in MCP server, are drawing significant attention within the self-hosting community. It could become a compelling option for users who prioritize keeping their travel data private or want to streamline group travel planning.

However, the complexity of initial setup and operational requirements might pose challenges. Additionally, using the Google Places API requires an API key, which incurs costs for large-scale usage.

As the MCP server’s use cases and supported AI assistants become clearer, interest in TREK’s capabilities is expected to grow further.

Editorial Opinion

TREK’s arrival signals a new direction for self-hosted applications. By embedding an MCP server, it allows AI assistants to directly manipulate travel plans—a feature that transcends mere functionality. Over the next 3–6 months, similar approaches may emerge in other self-hosted applications. Particularly, integration with personal information management tools like Notion or Obsidian may accelerate.

In the long term, integrated self-hosted tools like TREK could potentially replace SaaS-based travel planning tools like Google Trips and TripIt. This shift is driven by increasing user demand for data sovereignty and improved ease of operating self-hosted environments. However, whether average users can handle the complexities of self-hosting remains an open question.

Should MCP servers become standardized, interoperability of travel data across different AI assistants may become a reality. Nonetheless, there is still considerable room for improvement in areas such as the security design of the MCP protocol and the management of authentication credentials. TREK’s implementation of OAuth 2.1 provides a promising start.

References

• mauriceboe/TREK - GitHub — Published on 2026-06-26
• Model Context Protocol Official Documentation