Tabiori Editor MCP

Tabiori Editor MCP lets signed-in Tabiori users create and edit travel plans (itineraries, schedules, checklists, notes) through MCP-compatible clients such as ChatGPT Developer Mode.

Endpoints

• MCP server: https://tabiori.com/editor/mcp
• OAuth issuer: https://tabiori.com/oauth
• Protected resource metadata: https://tabiori.com/.well-known/oauth-protected-resource

Authentication

The MCP server requires OAuth 2.1 with PKCE. Users sign in with their Tabiori account on the consent screen and grant scopes:

• editor:read — read plans the user belongs to
• editor:write — create and update plans, schedules, and related content

Access tokens are short-lived JWTs. Refresh tokens rotate on use. Only the authenticated user's own plans are accessible.

What the connector does

• Read and list travel plans, schedules, checklists, notes, and chat messages
• Create new plans and append or update schedules
• Upload or generate cover and schedule images on Tabiori servers
• Delete plans or individual items when the user confirms

Changes are written directly to the user's Tabiori account and appear in the Tabiori mobile app and web client.

Data sent to Tabiori

Tool calls may include plan titles, dates, schedule text, spot keywords, image uploads, and identifiers needed to update the user's content. The MCP server does not request full chat transcripts. See our Privacy Policy for details on ChatGPT / MCP integration.

Rate limits

Requests are rate-limited per IP and per authenticated user. Heavy media tools have additional hourly limits. Clients receive HTTP 429 with Retry-After when limits are exceeded.

Support

Questions about this connector: info@tabiori.com

Last updated: 2026-06-08