[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Mews MCP server: Let your AI agent run your Mews front desk. > Mews has an official Connector API and no official MCP server (checked 6 Nov 2026). Cotlet adds 11 Mews tools for Claude and ChatGPT: no Mews API credentials or developer setup, hosted 24/7, one Cotlet account for many apps. Brief the morning arrivals, add guest notes and create tasks in Mews by asking in plain words. It works in your own Mews login, inside Claude or ChatGPT. Nothing to install or host. - Free 7-day trial, no card - Unofficial, not affiliated with Mews - Page: https://cotlet.dev/integrations/mews-api-mcp-server ## What can your AI agent do in Mews? - Brief today's arrivals and departures - Create tasks for missed check-outs - Add guest preferences to arrivals - Cancel unconfirmed optional bookings - List guests in house by room - Send weekly stay numbers ## Does Mews have an MCP server or an API? - Every Connector API call carries a ClientToken and an AccessToken. Production tokens arrive by email after Mews certification, and the property needs the Connectivity add-on or the Enterprise package. - Mews has a Zapier app with 23 operations: 6 triggers, 12 actions and 5 searches. It includes Create New Task and Update Customer. - Community Mews MCP servers on GitHub run on the same API tokens. | What you need | Connector API | Zapier | Cotlet | |---|---|---|---| | What you set up | Certification, tokens, code | A connection and a Zap per job | Sign in to Mews once | | List arrivals and departures for a day | You build the list | Reservation events and lookups | Yes, as the Mews tabs show them | | Create a task | Yes, after certification | Yes, Create New Task | Yes, after your OK | | Add a reservation note | After certification | Not in the action list | Yes, after your OK | | Cancel a reservation | After certification | Not in the action list | Yes, after your OK | | Use it inside Claude and ChatGPT | You build the agent layer | Through Zapier MCP | Yes, one address | Checked 6 Nov 2026. Sources: [Mews Connector API: Authentication](https://docs.mews.com/connector-api/guidelines/authentication), [Mews Connector API: Getting started](https://docs.mews.com/connector-api/getting-started), [Mews Connector API: Certification](https://docs.mews.com/connector-api/guidelines/certification), [Mews Connector API: Private integration journey](https://docs.mews.com/connector-api/your-journey/private-integration), [Zapier: Mews operations](https://zapier.com/apps/mews/integrations) ## How does Cotlet connect Mews to your AI agent? 1. **Sign in to Mews.** Use your own login in your Cotlet Cloud Browser. 2. **Connect your AI agent.** Add one address to Claude, ChatGPT or n8n. 3. **Ask in plain words.** Your agent works in your Mews. We never keep your Mews password, and no note, task or cancellation happens until you approve it. ## How to connect Mews to your AI agent Three steps. Chat apps, editors, n8n and scripts use the same Cotlet address. 1. **Enable Mews for agents.** Sign up, sign in to Mews in its Cloud Browser, then press Enable for agents. 2. **Add the Cotlet address.** Add https://cotlet.dev/mcp/v1 as an MCP server or connector in your agent. 3. **Approve the connection.** Chat apps ask you to sign in to Cotlet. Editors, n8n and scripts use an API key from the console. One shared address, `https://cotlet.dev/mcp/v1`, also carries Mews next to your other apps. If you enable Mews after connecting, refresh the connector so the new tools show up. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-mews \ 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-mews": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-mews] 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, Tool: mews_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: mews_write ``` ## All 11 Mews MCP tools ### Arrivals, departures and stays Read only. They follow the Reservation overview tabs, so the account needs access to that screen in Mews. - **List arrivals** (`list_arrivals`, read): Reservations arriving on a day, as in Reservation overview, Arrivals tab. - **List departures** (`list_departures`, read): Reservations departing on a day, as in Reservation overview, Departures tab. - **List guests in house** (`list_guests_in_house`, read): Guests staying at the property, as in the Guests in house report. - **Get stay statistics** (`get_stay_statistics`, read): Daily counts from Reservation overview, Statistics tab. ### Reservations and guests Read only. A guest profile has no identity documents or payment details. - **List reservations** (`list_reservations`, read): Reservations by status and date, as in the Reservation report. - **Get a reservation** (`get_reservation`, read): One reservation with its status, dates, notes and customer. - **Find a customer** (`find_customer`, read): Customers whose name matches the search, as in the Mews search bar. - **Get a customer profile** (`get_customer`, read): A guest profile: contact details, Internals notes, reservations and open bills. ### Notes, tasks and cancellations Each one asks first. A department must already exist in Settings, and a guest in house cannot be cancelled. - **Add a reservation note** (`add_reservation_note`, write, asks first): Add a note in the reservation's Notes section. - **Create a task** (`create_task`, write, asks first): Create a task for an employee or a department, optionally linked to a reservation. - **Cancel a reservation** (`cancel_reservation`, write, asks first): Cancel a reservation from its Status tab. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/mews-api-mcp-server#tools ## Who can see my Mews session, and how do I revoke it? - **What we store.** Your signed-in Mews profile, encrypted with AES-256-GCM, in Finland. Not the password. - **What your agent gets.** The 11 Mews tools. Never the cookie. - **What the session sees.** What your Mews login sees: reservations, guests, notes, tasks. - **What no tool touches.** Bills, payments, settings, password and two-factor. - **If Mews asks for a code.** You type it in. We never do. - **How to cut access.** Disable for agents, reset the browser, or sign out of Mews. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). ## What can the agent do in my Mews? The agent works in your own signed-in Mews Operations session, so it sees what your login sees. Reading the day lists needs access to Reservation overview. Cancelling needs the Create and manage reservations permission. Log in with a front desk role and the agent does front desk work. Log in with a narrower role and it does less. Nothing here asks Mews for extra rights. How the agent stays in its lane: - Your own Mews login, signed in by you - One Cloud Browser for your property, with its own cookies - Notes, tasks and cancellations wait for your OK - No tool reads identity documents or payment details - Cancel works only before check-in ## What happens when Mews changes? - **12 h** between tests of the Mews tools - **$0** for a call to a Mews tool paused for repair When Mews moves a tab or renames a column, the fix happens on our side and your prompts keep working. [status.cotlet.dev](https://status.cotlet.dev) watches the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the departures.** Bookings flagged Check-out missed come first. 2. **Finds the reservation.** The task links to the guest's booking. 3. **Waits for your OK.** The task shows up in your Cotlet console first. 4. **Reports the task.** Task ID, department, linked reservation. | Action | Undo | |---|---| | Add a reservation note | Staff edit or delete the note in Mews | | Create a task | Close it in Mews; only staff see it | | Cancel a reservation | No. Create the booking again in Mews | 3 of 11 tools ask first: all three writes. The 8 reads change nothing. Switch the wait off per tool for a scheduled run. > A guest who is in house cannot be cancelled. Shorten the stay and check the guest out in Mews instead. MCP call: ``` { "name": "create_task", "arguments": { "name": "Check-out missed: call guest", "department": "Front desk", "reservation_id": "b2e1d3c5-8c7f-4d2b-8f42-3a6e9c1d2b01" } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/mews/tasks \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"name":"Check-out missed: call guest","department":"Front desk","reservation_id":"b2e1d3c5-8c7f-4d2b-8f42-3a6e9c1d2b01"}' ``` Tool output: ``` { "task_id": "f6a5b7c9-2a1d-4b6f-8d86-7e0c3a5b6f01", "name": "Check-out missed: call guest", "department": "Front desk", "reservation_id": "b2e1d3c5-8c7f-4d2b-8f42-3a6e9c1d2b01", "status": "open" } ``` Scripts and cron jobs reach the same tools over REST, with the same key and price. The tools table lists the REST path of each tool. A failed call costs nothing. ## How much does the Mews MCP server cost? **About $43 a month** for a 50-room hotel, 7,380 credits. Your Mews plan is billed by Mews as before. | Job | Calls | Credits | |---|---|---| | Morning brief: arrivals, departures, numbers | 3 × 30 | 900 | | Task for a missed check-out | 2 × 30 | 600 | | Preference notes on tomorrow's arrivals | 11 × 30 | 3,300 | | Cancel unconfirmed optional bookings, weekly | 6 × 4 | 240 | | Weekly stay numbers | 1 × 4 | 40 | | Front desk questions: find a guest, read a booking | 2 × 40 | 800 | | Cloud Browser, 30 days | | 1,500 | | Total | | 7,380 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - Mews plan prices stay with Mews The month is our example: about 17 arrivals a day, 5 of them with a preference note, one missed check-out a day. Small Luxury Hotels of the World says its Mews hotels have 50 rooms on average. Mews publishes no average of its own. Dollars at the $29 pack rate. ## Mews MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [code-rabi/mews-mcp](https://github.com/code-rabi/mews-mcp) | Unofficial MCP server on the Connector API: customers, reservations, transactions, settings. Also hosted on Smithery with 53 tools. | Needs your own API tokens. 0 stars, last commit 6 Aug 2025. | | [tjg37/mews-mcp-server](https://github.com/tjg37/mews-mcp-server) | Local MCP server for Claude Desktop and Claude Code, MIT licence. | Needs API tokens and runs on your computer. 0 stars, last commit 20 Mar 2026. | | [Peliqan](https://peliqan.io/model-context-protocol/mews-mcp/) | Hosted MCP server, EUR 15 per connection a month. Questions run on a synced copy of your Mews data. | Reservations, bills and payments are read only. Writes cover rates, vouchers and companies. | | [Zapier and Zapier MCP](https://zapier.com/mcp/mews) | Mews operations as Zaps or as MCP tools: 6 triggers, 12 actions, 5 searches. | No action to add a note or cancel a reservation. | The Mews Connector API is the official route if your hotel has the certification and a developer. The GitHub servers sit on it. Cotlet needs neither: it works in your signed-in Mews and is hosted, so ChatGPT, your phone and a 7 a.m. schedule all work. ## Who runs Cotlet Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), working since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Mews tools. ## Mews MCP server: questions ### How do I connect Mews to ChatGPT or Claude? Sign up at cotlet.dev, log in to Mews 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 Mews account through Cotlet, in their phone apps too. ### What can ChatGPT do in Mews? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Mews: morning arrivals and departures brief; create tasks for missed check-outs; add guest preferences to arriving reservations. You ask in plain words, and anything that reaches other people waits for your OK first. ### How do I get access? Create a free account at https://cotlet.dev, open Mews under Integrations in the console and sign in to Mews in its Cloud Browser. The trial starts with your first app, no card asked. ### Do I need Connector API tokens to use Mews with an AI agent? No. Cotlet works in your own signed-in Mews session. Mews issues production Connector API credentials only after a certification process (docs.mews.com, Authentication). Your Mews role still counts: the agent can only do what your account is allowed to do. ### Can the agent cancel a checked-in reservation? No. Mews does not allow cancelling a reservation that is in house, so cancel_reservation fails for it. A reservation that has not checked in can be cancelled while it is inside the property's editable history window. ### Does Mews have webhooks? Yes, through the Connector API, for certified integrations. Cotlet does not receive them, so run your agent on a schedule instead, for example a list_arrivals and list_departures pass every morning. ### Does it work on every Mews plan? Cotlet works in your own Mews login. What the agent can reach follows your role, not a Cotlet setting. ### Can the agent read payment details or identity documents? No. get_customer returns the profile, the Internals notes, reservations and open bill counts. It does not return identity documents or payment details. ### Is the MCP server different from the REST API? Only the door is different. Both expose the same 11 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with Mews? No. Cotlet is independent and not affiliated with Mews. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) 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](https://cotlet.dev/about.md) 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.