Wyndham Hotels and Resorts
Search Wyndham hotels by city and dates and pull room types, policies and rates into an AI agent. Two tools, both read-only. No booking tool, no Wyndham Rewards access, no sign-in.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Wyndham Hotels and Resorts via MCP
https://mcp.wyndhamhotels.com/claude/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Wyndham Hotels and Resorts Tools & Capabilities (2)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- No booking, no modification, no cancellation. The connector ends at discovery. Every reservation action happens on Wyndham's website or by phone, and Wyndham's llms.txt routes "I need to cancel my reservation" to its find-reservation page rather than to any tool.
- No Wyndham Rewards access of any kind — no balance, no tier, no stay history, no redemption. A consequence rather than a gap: the connector cannot quote the member rate that Wyndham says signed-in members always receive.
- We could not verify the authentication posture. Our anonymous request to the endpoint returned HTTP 403 with an Akamai "Access Denied" body and an
errors.edgesuite.netreference, carrying noWWW-Authenticateheader and no JSON-RPC error. A nonsense control path on the same host returned 503 instead, so the 403 is path-specific — but an edge block is not an authentication challenge, and we will not record one as the other. TheauthVerifiedflag on this page is therefore false. - No RFC 9728 metadata was reachable. All four well-known probes returned identical-shape 503 origin errors, including a nonsense control path, so the host published nothing we could read. No scopes are documented anywhere; with two read-only tools there is no boundary for a scope to fall between.
- We could not read tool schemas or safety annotations. No
tools/listresponse was obtained, so every parameter detail on this page comes from Wyndham's documentation rather than from the server. If the server's live schema differs, the server is right and this page is stale. - Search is city-scoped.
city,stateCodeandcountryCodeare all required. There is no coordinate, radius, landmark or address parameter, so "near the airport" is a judgement the agent makes from returned addresses rather than a query the server answers. Note that DirectBooker exposes coordinate and Google Place ID lookups that this connector does not. - Wyndham properties only. Search returns nothing outside Wyndham's roughly 8,300 hotels, so the connector cannot tell you whether a competitor is cheaper.
- Undated searches silently jump forward a month. Both tools default
checkinDateto 30 days out andcheckoutDateto one night later. Ask about "tonight" without stating the date and the prices returned may be for a different month. - No rate limits are published. Wyndham documents none for this server, and we could not observe any. Treat throughput as unknown rather than unlimited.
- The connector is documented for Claude only. Wyndham's page covers the Claude flow, and the endpoint path is
/claude. Anthropic lists Claude, the Claude API and Claude Code as supported clients; other MCP clients are untested rather than excluded.
Frequently asked questions
No. Both tools are read-only lookups, and neither Anthropic's directory nor Wyndham's own connector page names a tool that creates, modifies or cancels a reservation. Wyndham's documentation describes the connector as search and discovery, and routes booking to its website. An agent using this connector cannot commit you to a room or a rate.
No. Neither tool reads a member profile, a points balance or an elite tier, and none can redeem points. Wyndham's llms.txt routes every points question to pages on its website instead. Because redeeming points spends a real asset, the absence of any loyalty tool is the safety-relevant fact here.
Anthropic's directory records this server as authless, and Wyndham's setup instructions describe adding the connector with no credential step. We could not confirm that ourselves: the endpoint sits behind an Akamai edge filter that returned Access Denied to our anonymous request, so no handshake reached the server.
Room types, accessibility features, room amenities and hotel policies. Wyndham documents get-wyndham-hotel-details as returning complete hotel details for one or more property IDs, including policies. Its own sample prompts name check-in time and cancellation policy, so the connector reports a cancellation policy without being able to trigger one.
Because its search is city-scoped rather than free-text. Wyndham documents city, stateCode and countryCode as all required on search-wyndham-hotels, with an empty stateCode for international cities and a country default of US. There is no latitude and longitude parameter, so searching near a landmark means naming its city.
Yes, for the dates you supply. Wyndham states that search returns price and available amenities for the searched dates, and that omitting dates defaults to a 30-day-out one-night stay. A quoted rate is a quote, not a hold — nothing in this connector reserves inventory, so availability can change before you book.
Wyndham's llms.txt states the company operates more than 8,300 hotels across 25 brands in over 95 countries, spanning Days Inn, Super 8, La Quinta, Ramada and Wyndham Grand. The connector searches Wyndham properties only, so it cannot compare a Wyndham rate against a competitor's.
The endpoint is streamable HTTP, so any MCP client can address it, and Anthropic lists the connector as working with Claude, the Claude API and Claude Code. Wyndham's documentation covers only the Claude connector flow, and its path segment is literally /claude, so non-Claude use is undocumented rather than blocked.
Sources
- Wyndham Claude AI connector documentation (retrieved 2026-08-22). Carries the tool table, parameters, return descriptions, setup steps and sample prompts used throughout this page. Wyndham's
robots.txtpermits this path. · retrieved 2026-08-22 - Wyndham
llms.txt(retrieved 2026-08-22). Source for the 8,300-hotel and 25-brand figures, the Wyndham Rewards redemption rates, and the "Guidance for AI Systems" section reported above. Dated March 2026 by its own footer. · retrieved 2026-08-22 - Wyndham
robots.txt(retrieved 2026-08-22). Last updated November 2025; noContent-Signaldirective present. · retrieved 2026-08-22 - Live endpoint probe — anonymous
initializetohttps://mcp.wyndhamhotels.com/claude/mcpreturned HTTP 403 with an Akamai Access Denied body; a nonsense control path on the same host returned 503; four RFC 9728 well-known probes all returned 503 (2026-08-22) · retrieved 2026-08-22 - Wyndham Rewards program hub (referenced 2026-08-22) · retrieved 2026-08-22
- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- DirectBooker and Ticketmaster directory entries, for the comparison above — · , same snapshot
- Wyndham support — · Privacy notice
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Wyndham Hotels and Resorts
- Tools
- 2
- Domain
- mcp.wyndhamhotels.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.