Skip to content
Travel Log

TravelLog MCP / permissioned tools

Your assistant can use the trip without owning the trip.

Connect ChatGPT, Claude, Cursor, Codex, or another MCP client to TravelLog's authenticated tools for private trips, public destination knowledge, and business workflows. The assistant gets scoped actions, not raw database access.

Choose a connectorReview security

Remote MCP URL

https://mcp.travellog.app/mcp

The same Streamable HTTP endpoint powers ChatGPT, Claude, Cursor, Codex, and future MCP clients.

OAuth discoveryhttps://mcp.travellog.app/.well-known/oauth-authorization-serverProtected resourcehttps://mcp.travellog.app/.well-known/oauth-protected-resource

Built for private travel data

Every tool call stays tied to the signed-in user.

Authentication required

TravelLog rejects anonymous MCP calls and validates bearer tokens before any tool runs.

Scoped access

Default scopes cover profile, trips, timelines, memories, media metadata, maps, and public knowledge.

Privacy boundaries

Private trips use membership checks; media uses metadata by default; signed URLs require explicit enablement.

Auditable actions

Sensitive reads and write tools are scope checked and designed for reviewable assistant workflows.

Connectors

Use one endpoint across the assistant tools you already use.

ChatGPT

Connect TravelLog as a ChatGPT app.

ChatGPT can use the authenticated TravelLog MCP endpoint with read-only search and fetch tools for public destination knowledge, plus scoped traveler tools after OAuth.

  1. Open ChatGPT connector or app setup.
  2. Add the TravelLog remote MCP server.
  3. Use https://mcp.travellog.app/mcp.
  4. Connect and approve the requested TravelLog scopes.

Claude

Add TravelLog as a custom connector.

Use Claude's custom connector flow with the TravelLog remote MCP URL. Team and Enterprise owners add it once for the organization; Pro and Max users can add it from their connector settings.

  1. Open Claude connector settings.
  2. Add a custom web connector.
  3. Enter https://mcp.travellog.app/mcp.
  4. Connect and complete TravelLog OAuth.

Cursor

Install the TravelLog MCP server in Cursor.

Cursor can use the same remote MCP endpoint through Marketplace install or manual MCP JSON. OAuth discovery keeps tokens out of project files.

  1. Open Cursor Customize and MCP settings.
  2. Add a remote MCP server named TravelLog.
  3. Use https://mcp.travellog.app/mcp.
  4. Authenticate when Cursor prompts for access.

Codex

Use the packaged TravelLog plugin.

The repo-local Codex plugin bundles TravelLog skills with the authenticated MCP server, so coding agents get scoped tools plus project-specific operating instructions.

  1. Install or load the TravelLog Codex plugin.
  2. Enable the TravelLog MCP server.
  3. Grant only the scopes needed for the task.
  4. Use signed media access only when explicitly required.

Default access

Useful by default, narrow by design.

Start with read-oriented traveler scopes. Add business or social write scopes only when the assistant workflow actually needs them.