
TravelLog
io.github.jarm-devPublished by GitHub account jarm-devv1.1.5Updated Nov 11, 2026
Trip planner and travel log: read and add to your trips, itineraries, expenses and places lists.
The publisher's own server: travel.art
Overview
Hosted TravelLog connector that lets an assistant read your trips, itineraries, expenses and places lists, and add entries, bookings and suggestions.
- What you can do
- Read trips, itineraries, day and trip notes, pending suggestions, expenses and totals, travel history, and Been and Want to go lists
- Create trips, add entries, expenses, day notes and places, import past trips in bulk, and edit or remove itinerary entries
- File the assistant's ideas as labelled suggestions, then accept or dismiss them
- Add bookings you actually made as real entries
- Request an account-deletion email link, and on the sign-up address create an account and check its verification status
- When to use it
- Useful when you keep your travel plans in TravelLog and want an assistant to answer questions about a trip, log places and expenses as you go, or draft itinerary ideas for you to approve. Not needed if you don't use TravelLog.
- Requirements
- Remote streamable HTTP endpoint with OAuth 2.1 sign-in through a TravelLog account (Google, Apple or email); clients register themselves, so no client ID or secret is needed. Tools that cannot open a sign-in page use a personal access key sent as a bearer token. A separate sign-up address works without an account.
Installation
In SourceWeft
- Open TravelLog in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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.jarm-dev%2Ftravellog/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"travellog": {
"type": "http",
"url": "https://travellogapp.web.app/mcp"
}
}
}README
TravelLog MCP server
TravelLog is a trip planner and travel log. Plan trips day by day, log where you've been, and keep a list of places you want to go.
This is a hosted MCP server, not open source. TravelLog runs it for TravelLog users. This repository holds documentation only: there is no server code here to install or run. You connect your AI assistant to the hosted address below and sign in with your TravelLog account.
Contents
- What it does
- Set up your assistant
- Sign-in
- Permissions
- Tools
- Limits
- Undo and disconnect
- Privacy
- Tested with
- Support
What it does
Once connected, your assistant can read your TravelLog trips: each trip's itinerary, trip and day notes, expenses, a travel history summary (past trips, days away, countries and cities) and your Been and Want to go places lists. If you allow it, it can also create trips, add its ideas to a trip as suggestions you add or dismiss, add bookings, entries, expenses, day notes and places you ask for, import past trips in bulk, and edit or remove itinerary entries.
Its own ideas never go straight into your plan: they arrive as suggestions labelled "From ", and nothing becomes a real entry until you add it (in the app, or by asking the assistant to). The assistant is told to add things directly only when you asked for that exact thing, and to ask you before it edits or removes anything.
Example: ask "What's on my Lisbon trip tomorrow?" and the assistant reads that day of the trip's itinerary.
The full tool reference is on the TravelLog website: https://travellogapp.web.app/mcp-docs. Setup help for people (not developers) is at https://travellogapp.web.app/connect-ai.
Set up your assistant
Menus change from time to time, and custom connectors may need a paid plan. If a step doesn't match, look for "connectors" or "MCP" in your assistant's settings.
Claude
- In Claude, open Settings › Connectors and choose Add custom connector.
- Paste the address and choose Add:
https://travellogapp.web.app/mcp - Claude opens the TravelLog sign-in page. Sign in and allow access.
ChatGPT
- In ChatGPT, open Settings › Connectors and turn on developer mode.
- Add a custom MCP server with the address:
https://travellogapp.web.app/mcp - ChatGPT opens the TravelLog sign-in page. Sign in and allow access.
Developer mode depends on your ChatGPT plan.
Grok
- On grok.com, add a custom connector.
- Paste the address:
https://travellogapp.web.app/mcp - Grok opens the TravelLog sign-in page. Sign in and allow access.
The exact menu names on grok.com have not been checked by the TravelLog team.
Other MCP clients
Your own bot: access keys
For a tool that can't open a sign-in page (for example a bot you build on the xAI Grok API), create a personal access key at https://travellogapp.web.app/account or in the TravelLog app under Settings › Connected apps › Create access key:
- Name it, choose Read only or Read & write, and choose when it expires: 30 days, 90 days (the default), 1 year or never.
- The key starts with
tlpat_and is shown once. Copy it then; TravelLog stores only a one-way hash of it. - Give your tool the address above and send the key as a bearer token (
Authorization: Bearer tlpat_…), or paste it where the tool asks for an API key or token. - You can have up to 5 active keys and revoke any of them at once. Whoever holds a key can use your TravelLog as it allows, so keep it secret.
No TravelLog account? Let your assistant create one
Add this address instead, with no sign-in:
Your assistant asks you for the same things TravelLog asks at sign-up (your email, the name others see, a unique @handle, and whether you accept the Terms of Service and Privacy Policy and are 18 or older) and may answer yes only if you told it to. TravelLog then emails you a verification link: tapping it is the only thing you do. The assistant then receives an access key for your new account (Read & write, expires after 90 days, listed under your access keys where you can revoke it) and the same chat is signed in.
Until you tap the link, the sign-up connection lists only the three sign-up tools; any other tool answers that it needs a TravelLog account and does nothing. Once the account is verified, the connection tells the assistant its tool list changed, and the assistant is told to list the tools again. The sign-up expires after 24 hours, and if nobody taps the link within 3 days, TravelLog deletes the account and frees the @handle.
Afterwards, use the normal address above for everyday use. You can also create an account yourself at https://travellogapp.web.app/account, or on the sign-in page your assistant opens. The app is optional; install it later and everything is there.
Sign-in
TravelLog uses OAuth. When you connect, your assistant opens TravelLog's connect page, where you:
- Sign in with your TravelLog account (Google, Apple or email), or create one on the same page.
- See which assistant is asking, which website it will return you to, and what it wants to do (see Permissions). You can switch on Read only.
- Tap Allow.
Nothing is shared until you tap Allow. The assistant gets an access key that works for 1 hour and renews it with a renewal key that lasts 60 days and is extended every time it is used, so a connection the assistant hasn't renewed for 60 days ends on its own.
An account made on the website must verify its email before an assistant can change anything; until then the assistant can only read. Accounts made in the TravelLog app are not affected.
Permissions
The connect page lists what the assistant asked for. You can accept it all or switch on Read only, which keeps
only trips:read. Access keys are either Read only (trips:read) or Read & write (all four).
Tools
21 tools once you are signed in, plus 3 sign-up tools on the sign-up address. Server version 1.5.0. "Read" tools
change nothing. Every change tool takes a clientRequestId, so a retried request happens only once.
Read (trips:read)
Trips (trips:write)
Suggestions (suggestions:write)
Bookings (bookings:write)
Sign-up (only on https://travellogapp.web.app/mcp?signup=1, no sign-in)
Arguments and full descriptions for every tool: https://travellogapp.web.app/mcp-docs.
Limits
Per assistant you connect, and per access key, on your account:
- 60 calls an hour (20 of them changes) and 600 calls a day.
- Imports have their own limit for your account (every assistant and key together): 10 import calls an hour and 200 trips a day, 20 trips a call, 80 entries and 15 day notes a trip. Each import call still counts toward the 60 an hour and 600 a day, but not toward the 20 changes.
- Up to 40 suggestions a call (
add_suggestions,accept_suggestion,dismiss_suggestion). - Places lists hold up to 500 places.
- Up to 5 active access keys.
- Account deletion links: 1 a minute, 3 a day. Each link expires after about an hour.
- Assistant sign-up: 3 a minute and 10 new accounts a day per network, 3 a day per email address.
Connecting an assistant, and every tool, is free with a free TravelLog account; no tool needs TravelLog Pro. No TravelLog MCP tool runs AI on TravelLog's side.
Undo and disconnect
Suggestions an assistant adds are labelled with its name and stay suggestions until you add or dismiss them. Everything else it adds or changes behaves like your own edits: change or remove it in the app or ask the assistant to. There is no one-step undo of an assistant's changes.
In the TravelLog app, go to Settings › Connected apps, or on the website go to https://travellogapp.web.app/account:
- Disconnect (an assistant) or Revoke (an access key) stops its access at once and deletes TravelLog's request records for it. Anything it already added stays in your trips. It does not delete your account.
- Sign out of all assistants and keys disconnects every assistant and revokes every key in one step.
You can also disconnect from inside the assistant where it offers that, but disconnect in TravelLog to be sure. Deleting your TravelLog account disconnects every assistant and revokes every key.
Privacy
Full policy: https://travellogapp.web.app/privacy (Section 3a covers AI assistants).
- What it can see: only what you allowed: your trips' names, dates and destinations (your own and trips shared with you); each trip's itinerary entries (title, category, place, local start and end times, notes); trip and day notes; the suggestions assistants have added for you; your Been and Want to go lists with your notes; a travel history summary worked out when asked; and, on trips you own or can edit, expenses (title, amount, currency, category, date, who paid and the split) and totals.
- What it never sees: location tracking data of any kind (location points, detected stops, distances or times recorded by tracking), your private entries and notes, other members' private entries, settlement payments, receipts, photos, confirmation codes, other people's profiles, comments, email addresses or invite links. On a trip shared with you as a viewer it cannot see expenses and can only read.
- What it can't do: delete trips, share trips, change your account, or see, change or remove another member's private entries or anyone's own visit records. Health-care places are not accepted as suggestions or in your places lists.
- What TravelLog keeps: only what you asked the assistant to store; a record of each request (which assistant, which action, whether it worked and when) with no trip content, for 90 days; access keys in hashed form only; and, when an assistant adds a place to your lists, a short note of that addition (name and coordinates) for 30 days so a phone that hasn't synced yet doesn't drop it.
- The assistant's company: what your assistant reads goes to the company that runs it, under that company's own privacy policy, and it may keep it after you disconnect. TravelLog doesn't sell this data or use what an assistant sends it for advertising, profiling or AI training.
- Deletion: an assistant can't delete your account. It can only ask TravelLog to email you a link that opens a page showing what will be deleted, where you confirm with one tap. Deleting your account, in the app, on the website or from that link, deletes your data, disconnects every assistant and revokes every key.
Tested with
These were run by the TravelLog team against the TravelLog server code:
- MCP Inspector CLI 2.10.1:
tools/liston the current and older protocol versions and alist_tripscall (on the first release of the server). - The MCP conformance suite (
@modelcontextprotocol/conformance0.2.0-alpha.12) on protocol versions2026-07-28and2025-11-25(on the first release of the server). - A scripted Streamable HTTP client against local test servers: the full OAuth flow (client registration,
sign-in, consent, code exchange, key renewal, revoke), permission checks, every tool listed above, access keys,
the limits, Disconnect, the assistant sign-up flow from
create_accountto a signed-in session, and account deletion.
The Claude, ChatGPT and Grok steps above are the ones on the TravelLog website; they are not yet listed here as tested.
Support
Email us at [email protected]. Privacy questions: see the privacy policy. Setup help: https://travellogapp.web.app/connect-ai. Tool reference: https://travellogapp.web.app/mcp-docs.
Source: README.md at commit d153691
Tools
0Version history
1- v1.1.5LatestNov 11, 2026
Score
75% 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
- License10 pts
Declare a license in the repository or the registry entry.
Other Travel integrations

travel.art
art.travelOfficial publisher
Read-only travel.art server that lets an assistant look up art events, museum visitor guides, layover itineraries and city art-trip suggestions.

OlaChill Vietnam — Travel and Private Transport
Published by GitHub account dang13021993
Read-only Vietnam travel catalog that lets an assistant look up charter coach and private car classes and explain how to request a quote.

MonoEsim — Travel Connectivity for AI Agents
Published by GitHub account Andrii-Tiurin
Lets an assistant search, compare and quote travel data eSIM plans in EUR, check phone compatibility, and hand customers a Stripe checkout link.

Alibaba Travel
Published by GitHub account sepehr071
Read-only search of Alibaba (alibaba.ir) Iran travel listings: trains, buses, flights, hotels, holiday homes and tours, with prices and seats.

Travel Tracker
Published by GitHub account changzhiai
Travel checklists in 9 languages on six maps: world, USA, US NPs, Europe, China, India.