Everway MCP Server README
The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Everway MCP Server listing page.
Everway MCP Server
The official Model Context Protocol (MCP) server for Everway — connect Cursor, Claude, ChatGPT, or any MCP client to your real trips and itineraries.
Everway turns forwarded confirmation emails into one day-by-day itinerary. This MCP server is a hosted bridge between your Everway account and MCP-compatible AI tools: once connected, your assistant can read your itinerary, answer questions about your plans, and add or update bookings — all with your permissions, and without ever touching your inbox.
Server URL
One-click setup
 |  |
|---|---|
| Ask about your trips and add bookings from Cursor. | Read and update itineraries via GitHub Copilot. |
For any other client, add a remote MCP server with the URL above. A browser sign-in handles the rest — no API keys to generate, copy, or rotate.
Supported clients
Everway works with any client that supports remote MCP servers over streamable HTTP with OAuth, including:
| Client | Setup reference |
|---|---|
| Cursor | Cursor MCP docs |
| Claude (Claude.ai, Desktop, and Code) | Claude MCP docs |
| OpenAI ChatGPT | Connectors / MCP guide |
| Visual Studio Code (GitHub Copilot) | VS Code MCP docs |
| Google Gemini CLI | Gemini CLI MCP docs |
Manual configuration
This repository also ships a .mcp.json for Claude Code and a server.json manifest for the MCP Registry.
Plugins and extensions
Beyond the raw server URL, this repo packages Everway as a plugin for clients that support them — each bundles the MCP connection together with the skills:
Claude Code
Cursor
The .cursor-plugin manifest packages the MCP server and skills as a Cursor plugin. You can also just add the server URL directly — see one-click setup.
Gemini CLI
Skills
The skills/ directory contains agent skills for the travel tasks people actually repeat. Clients that support skills (Claude Code, Cursor) pick them up automatically via the plugin manifests.
| Skill | What it does |
|---|---|
add-bookings-from-text | Turn pasted confirmations or trip notes into structured itinerary items. |
trip-gap-audit | Find what's missing: empty days, uncovered nights, missing transfers, no return flight. |
daily-briefing | Answer "where am I, what do I do next?" with times, addresses, and confirmation numbers. |
trip-budget-report | Roll up trip costs by category, day, or traveler — honest about what isn't priced yet. |
share-trip | Add travelers, send view-only invites, and manage which bookings are shared or private. |
What you can do
Ask about your trips:
- "What's left to book on my Tokyo trip?"
- "What time is my ferry on Saturday, and where does it leave from?"
- "Which days have nothing planned yet?"
- "What's the total cost of my trip so far?"
Or tell it what to do:
- "Add my rental car pickup at 9am Friday to the Lisbon trip."
- "Move my hotel checkout to the 12th."
- "Create a trip called Amalfi for June 10–17."
- "Invite sam@example.com to view this trip."
Changes made by your assistant show up instantly in the Everway app, on your maps, and for anyone you've shared the trip with.
Supported tools
| Tool | What it does |
|---|---|
get_account | The signed-in account: email, plan, and whether it can create another trip. |
list_trips | All trips the user owns or was invited to view. |
get_trip | A single trip with the user's role on it. |
create_trip | Create a trip with a name and dates. |
update_trip | Update a trip's name or dates. |
update_trip_alias | Change the trip's @everway.ai forwarding address. |
list_itinerary_items | Every itinerary item on a trip the user can see. |
add_itinerary_item | Add a flight, lodging, restaurant, or activity; addresses are geocoded automatically. |
update_itinerary_item | Update an existing itinerary item. |
delete_itinerary_item | Delete an itinerary item. |
set_item_visibility | Share an item with the trip or make it private again. |
set_item_people | Attach trip people to an item (passengers, guests, diners). |
list_trip_people | Everyone on a trip: owner, guests, and travelers found in bookings. |
add_trip_person | Add a traveler to the trip's people list. |
rename_trip_person | Rename a traveler who has no Everway account. |
remove_trip_person | Remove a traveler from the trip and its items. |
list_invites | View-only invites on a trip and their status. |
invite_viewer | Email someone a view-only invite to the trip. |
revoke_invite | Revoke a view-only invite. |
Write tools respect the same rules as the app: owner-only actions stay owner-only, and free-plan limits apply (a second trip on the free plan prompts an upgrade instead of failing silently).
Authentication
The server uses OAuth 2.1 with dynamic client registration. The first time your client connects, it opens Everway in the browser; you sign in with the one-time code we email you and approve access. No passwords, no API keys.
The connection is scoped to your account. To disconnect, remove Everway from your client's MCP settings — the access token stops working on the next request.
Data and security
- Your assistant acts as you, with your exact permissions: it can view and edit trips you own, and view trips shared with you. It can't reach anyone else's trips or another traveler's private bookings.
- No inbox access. Everway never connects to your mailbox, and neither does your assistant. It only sees the trips and itinerary items already in your Everway account.
- All traffic is encrypted in transit over HTTPS.
- Invite tokens and other single-use secrets are never exposed to agents.
MCP clients can perform actions in Everway with your existing permissions. Only connect clients you trust, and review high-impact changes before confirming. See SECURITY.md for how to report a vulnerability.
Requirements
- An Everway account — the MCP connection is included on every plan, free and Pro.
- An MCP-compatible client that supports remote servers.
- A browser to complete the OAuth sign-in.
What's in this repo
The server runs as a hosted service at everway.ai/api/mcp and isn't part of this repo. What lives here are the public-facing pieces:
README.md— this documentationserver.json— the MCP Registry entry.mcp.json,.claude-plugin/,.cursor-plugin/,gemini-extension.json— client manifestsskills/— agent skills for common travel tasksscripts/validate-template.mjs— validates the manifests and skills (node scripts/validate-template.mjs)
Support and feedback
- Product documentation: everway.ai/mcp
- Problems with the hosted server, sign-in, or your account: support@everway.ai
- Problems or ideas for this repo's docs, manifests, or skills: open an issue
- Want to contribute? See CONTRIBUTING.md and the Code of Conduct.
License
This repository (documentation, configuration manifests, and skills) is licensed under the MIT License. The Everway service itself is proprietary — see the terms of service.