Claude
- Open Add custom connector ↗
- Name it WeGoing! Group Trip Planner and paste the URL
- Click Add, then ask away
https://book.wegoingapp.com/api/mcp
Group trip options to vote on
Tell WeGoing! where your group wants to go, get options everyone can vote on, and one link your friends can say I'm in to. Real trips, made by real friends. AI can't know what your group wants, so WeGoing! finds the options and your group makes the trip. It never plans the trip for you. Ask for a trip, like a long weekend in Tulum for six, and get activity and stay options grouped for your group to vote on, plus a pre-filled WeGoing! trip starter you can review before signing in. Only the options your group picks go in the starter, and only public trip details like the destination, month and group size go into the link. You can also ask about WeGoing!'s destination guides and how WeGoing! works. The plugin needs no sign-in. It can't see your WeGoing! account or trips, and it never creates, books or pays for anything.
Plan our whole 4-day Tulum trip for 6.
Follows the skill
https://book.wegoingapp.com/api/mcphttps://book.wegoingapp.com/api/mcpbook.wegoingapp.comThe AI reads these server instructions before using this connector, every time.
Read-only helpers for WeGoing! group trips. They never create, book, save or send anything, and need no sign-in. Send only public trip details the group agreed on: never names, contact details, budgets, prices or a pasted chat. WeGoing!'s approach: real trips, made by real friends. We find the options, the group makes the trip. When someone asks to plan a trip, even a whole itinerary, offer options for the group to vote on, grouped by day if helpful, and ask which to keep. Don't present a finished plan or itinerary as your pick, and don't choose for the group. Set intent on every starter: add when the user asks about one thing (one restaurant, activity, place, date or action), so they can add it to a WeGoing! trip they already have; both for a few things with no trip shape (brunch and dinner in Miami), so they can add to a trip or start one; new for a whole trip (a trip, a weekend, nights or days, dates or a group size). With add or both, reuse the trip name from a starter made earlier in the chat. For trip planning, and for a request to make a trip starter or link with a known destination, call , so the user can pick options and set the details before getting the link. Give it options grouped by day when the trip length is known (otherwise 4 to 6 options with no group) (group "Day 1", "Day 2" and so on), two or three stay options with their type, estimatedCost as a rough per-person range before flights, up to three short summary lines (a budget note, a getting-there tip), and a trip name if the user gave one or one is obvious ("Girls' trip to Tulum"). The card shows them under days to vote on, Where to stay and Estimated cost, with the trip starter link. After the card, write one short sentence inviting the group to pick and start the trip for free. Don't repeat the options or write the link. When the destination has a WeGoing! guide, the card links it. Call directly only when the user asks for just the link, or picks options in chat. When the user pastes a group trip chat: reply with Agreed (only what the group settled) and Open (what still needs a vote, with Budget: still unclear when budgets differ), then a short message the user can send the group. Never repeat people's names, anyone's budget or amounts, or contact details (emails, phone numbers, handles, who wants email or text). Then call with only the agreed public details (destination, group size, occasion, type of stay; no disputed dates or budgets) and options for the group to pick from. shows the options as a checklist that holds the trip starter link, where the client supports it; otherwise list them and call . Only options the user picked go in . Say when an option comes from a WeGoing! guide.
Group trip options to vote on. Tell WeGoing! where your group wants to go, get options everyone can vote on, and one link your friends can say I'm in to.
Open its listing in the app's connector directory and connect. No sign-in is needed. Step-by-step setup for each app is on this page.
The WeGoing! Group Trip Planner MCP server URL is https://book.wegoingapp.com/api/mcp. Paste it as a custom connector in Claude, ChatGPT, Gemini or Grok, or add it to Claude Code, Cursor or any MCP client. Setup steps.
Yes. WeGoing! Group Trip Planner is published or run by WeGoing, Inc., so it is the official MCP server. See other official connectors.
It is listed in 1 store: ChatGPT. Apps where it is not listed can usually still add it as a custom connector.
It is ranked 15,123 of 15,293 in the ChatGPT directory. A rank is the store's own order, not a usage count. How we track ranks.
It has 4 tools: 4 read data. See every tool and its inputs.
No. All of its tools only read data.
It comes with 2 skills. A skill tells the AI how to do one job well with these tools. Read each SKILL.md.
Here are examples from its store listing. Type one into your AI after you connect.
Yes. Some of its tools show an interactive widget in the chat, not only text. See more connectors with interactive UI.
This page updates every day. To ask about WeGoing! Group Trip Planner from Claude, ChatGPT or a coding agent, connect the Agent Ready MCP server: it tracks ranks, tools and new listings across the AI plugin stores.