SiteMinder MCP Server

Tarifas, disponibilidad y reservas en tu channel manager de SiteMinder.

Servidor MCP alojado

npx add-mcp 'https://cotlet.dev/mcp/v1/siteminder'

Se instala en Claude Code, Codex, Cursor y más

Documentación

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

SiteMinder API and MCP server: Let your AI agent work your SiteMinder inventory grid.

SiteMinder's five APIs serve PMS, RMS, channel and app partners, and its MCP work sells your rooms to AI travel sites (checked 27 Oct 2026). Nothing lets your own agent change rates or read reports, so Cotlet runs 12 SiteMinder tools hosted, over MCP for agents and REST for scripts.

Rates, availability and reservations in your SiteMinder channel manager. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

What can you automate in SiteMinder?

  • Raise rates for event nights
  • Set minimum stay and closed to arrival
  • Fill gap nights between bookings
  • Pull rooms out of sale for repairs
  • List tomorrow's arrivals by channel
  • Report channel mix, pace and parity

Does SiteMinder have an MCP server or an API?

  • pmsXchange, SiteConnect, Channels Plus and SMX need a partner contract and certification. The Direct Booking key reads booking-engine prices and room data only.
  • Channels Plus MCP and Direct Booking MCP (April 2026) let AI travel apps find and book your hotel. They do not touch your grid, reservations list or Insights.
  • Zapier and n8n have no SiteMinder app. The Developer Guide MCP answers questions about the docs, not your property.
What you needCertified PMS or RMSDirect Booking APICotlet
Change rates, availability, restrictionsFrom that system's screensNo, read onlyYes, after your OK
Read reservationsDelivered into the PMSNoYes, without card data
Booking performance, pace, parityInsights onlyNoYes, as data
Your AI agent can call itIf the PMS has an APIPrices, with your developerYes, MCP and REST
Who can get itVendors, after certificationDirect Booking customersAny SiteMinder user

Checked 27 Oct 2026. Sources: SiteMinder APIs and who they are for, SiteMinder Help: Direct Booking API, SiteMinder AI distribution (Channels Plus MCP), Supergood API report card: SiteMinder

How does Cotlet connect to SiteMinder?

  1. Sign in to SiteMinder. Use your own account in its Cotlet Cloud Browser.
  2. Choose MCP or REST. Connect your agent or create a Cotlet API key.
  3. Run your workflow. Ask your agent or send an HTTP request.

We never keep your SiteMinder password, and no rate, room count or restriction reaches a channel until you approve it.

Connect SiteMinder to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

  1. Sign in to SiteMinder through Cotlet. Create a Cotlet account, open SiteMinder in its Cloud Browser, log in with the user you made for the agent, then press Enable for agents.
  2. Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 where your agent lists MCP servers or connectors.
  3. Approve the connection. Chat apps send you to a Cotlet login. Code editors, n8n and scripts use an API key from the console instead.

SiteMinder uses the shared address https://cotlet.dev/mcp/v1, together with every other app you turn on. If you enabled it after connecting, refresh the connector and the 12 SiteMinder tools show up.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-siteminder \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-siteminder": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-siteminder]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: siteminder_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: siteminder_write

How to use the SiteMinder REST API

Create your Cotlet API key

Create a Cotlet API key with access to SiteMinder and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect SiteMinder in Cotlet and enable it for agents. Account access: Your own SiteMinder Platform account (Admin or a General user with access to the areas you use).

Make your first SiteMinder API request

REST:

curl https://cotlet.dev/api/v1/siteminder/room-rates \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read room rates and apply the operation limits

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "siteminder",
  "tool": "list_room_rates",
  "result": {
    "room_types": [
      {
        "room_type_id": "rt_1021",
        "name": "Standard Double",
        "room_rates": [
          {
            "room_rate_id": "rr_48210",
            "name": "Standard Double Flexible",
            "type": "base",
            "channels": [
              "Booking.com",
              "Expedia",
              "Direct Booking"
            ]
          }
        ]
      },
      {
        "room_type_id": "rt_1022",
        "name": "Deluxe King",
        "room_rates": [
          {
            "room_rate_id": "rr_48213",
            "name": "Deluxe King Flexible",
            "type": "base",
            "channels": [
              "Booking.com",
              "Expedia",
              "Agoda",
              "Direct Booking"
            ]
          },
          {
            "room_rate_id": "rr_48214",
            "name": "Deluxe King Non-refundable",
            "type": "derived",
            "derived_from": "rr_48213",
            "channels": [
              "Booking.com",
              "Expedia"
            ]
          }
        ]
      }
    ]
  }
}

Returns every room type with its room rates. A derived rate shows the base rate it follows; SiteMinder does not let you set derived rates by hand.

Use the IDs from here in get_inventory and the update tools.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

SiteMinder workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestThe inventory grid for a date range: rates, availability and restrictions per room rate and channel. Use get_inventory in your configured travel brief.
MakeHTTP > Make a requestReservations with channel, status, dates, room and total. Searches the last 548 days. Use list_reservations in your configured travel brief.
Python or Node.jsREST APIRoom and total revenue, reservations, room nights, ADR, ALOS, lead time and cancellations, split by channel, market, room or rate. Use get_booking_performance in your configured travel brief.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads SiteMinder; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

SiteMinder API endpoints and MCP tools

Inventory grid: rates, rooms and restrictions

Derived rates follow their base rate and cannot be set. Where a two-way PMS or RMS sends the same data, its next sync wins.

  • List room rates (list_room_rates, read): Room types and their room rates, with derived rates and the channels each one is mapped to.
  • List channels (list_channels, read): Connected booking channels with status and the data each channel rate supports.
  • Get inventory (get_inventory, read): The inventory grid for a date range: rates, availability and restrictions per room rate and channel.
  • Update rates (update_rates, write, asks first): Set the rate for room rates or channel rates over a date range. Goes live on mapped channels.
  • Update availability (update_availability, write, asks first): Set the number of rooms to sell per room type over a date range, for all channels.
  • Update restrictions (update_restrictions, write, asks first): Set stop sell, minimum or maximum length of stay, closed to arrival or closed to departure.
  • Close dates (close_dates, write, asks first): Stop sell the room rates you pick, or a whole channel, for a date range.

Reservations

Read only. Guest e-mail, phone and card details stay behind SiteMinder's trusted-device check and never come back.

  • List reservations (list_reservations, read): Reservations with channel, status, dates, room and total. Searches the last 548 days.
  • Get reservation (get_reservation, read): One reservation: stay, rooms, rate plan, channel, status history and payment summary. No guest contact or card numbers.

Insights reports

Rate parity needs SiteMinder Plus; without it that one call fails and costs nothing.

  • Get booking performance (get_booking_performance, read): Room and total revenue, reservations, room nights, ADR, ALOS, lead time and cancellations, split by channel, market, room or rate.
  • Get pace report (get_pace_report, read): Reservations, revenue, room nights and ADR for a period, compared with the same period last year.
  • Get rate parity (get_rate_parity, read): Your rates on Agoda, Booking.com, Expedia, HRS and Direct Booking by stay date. Needs SiteMinder Plus.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/siteminder-api-mcp-server#tools

Who can see my SiteMinder session, and how do I revoke it?

  • What we store. The signed-in SiteMinder browser profile, AES-256-GCM encrypted, in Finland. Never the password.
  • What your agent gets. The 12 SiteMinder tools. Not the cookie, not guest contacts, not card numbers.
  • What the session sees. Only the areas that SiteMinder user has permission for. A General user starts read only.
  • What no tool touches. Payment details, billing, user management, PMS settings and channel mapping.
  • When SiteMinder asks to verify. A new device needs MFA or an e-mail link. You confirm it; we never do.
  • How to cut access. Disable for agents, reset the browser, or remove its trusted device in SiteMinder.

cotlet.dev holds A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). We do not have a SOC 2 report or a third-party pentest yet.

Is it against SiteMinder's terms? Account safety

We will issue each Customer User with login credentials to access the Products (including username and password). These login credentials are personal and must not be shared.

SiteMinder customer terms and conditions, clause 3.7, read 27 Oct 2026 (Wayback copy of 14 Jun 2026)

The customer terms do not mention bots, scraping or automation. Clause 3.3 limits use to "Customer Users", and clause 1.1 counts your "agents, contractors or representatives" among them. SiteMinder Help adds that every staff member needs a user with a unique e-mail, and a shared login is "not permitted". So give the agent a General user of its own, with only the inventory and reservation permissions it needs. We found no public case of a hotel account closed for automation (checked 27 Oct 2026).

How we keep your property account safe:

  • A SiteMinder user you create for the agent, not a staff member's login
  • No payment permission, so card details stay locked
  • One Cloud Browser that you trust once, so no new-device checks
  • Rates, room counts, restrictions and stop sells wait for your OK
  • If SiteMinder objects, we pause the SiteMinder tools for everyone within 24 h

Every change goes on to Booking.com, Expedia and your other channels. Group a season into a few date ranges with days_of_week instead of hundreds of single nights.

What happens when SiteMinder changes?

  • 12 h between tests of the grid, reservation and Insights reads
  • 24 h between tests of writes that reach your channels
  • $0 for a call to a SiteMinder tool paused for repair

SiteMinder keeps shipping: trusted devices became required on 22 Sep 2026, and the Dynamic Commerce Engine arrived the next day. When a screen moves, we repair the tool and your scheduled runs keep their prompts. status.cotlet.dev checks the site, console and API every 3 minutes.

Approvals, undo and mistakes

  1. Reads the grid. get_inventory saves every night as it is now.
  2. Groups the change. One call per value, date range and weekdays.
  3. Waits for your OK. Old and new values sit in your Cotlet console.
  4. Checks it landed. Reads the nights again and names any that did not.
ActionUndo
Update ratesSend the saved rate; rooms sold meanwhile keep the new price
Update availabilitySet the old room count again
Update restrictionsRun it again with the old values; min stay 1 means none
Close datesupdate_restrictions with stop_sell false
ReservationsNo tool changes them; OTA bookings are cancelled on the channel

All 4 write tools of 12 ask first, because each one reaches your channels. The 8 reads run at once. When a scheduled job, such as the daily gap-night fix, has gone right a few times, you can switch the wait off for that tool.

If a two-way PMS or RMS owns rates or restrictions, it overwrites a change made in SiteMinder at its next sync. The agent says so before it asks you.

MCP call:

{
  "name": "update_restrictions",
  "arguments": {
    "room_rate_ids": [
      "rr_48213",
      "rr_48214"
    ],
    "from": "2026-12-24",
    "to": "2026-12-26",
    "restrictions": {
      "cta": true,
      "min_los": 3
    }
  }
}

REST:

curl -X PATCH https://cotlet.dev/api/v1/siteminder/restrictions \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"room_rate_ids":["rr_48213","rr_48214"],"from":"2026-12-24","to":"2026-12-26","restrictions":{"cta":true,"min_los":3}}'

Response:

{
  "status": "updated",
  "room_rates": 2,
  "dates": 3,
  "channels": [
    "Booking.com",
    "Expedia",
    "Direct Booking"
  ],
  "skipped": [
    {
      "channel": "Agoda",
      "reason": "CTA not supported by this channel rate"
    }
  ]
}

A revenue spreadsheet or a nightly cron job calls the same tools over REST at /api/v1/siteminder, with one key and one price. A channel that does not take CTA comes back under skipped, so you know which extranet to open. The tools table lists the REST path of each tool.

How much does the SiteMinder MCP server cost?

About $23 a month for a 40-room hotel, 3,880 credits. Your SiteMinder subscription stays as it is.

JobCallsCredits
Tomorrow's arrivals, daily4 × 301,200
Gap nights under minimum stay, daily3 × 30900
Channel mix and pace, Mondays3 × 4120
Rate parity, weekly1 × 440
Event pricing over a weekend6 × 2120
Cloud Browser, 30 days1,500
Total3,880
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Any SiteMinder plan; rate parity needs SiteMinder Plus

The hotel is our example. SiteMinder lists 56,000 hotels and 2.5 million rooms, about 45 rooms each. For comparison, SiteMinder's own price list puts a 40-room property at $315 a month, or $415 on Plus (Americas, 27 Oct 2026). Dollars here at the $29 pack rate.

SiteMinder MCP server on GitHub, Zapier or hosted: which to use

OptionWhat it doesWhere it stops
anapartner-com/siteminder-mcp-appAn MCP server for Broadcom's CA SiteMinder, a login and access product.Not the hotel platform at all. 0 stars, last push Nov 2025.
Dynamic Revenue PlusSiteMinder add-on that applies IDeaS prices within your floor and ceiling.Its own model, not your rule; a fee on completed stays.
Dynamic Commerce Engine (Sep 2026)Finds pricing and mapping fixes inside SiteMinder and applies them after approval.No API or MCP; your agent cannot ask it anything.
RoomPriceGenie and other RMS appsRevenue management that pushes rates through SiteMinder.Rates only, about €198 to €440 a month.
SupergoodBuilds an unofficial API on the web app for one customer.Made to order, no public price.
Zapier, n8nNothing: no SiteMinder app.Both pages answer 404.

Nobody else runs an MCP server for SiteMinder's hotel platform. An RMS prices well and stops there, and SiteMinder's own AI works only inside its screens. Cotlet gives your agent the grid, reservations and Insights in the subscription you already pay for, and runs your rules instead of a model's.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Cotlet belongs to Take Group sp. z o.o., registered in Poland, EU (VAT PL6342984273), building software since 2019. Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing) founded it. Send questions about the SiteMinder tools to contact@cotlet.dev.

SiteMinder API and MCP: questions

How do I get access?

Sign up free at https://cotlet.dev, open SiteMinder under Integrations in the console and log in to SiteMinder in its Cloud Browser. The trial starts right away and asks for no card.

How do I connect SiteMinder to ChatGPT or Claude?

Sign up at cotlet.dev, log in to SiteMinder once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your SiteMinder account through Cotlet, in their phone apps too.

What can ChatGPT do in SiteMinder?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in SiteMinder: update rates for busy dates; set minimum stay and closed to arrival for peak dates; fill gap nights between bookings. You ask in plain words, and anything that reaches other people waits for your OK first.

Does it work if my hotel has a connected PMS or RMS?

Reads work either way. For changes, SiteMinder says a two-way PMS, RMS or CRS overwrites manual updates in the inventory grid, so rates, availability and restrictions are changed in that system. Cotlet changes the same grid you do, so use the write tools only for data your PMS does not sync.

Can it cancel or change a channel reservation?

No. SiteMinder says channel bookings from Booking.com, Expedia and other OTAs cannot be cancelled in the platform; the guest or you must cancel at the channel. Cotlet reads reservations and does not change them.

Does it return guest emails, phone numbers or card details?

No. Since 22 Sep 2026 SiteMinder shows guest contact and card details, and allows reservation downloads, only on a trusted device (SiteMinder Help: Trusted devices). get_reservation leaves those fields out.

Which SiteMinder user should the agent use?

A user of its own. In User management, add a General user with a unique e-mail and turn on only the inventory grid and reservation permissions. Leave guest payment details off. You need a trusted device to add users.

What about MFA and trusted devices?

You set up MFA for the agent's user and confirm the Cloud Browser as a trusted device with the e-mail link SiteMinder sends. A trusted device signs in without an MFA prompt, so this is mostly a one-time step. We never enter codes for you.

Is this the same as the Little Hotelier MCP server?

No. Little Hotelier is SiteMinder's product for small properties, with its own login and screens, and has its own Little Hotelier MCP server page on Cotlet. This page covers the SiteMinder platform.

Is the MCP server different from the REST API?

Only the way in differs. Both carry the same 12 tools, inputs and answers, with one key and one price. Agents connect over MCP; scripts and HTTP steps call REST.

Is Cotlet affiliated with SiteMinder?

No. Cotlet is independent and not affiliated with SiteMinder Limited or with Broadcom.

Can I use the SiteMinder API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.


Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.