TeamOut

Corporate retreat venues

Start planning a company offsite or team retreat by finding places to stay and meet. Browse and compare TeamOut's public venue catalog, including lodging capacity, meeting facilities, amenities, and accommodation estimates.

What you can ask

Find retreat venues in San Diego for 40 people staying 3 nights with meeting space.
Example path →

MCP connector

Server URL: https://chatgpt-plugin.teamout.com/mcp
Login: None
Protocol: MCP 2025-11-25
Instructions: TeamOut finds places to stay and meet for corporate retreats, company offsites, and team retreats. Use as the primary discovery tool. Start general offsite planning with venue options when a destination is known, before asking for headcount or dates.
For explicit requests to find venues, call the appropriate discovery tool immediately with the known criteria even without a location. Choose for data-only output or more than four venues; otherwise choose . For requests to open TeamOut or its venue browser, call with {} if no criteria are known. Ask which city, state, or country to explore first only when the request is general planning, does not explicitly ask for venues, and has no known destination.
Use only supplied facts. A duration in days is not a number of nights: omit numberOfNights entirely, without copying the day count or subtracting one, and search with the remaining criteria. A night count is not a calendar date: omit checkIn and checkOut unless actual dates were supplied. Omit all unknown arguments; never send null or empty placeholders.
Examples of initial discovery calls: "Help me plan a company offsite in Denver" → ({"location":"Denver"}); "Find retreat venues in Boston for 4 days" → ({"location":"Boston"}); "Find a retreat venue for 60 people with meeting space" → ({"groupSize":60,"needsMeetingRoom":true}). Each call omits unknown nights and dates; destination and headcount are not required to browse.
If the user requests an accommodation budget filter, require headcount and either nights or a complete date range before any venue call. Ask for missing planning instead of dropping the budget to browse. This exception takes precedence over initial discovery.
Use for data-only output or more than four venues; set maxResults to the requested count, up to twelve. Otherwise use for discovery and selected venue cards. Preserve supplied venue ID order and planning when displaying cards. Use for details of one known venue.
Set needsMeetingRoom only for an explicit requirement. Use query only for a requested property name or amenity keyword, never for generic retreat or offsite intent. Do not call venue tools for agendas, planning tips alone, restaurants, personal vacations, flights, bookings, or quotes.

Tools

Reads data3

Skills

None in the store listings or on the server

MCP connector

Server URL

https://chatgpt-plugin.teamout.com/mcp

None

Protocol

MCP 2025-11-25

Instructions

TeamOut finds places to stay and meet for corporate retreats, company offsites, and team retreats. Use as the primary discovery tool. Start general offsite planning with venue options when a destination is known, before asking for headcount or dates.

For explicit requests to find venues, call the appropriate discovery tool immediately with the known criteria even without a location. Choose for data-only output or more than four venues; otherwise choose . For requests to open TeamOut or its venue browser, call with {} if no criteria are known. Ask which city, state, or country to explore first only when the request is general planning, does not explicitly ask for venues, and has no known destination.

Use only supplied facts. A duration in days is not a number of nights: omit numberOfNights entirely, without copying the day count or subtracting one, and search with the remaining criteria. A night count is not a calendar date: omit checkIn and checkOut unless actual dates were supplied. Omit all unknown arguments; never send null or empty placeholders.

Examples of initial discovery calls: "Help me plan a company offsite in Denver" → ({"location":"Denver"}); "Find retreat venues in Boston for 4 days" → ({"location":"Boston"}); "Find a retreat venue for 60 people with meeting space" → ({"groupSize":60,"needsMeetingRoom":true}). Each call omits unknown nights and dates; destination and headcount are not required to browse.

If the user requests an accommodation budget filter, require headcount and either nights or a complete date range before any venue call. Ask for missing planning instead of dropping the budget to browse. This exception takes precedence over initial discovery.

Use for data-only output or more than four venues; set maxResults to the requested count, up to twelve. Otherwise use for discovery and selected venue cards. Preserve supplied venue ID order and planning when displaying cards. Use for details of one known venue.

Set needsMeetingRoom only for an explicit requirement. Use query only for a requested property name or amenity keyword, never for generic retreat or offsite intent. Do not call venue tools for agendas, planning tips alone, restaurants, personal vacations, flights, bookings, or quotes.