getStaysByWiFiSpeed — Nomad Stays MCP Tool
getStaysByWiFiSpeed
(get stays by wi fi speed) 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 getStaysByWiFiSpeed from your client
- Claude Code Nomad Stays getStaysByWiFiSpeed run in your project directory
- Claude Desktop Nomad Stays getStaysByWiFiSpeed ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Nomad Stays getStaysByWiFiSpeed ~/.cursor/mcp.json
- VS Code Nomad Stays getStaysByWiFiSpeed .vscode/mcp.json
- Zed Nomad Stays getStaysByWiFiSpeed ~/.config/zed/settings.json
- Windsurf Nomad Stays getStaysByWiFiSpeed ~/.codeium/windsurf/mcp_config.json
- Cline Nomad Stays getStaysByWiFiSpeed ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Nomad Stays getStaysByWiFiSpeed ~/.gemini/settings.json
- Grok Nomad Stays getStaysByWiFiSpeed .mcp.json (in your project root)
- ChatGPT Nomad Stays getStaysByWiFiSpeed Settings → Connectors → Advanced → Developer mode
- Claude.ai Nomad Stays getStaysByWiFiSpeed Settings → Connectors → Add custom connector
- LangChain Nomad Stays getStaysByWiFiSpeed 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
- getAllLifestyles
- getAllAmenities
- checkStayAvailability
- 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.