MCP Server

Connect Claude, ChatGPT, and compatible AI assistants to your Globe.cv account to manage places, trips, and itinerary segments.

#Endpoint

https://api.globe.cv/mcp

Globe.cv uses the standard MCP Streamable HTTP transport. https://www.globe.cv/mcp redirects here for documentation; use the API hostname in client configuration.

#Sign in

Use OAuth when your client supports it. The client opens Globe.cv, where you sign in and approve the requested permissions once. You can review and revoke connected apps in Settings > API.

For CLIs and headless clients, use the OAuth device flow: your client shows a code, then you enter that code at https://www.globe.cv/oauth/device.

Existing API keys also work as Authorization: Bearer gcv_.... Treat a key like a password: it has read and write access to your Globe.cv account.

#Permissions

• places:read and places:write
• trips:read and trips:write

#Tools

#Places

list_places, get_place, create_place, update_place, and delete_place. Creating a place by name uses the same enrichment and subscription limits as the Globe.cv app. To skip enrichment, send a resolved place with a category and valid coordinates, or set enrichment: "skip" to require direct creation. Resolved places can also include identifier, tags, and confidence_level.

#Trips

list_trips, get_trip, create_trip, update_trip, and delete_trip.

#Itinerary segments

create_trip_segment, update_trip_segment, and delete_trip_segment. Use immutable IDs returned from list/get calls. Segment place_ids must belong to your account.

#Safety and limits

Delete tools permanently change your live account and require an explicit ID. MCP follows your existing free or premium API rate limits and place limits; it does not bypass them.

#Troubleshooting

401 means your login, key, or token is missing or expired. 403 means the connected app lacks a scope. 429 means you have reached the rate limit. Reconnect or generate a new API key from Settings if you revoke access.

For the REST API, see API documentation.