hasAvailabilityInWindow — Nomad Stays MCP Tool
hasAvailabilityInWindow
(has availability in window) is one of 79 tools on the
Nomad Stays
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call hasAvailabilityInWindow from your client
- Claude Code Nomad Stays hasAvailabilityInWindow run in your project directory
- Claude Desktop Nomad Stays hasAvailabilityInWindow ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Nomad Stays hasAvailabilityInWindow ~/.cursor/mcp.json
- VS Code Nomad Stays hasAvailabilityInWindow .vscode/mcp.json
- Zed Nomad Stays hasAvailabilityInWindow ~/.config/zed/settings.json
- Windsurf Nomad Stays hasAvailabilityInWindow ~/.codeium/windsurf/mcp_config.json
- Cline Nomad Stays hasAvailabilityInWindow ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Nomad Stays hasAvailabilityInWindow ~/.gemini/settings.json
- Grok Nomad Stays hasAvailabilityInWindow .mcp.json (in your project root)
- ChatGPT Nomad Stays hasAvailabilityInWindow Settings → Connectors → Advanced → Developer mode
- Claude.ai Nomad Stays hasAvailabilityInWindow Settings → Connectors → Add custom connector
- LangChain Nomad Stays hasAvailabilityInWindow pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp-server https://mcp.nomadstays.com/mcp
Other tools on this server
- getStayByID
- signupNomadStaysAccount
- getStaysByCountry
- getStaysByContinent
- getStaysByLocation
- getMarketplaceAdverts
- getMarketplaceCategories
- searchHelpCenter
- getHelpCenterArticle
- listHelpCenterCategories
- getStaysByLifestyle
- getStaysByBudget
- getStaysByAmenities
- getStaysByWiFiSpeed
- getAllLifestyles
- getAllAmenities
- checkStayAvailability
- findNearestAvailability
- getAvailabilityByMonth
- getRoomAvailability
- getRoomAmenities
- getMyStays
- getMyStayDetail
- getMyStayOnboardingStatus
- getMyStayRooms
- getMyStayPackages
- getMyStayOrganisationalData
- getMyBusinessProfile
- updateStayDetail
- createStayRoom
- updateStayRoom
- deleteStayRoom
- getRoomTypeOptions
- getRoomFacilityOptions
- deleteRoomPhoto
- reorderRoomPhotos
- createStayPackage
- updateStayPackage
- deleteStayPackage
- getCurrencyOptions
- updateStayOrganisationalData
- updateHostBusinessProfile
- uploadStayPhoto
- getMyStayContacts
- updateStayContacts
- getMyStayFacilities
- updateStayFacilities
- getFacilityGroups
- getStayTypeOptions
- getCountryOptions
- getCancellationPolicyOptions
- getAdditionalInformationOptions
- getBusinessModelOptions
- getMyStayPhotos
- deleteStayPhoto
- reorderStayPhotos
- getProductInfo
- purchaseProduct
- getPurchaseStatus
- listStayApplications
- getStayApplication
- createStayApplication
- saveStayApplication
- submitStayApplication
- listExperienceApplications
- getExperienceApplication
- createExperienceApplication
- saveExperienceApplication
- submitExperienceApplication
- quoteStayBooking
- bookStay
- getBookingStatus
- listMyBookings
- listCoworkingApplications
- getCoworkingApplication
- createCoworkingApplication
- saveCoworkingApplication
- submitCoworkingApplication
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.