MCP Servers

Wink’s MCP tools are published as toolsets — focused endpoints, each covering one job. You connect your AI client to the one or two that match your work, not to all of them.

Every endpoint uses interactive OAuth2 login (PKCE authorization code flow): your AI agent opens a browser tab, you sign in with your Wink account, and that is it. No client secrets to manage.

A channel manager integrator connects to one endpoint

claude mcp add wink-channel-manager https://integrations.wink.travel/mcp/channel-manager --transport http

A hotelier managing their own rates connects to another

claude mcp add wink-rates https://api.wink.travel/mcp/extranet/rates --transport http

---

Why the tools are split across endpoints

Wink exposes around 500 tools. Handing all of them to an agent at once is technically possible — and a bad idea.

Tool definitions cost context. Every tool an MCP server advertises is loaded into the model’s context window before it does any work, along with its description and full parameter schema. Five hundred of those consume a large share of the budget your actual task needs, on every single request.

Choice quality falls as the list grows. An agent picking from 500 similarly-named tools makes worse choices than one picking from 40. If you integrate a channel manager, roughly twenty tools are relevant to you; the other 480 are noise that makes the right tool harder to find.

The work is genuinely separable. Someone syncing availability from a PMS and someone curating affiliate landing pages share almost no tools. Splitting by job means each connection carries the vocabulary of one job.

Toolsets are not permissions

Choosing a narrow toolset does not restrict what your account can do, and choosing a broad one does not grant anything extra. Every tool enforces the same account permissions as the web portal, under your signed-in identity. If your account cannot cancel a booking in Wink Portal, the agent cannot either — regardless of which endpoint it is connected to.

Pick toolsets for focus, not for security.

---

Endpoint directory

Two hosts serve toolsets. Tool counts are approximate and grow over time.

https://api.wink.travel — the platform

Endpoint	Tools	What it covers
/mcp/extranet/facilities	~64	The bookable and on-site inventory: guest rooms and room types, spas, restaurants, meeting rooms, activities, attractions, places, other sellable items
/mcp/extranet/property	~62	The property record and its commercial terms: profile and content, add-ons, cancellation policies, perks, announcements
/mcp/settings	~60	Account administration: managing-entity profile and branding, managers and their grants, customization, webhooks, notification preferences
/mcp/studio/embeds	~48	Publishing curated inventory: widgets, grids and ranked grids, cards, maps, deep links to inventory and supplier pages
/mcp/extranet/rates	~44	Prices and availability: inventory rate periods and allotments, rate plans, master rates, special and promotional rates
/mcp/extranet/operations	~39	Running a live property: reservations and their lifecycle, guest reviews and responses, calendar feeds, scheduled tasks
/mcp/extranet/distribution	~37	Where inventory is sold: sales channels and rate modifiers, affiliate and supplier relationship requests, registration, lead capture
/mcp/studio/curation	~35	Building merchandisable collections: static and dynamic lists, ranked lists, saved searches, property aggregates
/mcp/link-manager	~28	Syndicated link collections, their design, categories and tags, plus shortened URLs
/mcp/reference	~24	Read-only lookup data: countries, currencies and exchange rates, languages, timezones, geo lookups, IP geolocation
/mcp/analytics	~18	Booking and revenue analytics: overviews, line charts, leaderboards, affiliate performance, share metrics
/mcp/payment	~18	Financial operations: the ledger, withdrawals and fee estimates, booking funds aggregates
/mcp/booking-engine	~17	The traveller-facing shopping path: search and lookup, shopping cart and checkout, bucket lists, campaign customization
/mcp/social	~17	Connected social accounts, publishing and scheduling posts, reading post insights
/mcp/travel-agent	~8	Agent-facilitated bookings on behalf of travellers, and agent reports

https://integrations.wink.travel — channel manager integrations

One endpoint, because this host exists for one job.

Endpoint	Tools	What it covers
/mcp/channel-manager	~9	Connecting and verifying a channel manager, PMS or CRS integration

Integrating a channel manager vs. managing your own rates

These are different jobs for different people, and they do not share an endpoint.

A channel manager, PMS or CRS vendor integrates once through integrations.wink.travel/mcp/channel-manager, and from then on exchanges properties, rates, availability and reservations over that integration. That single endpoint is the whole surface.

A hotelier changing their own rates by hand uses the extranet toolsets on api.wink.travel — /mcp/extranet/rates and friends. Those are not part of a channel manager integration and an integrator has no reason to connect to them.

Account administration is also on api.wink.travel, at /mcp/settings. There is no /mcp/settings on the integrations host.

Every endpoint also carries a ping tool, so you can confirm a connection is live before asking it to do real work.

---

Which toolsets do I need?

If you are…	Connect to
Integrating a channel manager, PMS or CRS	integrations.wink.travel/mcp/channel-manager — just this one
Managing a property’s content	/mcp/extranet/property + /mcp/extranet/facilities
Managing rooms and room types	/mcp/extranet/facilities
Managing prices and availability	/mcp/extranet/rates
Running day-to-day reservations	/mcp/extranet/operations
Growing distribution	/mcp/extranet/distribution + /mcp/analytics
Building affiliate pages	/mcp/studio/curation + /mcp/studio/embeds
Running link-in-bio pages	/mcp/link-manager + /mcp/social
Booking on behalf of travellers	/mcp/travel-agent
Reconciling money	/mcp/payment
Building a booking experience	/mcp/booking-engine + /mcp/reference

Start with one. Add another when you find yourself asking for something it cannot do — each connection is independent, and adding one never affects the others.

Still want everything?

https://api.wink.travel/mcp and https://integrations.wink.travel/mcp remain available and serve every tool on their host. They are useful for exploring what exists, but we do not recommend them for day-to-day work: the tool list is large enough to crowd out your task and degrade the agent’s tool selection. Prefer the toolsets above.

---

How authentication works

Wink MCP servers use the OAuth2 Authorization Code + PKCE flow and support Dynamic Client Registration (RFC 7591). Here is what happens when you connect for the first time:

1. Your AI client discovers the authorization server from the MCP endpoint’s /.well-known/oauth-protected-resource metadata.
2. The client self-registers via Dynamic Client Registration — no manual application setup required.
3. The client opens a browser tab to https://iam.wink.travel. You sign in with your Wink account and approve the requested permissions on the consent screen.
4. Wink issues an access token scoped to your account and linked to your identity.
5. The AI client attaches the token to every MCP request. All tool results are automatically scoped to your managing entity.
6. Tokens expire after 3 hours. Your AI client refreshes silently in the background without prompting again.

Every tool call runs under your identity — the same ACL rules that protect the web portal apply to the AI agent.

---

Connect your AI client

Claude Code

1. Make sure Claude Code is up to date:

   npm install -g @anthropic-ai/claude-code

2. Pick a toolset from the directory above and add it. For example, prices and availability:

   claude mcp add wink-rates https://api.wink.travel/mcp/extranet/rates --transport http

3. Claude Code contacts the server, discovers the authorization server, and opens your default browser.

4. Sign in to Wink and approve the permission request on the consent screen.

5. Claude Code confirms the connection. Type /mcp to verify the server appears and its tools have loaded.

Add as many toolsets as your work needs — each is a separate server entry with its own name:

claude mcp add wink-operations https://api.wink.travel/mcp/extranet/operations --transport http
claude mcp add wink-analytics  https://api.wink.travel/mcp/analytics           --transport http

You only sign in once. After the first browser approval, Claude Code reuses your Wink session for additional Wink endpoints.

Share with your team

Add --scope project to claude mcp add and Claude Code writes the server URL to .mcp.json at the repo root. Commit that file — every team member gets the same toolsets, and each completes their own browser sign-in the first time they connect.

Claude Desktop

1. Edit the Claude Desktop config file:

   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json
   • Linux: ~/.config/Claude/claude_desktop_config.json

2. Add the MCP server entries:

   claude_desktop_config.json

   {
     "mcpServers": {
       "wink-extranet-rates": {
         "type": "http",
         "url": "https://api.wink.travel/mcp/extranet/rates"
       },
       "wink-extranet-operations": {
         "type": "http",
         "url": "https://api.wink.travel/mcp/extranet/operations"
       }
     }
   }

3. Fully quit and restart Claude Desktop (use Quit from the menu bar — closing the window is not enough).

4. Claude Desktop opens a browser tab for each new server. Sign in to Wink and approve permissions.

5. The plug icon in the bottom toolbar shows both servers as connected.

OpenAI Codex

1. Make sure Codex CLI is installed:

   npm install -g @openai/codex

2. Open (or create) the Codex config file:

   • macOS / Linux: ~/.codex/config.json
   • Windows: %USERPROFILE%\.codex\config.json

3. Add the Wink MCP server entries:

   ~/.codex/config.json

   {
     "mcpServers": {
       "wink-extranet-rates": {
         "type": "http",
         "url": "https://api.wink.travel/mcp/extranet/rates"
       },
       "wink-extranet-operations": {
         "type": "http",
         "url": "https://api.wink.travel/mcp/extranet/operations"
       }
     }
   }

4. Start Codex. On first use, Codex opens a browser tab to https://iam.wink.travel.

5. Sign in to Wink and approve the requested permissions.

6. Codex confirms the connection. Run codex and ask it to list available tools to verify the Wink servers are active.

Note

Codex CLI MCP support requires version 1.0 or later. Run codex --version to check, and npm install -g @openai/codex to upgrade.

ChatGPT

MCP server support is available in the ChatGPT desktop app for Plus, Pro, Team, and Enterprise subscribers.

1. Download and install the ChatGPT desktop app if you haven’t already.

2. Open the app and click your profile icon in the top-right corner, then choose Settings.

3. Go to Connectors (or MCP Servers depending on your app version) and click Add.

4. Enter the URL of a toolset from the directory above, for example:

   https://api.wink.travel/mcp/extranet/rates

   Then click Connect.

5. ChatGPT opens a browser tab to https://iam.wink.travel. Sign in to Wink and approve permissions.

6. Repeat steps 4–5 for any other toolset your work needs, for example:

   https://api.wink.travel/mcp/extranet/operations

7. Each toolset appears in your Connectors list. Start a new chat — Wink tools are available automatically.

Web app limitation

MCP servers are only configurable in the desktop app. The ChatGPT web interface at chatgpt.com does not support custom MCP servers.

Cursor

1. Open (or create) the Cursor MCP config file:

   • macOS / Linux: ~/.cursor/mcp.json
   • Windows: %USERPROFILE%\.cursor\mcp.json

2. Add the Wink MCP server entries:

   ~/.cursor/mcp.json

   {
     "mcpServers": {
       "wink-extranet-rates": {
         "type": "http",
         "url": "https://api.wink.travel/mcp/extranet/rates"
       },
       "wink-extranet-operations": {
         "type": "http",
         "url": "https://api.wink.travel/mcp/extranet/operations"
       }
     }
   }

3. Open Cursor. Go to Settings → Cursor Settings → MCP and confirm both servers appear with a green status indicator. If they show red, click Refresh.

4. Cursor opens a browser tab to https://iam.wink.travel. Sign in to Wink and approve permissions.

5. Open a chat (Ctrl+L / Cmd+L) and ask Cursor to list available Wink tools to confirm the connection.

Project-scoped config

You can also place an mcp.json file at the root of your project instead of in ~/.cursor/. Project-level config takes precedence and makes the servers available to every team member who opens the project in Cursor.

Windsurf

1. Open (or create) the Windsurf MCP config file:

   • macOS / Linux: ~/.codeium/windsurf/mcp_config.json
   • Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json

2. Add the Wink MCP server entries:

   ~/.codeium/windsurf/mcp_config.json

   {
     "mcpServers": {
       "wink-extranet-rates": {
         "type": "http",
         "url": "https://api.wink.travel/mcp/extranet/rates"
       },
       "wink-extranet-operations": {
         "type": "http",
         "url": "https://api.wink.travel/mcp/extranet/operations"
       }
     }
   }

3. Fully restart Windsurf (File → Quit, then reopen).

4. Go to Settings → MCP Servers and verify both servers show as connected. Windsurf opens a browser tab to https://iam.wink.travel on first use.

5. Sign in to Wink and approve permissions. The servers turn green in the settings panel once authenticated.

Note

Windsurf MCP support requires version 1.4 or later. Check via Help → About Windsurf and update from the Windsurf website if needed.

Cline (VS Code)

Cline is a VS Code extension with a built-in MCP server manager. No manual JSON editing is required.

1. Install Cline from the VS Code Marketplace:

   • Open VS Code and press Ctrl+Shift+X / Cmd+Shift+X
   • Search for Cline and click Install

2. Click the Cline icon in the Activity Bar (left sidebar) to open the Cline panel.

3. Click the MCP Servers icon (plug icon) in the Cline toolbar, then choose Edit MCP Settings.

4. VS Code opens cline_mcp_settings.json. Add the Wink entries:

   cline_mcp_settings.json

   {
     "mcpServers": {
       "wink-extranet-rates": {
         "type": "http",
         "url": "https://api.wink.travel/mcp/extranet/rates"
       },
       "wink-extranet-operations": {
         "type": "http",
         "url": "https://api.wink.travel/mcp/extranet/operations"
       }
     }
   }

5. Save the file. Cline reloads automatically and opens a browser tab to https://iam.wink.travel.

6. Sign in to Wink and approve permissions. Both servers appear as active in the MCP Servers panel.

Alternative: add via URL

In the MCP Servers panel, click Add Server and paste a toolset URL such as https://api.wink.travel/mcp/extranet/rates directly. Cline auto-populates the config and handles authentication without editing JSON manually.

---

Scopes

When you approve the consent screen you will see a breakdown of what the agent is requesting. MCP clients use the same permission vocabulary as the rest of the platform — see the full scope reference on the Authentication page.

Two things are specific to MCP:

• The mcp.read mcp.write mcp.remove scopes are additionally required to open the MCP transport. A client that holds an mcp.* scope is admitted to any Wink MCP endpoint, but every tool it invokes still enforces the section scope of the endpoint it wraps (e.g. booking.read).
• The AI client requests only the scopes it needs. You can deny individual permissions on the consent screen — tools that require a denied scope will return an error when invoked.

Toolsets do not change any of this. The endpoint you connect to decides which tools are listed, not what they are allowed to do. Connecting to /mcp/payment grants no financial permission you did not already have, and connecting to /mcp/reference does not stop a tool there from enforcing its own scope. Authorization is decided per tool call, from your token and your account’s grants.

---

Troubleshooting

Browser tab doesn’t open

Your AI client may not support the interactive PKCE flow yet. Verify you are running a recent version:

• Claude Code: npm install -g @anthropic-ai/claude-code
• Codex CLI: npm install -g @openai/codex
• Claude Desktop / ChatGPT desktop: update from the app’s built-in updater

401 Unauthorized after signing in

Your cached token may be stale. Remove and re-add the server to trigger a fresh sign-in:

# Claude Code
claude mcp remove wink-rates
claude mcp add wink-rates https://api.wink.travel/mcp/extranet/rates --transport http

For Claude Desktop and ChatGPT, remove the server entry from settings, restart the app, and add it again.

403 Forbidden when calling a specific tool

The tool requires a scope you did not approve on the consent screen, or a permission your account does not hold. Reconnect the server — the consent screen will appear again and you can approve the missing permission. If it still fails, the tool needs an account permission you do not have; connecting to a different toolset will not help, because toolsets do not grant permissions.

The tool I need isn’t in the list

You are probably connected to a toolset that does not cover that job. Check the endpoint directory and add the toolset that does — connections are independent, so adding one changes nothing about the others. If you are unsure which one has it, connect to https://api.wink.travel/mcp temporarily, find the tool, then look up which toolset lists it.

404 Not Found on a toolset endpoint

Check the path carefully — the nested toolsets have two segments (/mcp/extranet/rates, not /mcp/extranet-rates), and the flat ones have one (/mcp/link-manager). Note that an unauthenticated request to any path under /mcp returns 401, not 404, so a 401 alone does not tell you whether the endpoint exists.

I connected to api.wink.travel/mcp/channel-manager and got nothing

That endpoint does not exist. Channel manager integration is served from https://integrations.wink.travel/mcp/channel-manager only. If you also need to read or write a property’s own rates by hand, that is a separate job on a separate endpoint — see /mcp/extranet/rates.

The server appears but tool calls return “account not found”

You are signed in to a Wink account that has no managing entity. Go to Wink Portal and ensure your account is set up before using the MCP server.

Token expires mid-session

Tokens are valid for 3 hours. Claude Code and Claude Desktop refresh tokens silently without interrupting your session. If you see auth errors after a long idle period, type a new message — the client will re-authenticate automatically.

Codex CLI shows “MCP server unreachable”

Check that your ~/.codex/config.json is valid JSON (no trailing commas) and that "type": "http" is set. Codex requires HTTP transport for remote servers; stdio transport is for local binaries only.

ChatGPT “Connectors” menu is missing

MCP support requires ChatGPT desktop app version 1.2024.352 or later and an active Plus, Pro, Team, or Enterprise subscription. Update the app and verify your plan in Settings → Account.

Cursor server shows red / “Failed to connect”

Verify your ~/.cursor/mcp.json is valid JSON and contains "type": "http". Then go to Settings → Cursor Settings → MCP and click Refresh. If the error persists, fully restart Cursor — config changes are not always picked up without a restart.

Windsurf MCP servers not listed in settings

Windsurf requires a full restart (not just a window reload) to pick up changes to mcp_config.json. Use File → Quit and relaunch. If servers still don’t appear, confirm you are on Windsurf 1.4+ via Help → About Windsurf.

Cline “Add Server” option is not visible

The MCP server manager requires Cline 2.0 or later. Open the VS Code Extensions panel, find Cline, and click Update if an update is available. After updating, reload VS Code (Ctrl+Shift+P → “Developer: Reload Window”).

---

Open Wink Portal Wink on GitHub