Roomza Hotel Intelligence

io.github.roomza-incPublished by GitHub account roomza-incv1.1.0Updated Oct 28, 2026

The room-level truth layer of hospitality. Verified scores for exact hotel rooms, not just hotels.

VerifiedStreamable HTTPWeb executableLocation & LifestyleBusiness & Commerce

Overview

AI-generated overview

Roomza Hotel Intelligence lets an assistant search hotels, inspect room-level scores and reviews, check rates, and manage Roomza bookings.

What you can do
  • Search hotels by city, keyword or natural-language query, and read full hotel profiles with scores, character, amenities and review highlights.
  • List rooms with individual scores, bed type, view and floor, and display them through the required room display tool.
  • Read verified guest reviews, including per-room reviews and insider tips.
  • Check public room rates, with or without check-in and check-out dates.
  • Find nearby restaurants, bars, attractions and events around a hotel, and ask AI web-search questions about a hotel.
  • Look up your Roomza trips and saved preferences, add special requests to bookings, and price and lock an exact room with a booking link.
When to use it
Useful when planning or comparing hotel stays and wanting room-level detail rather than hotel-level ratings, or when managing existing Roomza bookings, preferences and special requests from a chat.
Requirements
A remote MCP endpoint at roomza.com over streamable HTTP; no package or local runtime. Trip, preference, special-request and room-lock tools require connecting a Roomza account.
Before you install
Several tools act on a connected Roomza account: adding special requests changes bookings, and secure_room prices and locks a room and returns a booking link, which can lead to a real reservation. Hotel questions are answered with AI plus web search, so results may be inferred rather than verified data.

Installation

In SourceWeft

  1. Open Roomza Hotel Intelligence in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.roomza-inc%2Froomza/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "roomza-hotel-intelligence": {
      "type": "http",
      "url": "https://www.roomza.com/api/mcp"
    }
  }
}

Tools

12

search_hotels

Search hotels

DISCOVERY ONLY: search Roomza's hotel database by city, keyword, or natural language query when the user has NOT named a specific hotel. Understands hotel types (boutique, resort, luxury), vibes (romantic, trendy, quiet), traveler types (couples, families, solo), neighborhoods, and nearby landmarks. Example queries: 'boutique hotels in SoHo', 'romantic resort near the Eiffel Tower', 'pet-friendly hotel in Seattle'. Renders for the user as a full map with a multi-hotel list (so do not repeat the list in prose). NEVER use this when the user names one specific hotel (e.g. 'Wynn Las Vegas'): the map of many hotels is wrong for that. Call get_hotel with the hotel name instead, then get_hotel_rooms and show_rooms.

Parameterscitylimitqueryrequired

get_hotel

Get hotel details

Get full details for a hotel including: Roomza Truth summary, score breakdown, top strengths, hotel character (type, vibes, best-for), nearby landmarks with distances, neighborhood, awards, amenities, and review highlights from the open web. Use hotel name, slug, or UUID as the identifier. This is the FIRST call when the user names a specific hotel ('Wynn Las Vegas') — no search_hotels needed; the name resolves directly.

Parametersidentifierrequired

get_hotel_rooms

List hotel rooms

List rooms for a hotel with individual Roomza scores, bed type, view, and floor. Pass room_number to look up a specific room.

Parametershotel_idrequiredroom_number

get_recent_reviews

Get guest reviews

Get verified guest reviews for a hotel, including comments and insider tips. Pass room_number to get reviews for a specific room.

Parameterslimithotel_idrequiredroom_number

get_hotel_pricing

Get room rates

Get public room rates for a hotel (the hotel's own public rate; booking on Roomza never costs more). Pass check_in and check_out dates (YYYY-MM-DD) to get nightly from-prices per room type. Without dates, returns the hotel's typical nightly from-price. No booking links; to price and book an exact room, use secure_room.

Parameterscheck_inhotel_idrequiredcheck_out

get_nearby

Get nearby places and events

Get nearby places (restaurants, bars, attractions, parks) and upcoming events near a hotel. Optionally filter events to a travel window with start_date / end_date.

Parametersend_datehotel_idrequiredstart_date

ask_about_hotel

Ask about a hotel

Ask a specific question about a hotel that standard data may not answer. Uses AI with web search to find the answer. Examples: 'Does this hotel have Eiffel Tower views?', 'Is there a rooftop bar?', 'How far is it from the airport?'. Try get_hotel first; use this only when that data doesn't answer the question.

Parametershotel_idrequiredquestionrequired

show_rooms

Show rooms

REQUIRED whenever you present rooms. Whenever you are about to mention, recommend, or describe one or more specific rooms to the user, you MUST call this tool with those room UUIDs INSTEAD of writing the rooms in text. This is mandatory even when there is only ONE matching room — show it as a single hero card, never describe a lone room in prose. Call this BEFORE writing any prose about the rooms; the cards must appear first, then a brief summary. Pass room UUIDs (from get_hotel_rooms or search results) in ranked order, best first, 1 to 8 rooms. ALWAYS pass check_in and check_out when you know the user's dates: card prices are then for those exact dates. Without dates, cards show a typical from-price that can differ a lot from any specific dates. Each card shows photo, Roomza score, view, bed, and price. NEVER ask the user whether they want to see cards or images — just call this tool.

Parameterscheck_inroom_idsrequiredcheck_out

get_my_trips

Your trips

Look up your upcoming and past hotel bookings/trips on Roomza. Requires connecting your Roomza account.

Takes no parameters.

get_my_preferences

Your preferences

Get your saved room preferences, standing requests, and loyalty accounts on Roomza. Requires connecting your Roomza account.

Takes no parameters.

add_special_request

Add a special request

Add a special request to one of your bookings (e.g. extra pillows, late checkout, anniversary celebration). Requires connecting your Roomza account.

Parametersrequestrequiredbooking_idrequired

secure_room

Price and lock a room

Price and lock an exact room for specific dates with Room Lock. Returns the live price, cancellation policy, and a secure booking link with the room preselected. Requires connecting your Roomza account.

Parametersguestsroom_idrequiredcheck_inrequiredcheck_outrequired

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.