Mews MCP
# Mews MCP Server
[](https://smithery.ai/server/@code-rabi/mews-mcp)
A Model Context Protocol (MCP) server for the Mews hospitality platform API. This server provides comprehensive access to Mews operations through a standardized interface.
## Overview
This MCP server provides comprehensive access to the Mews hospitality platform API, covering customer and company management, reservation operations, financial transactions, account management, configuration settings, and services inventory. It implements the core functionality needed for hospitality management through a standardized Model Context Protocol interface.
> **Disclaimer**: This is an unofficial MCP server for the Mews API and is not affiliated with or officially supported by Mews Systems s.r.o.
## Quick Start
### Using Smithery (Recommended)
The easiest way to use this MCP server is through [Smithery](https://smithery.ai), which provides hosted MCP servers:
1. Go to the [Mews MCP server on Smithery](https://smithery.ai/server/@code-rabi/mews-mcp)
2. Click "Add Configuration" and provide your Mews credentials
3. Copy the connection URL to your AI client
> **Demo Environment**: You can test this MCP server using Mews' public demo environment. The demo credentials are already included in the local installation example below and work with the demo API at `https://api.mews-demo.com`. These are publicly available test credentials from the [Mews API documentation](https://mews-systems.gitbook.io/connector-api/guidelines/environments#api-tokens-gross-pricing-environment).
### Using with NPX directly
To work directly with the published package, copy the following JSON and paste it in Claude, Cursor, or any other AI client that supports MCPs:
```json
{
"mcpServers": {
"mews-mcp": {
"command": "npx",
"args": ["-y", "mews-mcp@latest"],
"env": {
"MEWS_CLIENT_TOKEN": "07AB1F14B55C49B8BDD6AD200158423B-273A4497AFF5E20566D7199DB3DC2BA",
"MEWS_ACCESS_TOKEN": "BFD4298010F54B069F3DAD20015D53EA-D5561FADFBA4EFC8EA4C179C6BC461F",
"MEWS_CLIENT": "mews-mcp/1.0.0",
"MEWS_BASE_URL": "https://api.mews-demo.com"
}
}
}
}
```
> **Note**: The tokens above are public demo credentials from [Mews API documentation](https://mews-systems.gitbook.io/connector-api/guidelines/environments#api-tokens-gross-pricing-environment). Replace the `args` path with your actual installation path.
## License
MIT License - see LICENSE file for details. TDQS
Scored across 53 tools
Every tool has a clearly distinct purpose targeting specific resources and actions, such as addCustomer vs. updateCustomers or getAllReservations vs. cancelReservations. The descriptions reinforce these distinctions, with no ambiguous overlaps that would cause agent misselection.
Tool names follow a consistent verb_noun pattern throughout, using verbs like add, get, update, delete, export, and merge paired with specific nouns (e.g., addAccountingItems, getAllCustomers, updateReservations). There are no deviations in naming conventions, making the set highly predictable.
With 53 tools, the count is excessive for typical MCP server purposes, making it heavy and potentially overwhelming for agents. While the domain is broad (hotel/enterprise management), many tools could be consolidated or scoped down to improve usability without losing functionality.
The tool surface provides comprehensive CRUD/lifecycle coverage across all major domains (customers, reservations, loyalty, accounting, etc.), including add, get, update, delete, and export operations. There are no obvious gaps, ensuring agents can handle full workflows without dead ends.