MCP reference

The Movmo MCP server exposes the same handlers as REST through the Model Context Protocol. Use it from any MCP-aware client (Claude Desktop, Cursor, ChatGPT connectors, custom agents).

Transport

• stdio — for local agent hosts. The movmo-mcp binary spawns per user; auth flows through OAuth PKCE against auth.e2e.movmo.io (pre-prod; prod alias is auth.movmo.io).
• Streamable HTTP at https://e2e.api.movmo.io/v1/mcp — for remote MCP clients. Stateless Bearer auth: the client sends an OAuth access token on every request; no server-side token storage.

Both transports support OAuth discovery (RFC 9728 /.well-known/oauth-protected-resource and RFC 8414 /.well-known/oauth-authorization-server) and Dynamic Client Registration (RFC 7591) for autonomous agents. Pre-registered partners use the same OAuth flow as REST — see Authentication.

Tool list

The deployed tools are documented inline in each domain page:

• Profile — get_user_profile, get_travel_preferences, get_locale_preferences
• Passengers — get_passengers_profile, create_passenger_profile, update_passenger_profile, delete_passenger_profile
• Payments — get_payment_methods, delete_payment_method
• Flights — search_flights, create_offer, get_offer_details, get_seat_map, update_passenger, create_booking, get_booking

The server also registers two semantic-discovery tools (list_semantic_resources and read_semantic_resource) used by agents to retrieve plain-text booking guides, provider notes, and error references at runtime. They will appear in any tools/list response.

A consolidated tool reference with full input schemas is on the roadmap. Today, an MCP client discovers schemas via the standard tools/list call against the running server.