checkStayAvailability — Nomad Stays MCP Tool
checkStayAvailability
(check stay availability) 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 checkStayAvailability from your client
- Claude Code Nomad Stays checkStayAvailability run in your project directory
- Claude Desktop Nomad Stays checkStayAvailability ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Nomad Stays checkStayAvailability ~/.cursor/mcp.json
- VS Code Nomad Stays checkStayAvailability .vscode/mcp.json
- Zed Nomad Stays checkStayAvailability ~/.config/zed/settings.json
- Windsurf Nomad Stays checkStayAvailability ~/.codeium/windsurf/mcp_config.json
- Cline Nomad Stays checkStayAvailability ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Nomad Stays checkStayAvailability ~/.gemini/settings.json
- Grok Nomad Stays checkStayAvailability .mcp.json (in your project root)
- ChatGPT Nomad Stays checkStayAvailability Settings → Connectors → Advanced → Developer mode
- Claude.ai Nomad Stays checkStayAvailability Settings → Connectors → Add custom connector
- LangChain Nomad Stays checkStayAvailability pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp-server https://mcp.nomadstays.com/mcpOther tools on this server
- getStayByID
- signupNomadStaysAccount
- getStaysByCountry
- getStaysByContinent
- getStaysByLocation
- getMarketplaceAdverts
- getMarketplaceCategories
- searchHelpCenter
- getHelpCenterArticle
- listHelpCenterCategories
- getStaysByLifestyle
- getStaysByBudget
- getStaysByAmenities
- getStaysByWiFiSpeed
- getAllLifestyles
- getAllAmenities
- hasAvailabilityInWindow
- 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.