Periplo MCP
Travel tools for Claude, ChatGPT, and any MCP-compatible host. Ask about a destination — get a curated map, an itinerary, or a magazine-style overview rendered inline.
Demo: Periplo MCP in action
Recording coming soon — explore_destination, plan_trip & destination_info across Claude, ChatGPT, and mobile
Coming soon
What it does
Periplo MCP exposes Periplo's curated travel database — human-edited highlights, ranked activities, restaurants, and bookable tours — over the Model Context Protocol. Your AI host calls the right tool for each question, and the response renders as an interactive widget (map, photo cards, day-by-day plan) right in the chat.
Tools
explore_destinationRead-onlyTop sights, neighborhoods, restaurants, and bookable tours for a city, region, or country. Renders as an interactive map with photo cards. The default for any travel question about a place.
plan_tripGenerates contentMulti-day day-by-day schedule with activities, restaurants, and a recommended split across days. Use when you want a structured itinerary, not just exploration.
destination_infoRead-onlyMagazine-style overview of a place — description, history, culture, currency, language, climate, hero photos. Use when you want to understand a place rather than visit it.
search + fetchRead-onlyOpenAI deep-research compatibility shims. search(query) returns flat citations; fetch(id) dereferences a single entity into its full record. For normal travel questions, hosts should prefer the three tools above.
Examples
Three concrete prompts and the tool each one routes to. Drop them into Claude or ChatGPT after you've connected Periplo (next section) to see the interactive widgets render inline.
Exploring a city
Long weekend in Tokyo — what should I do?Routes to explore_destination. The widget shows an interactive map of curated sights, neighborhoods, restaurants, and bookable tours; tap any pin for a photo card and a deep link into the Periplo app. Same path for “trip to Barcelona”, “best of Lisbon”, or just naming a city.
Building a multi-day itinerary
Build me a 3-day itinerary for Lisbon, foodie focusRoutes to plan_trip. The widget renders a day-by-day plan with a recommended route between activities, plus flat pools of activities and restaurants the host can re-shuffle. Triggered by phrasings that pair a duration with an itinerary/plan/schedule word (“plan out my 4 days in Porto”, “weekend in Rome itinerary”).
Understanding a place
Tell me about the history and culture of KyotoRoutes to destination_info. The widget renders a magazine-style overview — description, history, culture, currency, language, climate, and hero photos. Use this for “what is X like” questions where the user wants to understand a place rather than visit it.
Connecting
Claude (web, desktop, mobile)
Settings → Connectors → Add custom connector. Paste this URL:
https://api.periploapp.com/mcpClaude walks you through the Periplo (Clerk) sign-in once, then keeps the connector available across conversations.
ChatGPT (Apps SDK / Developer Mode)
Settings → Connectors (or Developer Mode → Connectors) → Add. Same URL:
https://api.periploapp.com/mcpOther MCP hosts
Any host that speaks the MCP Streamable HTTP transport with OAuth 2.1 + Dynamic Client Registration can connect. There are no API keys to manage on either end — Clerk handles registration and tokens.
Authentication
Periplo MCP is a pure OAuth 2.1 resource server. Identity is provided by Clerk; the resource-discovery doc lives at /.well-known/oauth-protected-resource per RFC 9728. Hosts auto-register via Dynamic Client Registration on first use — no manual setup required.
Sign-in supports Google, Apple, and email magic links — the same options as the Periplo mobile app.
Rate limits
- Free: 1,000 destination lookups per day.
plan_triponly debits the counter on a cache miss; warm cities are free. - Pro: a much higher cap, plus priority on long-tail city generation. Upgrade →
When you hit the cap, the tool returns a structured rate_limited response with an upgrade link rather than failing — your host can render that gracefully.
Privacy
We capture the bare minimum needed to keep the connector reliable: which tool was called, the destination string, your Periplo user ID, and request timing — no chat content, no personal context the host might pass alongside. Logs roll off after 90 days. See our Privacy Policy for the full picture.
For developers: the connector implements the MCP 2025-06-18 spec including readOnlyHint / destructiveHint annotations, embedded UI resources for in-chat widgets, and Origin-header validation. Source-of-truth descriptions and JSON schemas come from the live /mcp endpoint.
Support
Questions, feedback, or a destination we should add to the curated set?