Servidor MCP de GuestLogic

• Nombre en el registroai.guestlogic/guest-logicverificado en el registro MCP

El nombre en el registro está bajo guestlogic.ai. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-11-03
• Herramientas19
• El servidor se llamaguest-logic
• Versión del servidor1.0.0
• Versión del protocolo2025-06-18

El 2026-11-03 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 117 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta191 ms
• Espacio en el contexto del agente≈ 2209 tokenslas definiciones de todas sus herramientas (19), que el agente lleva en cada turno
• Definiciones de herramientasA · 96 de 100
• Resultados tipados0 de 19 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 5 de 19

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• start_signup

  Creates the hotel in Guest Logic in free test mode. Use only when the owner has no Guest Logic account. After it, any other tool opens the sign-in for that e-mail. No sign-in needed.

• my_hotel

  The hotel's details: name, address, phone, rooms, check-in and check-out, taxes, and whether it is in test mode. Needs the owner's sign-in.

• setup_status

  The 12 setup steps: done or open, what was found for each, what needs a decision, and the reports already read. Needs the owner's sign-in.

• upload_report

  Sends one report's content as text (CSV, tab-separated or plain text, up to 4 MB) — read a PDF or spreadsheet first and send its rows. Guest Logic reads it and sets up what it can (rooms, room types, rates, taxes, stays). Returns what was…

• submit_facts

  Rooms and stays you already extracted, as rows. Guest Logic applies them by the same rules as an uploaded report. Needs the owner's sign-in.

• confirm_facts

  Confirms or changes one setup step. step and values: hotel {name, phone, email} · taxes {state, tourism, other} as percentages · checkin {check_in, check_out} as HH:MM · policies {cancellation, deposit, noshow, pets, smoking} · room_types…

• load_stays

  Loads the stays read from the reports into the hotel. First call without confirm to see the rows that need a decision; show them to the owner; then call with confirm true. Needs the owner's sign-in.

• add_photo

  Adds a picture from a public web address (PNG, JPEG or WebP, up to 10 MB) to the booking page: the hotel, or one room type. 40 a day while testing. Needs the owner's sign-in.

• set_logo

  Sets the hotel's logo from a public web address (PNG, JPEG or WebP, up to 10 MB). Needs the owner's sign-in.

• drop_link

  The owner's links to drop files you cannot send as text (a scanned PDF) and to manage photos. Needs the owner's sign-in.

• ask_us

  Asks the Guest Logic team to connect card payments, Expedia and Booking.com, or to finish the whole setup by hand. Connected within 24 hours. Needs the owner's sign-in.

• invite_staff

  E-mails a sign-in to a front-desk employee or a manager. Needs the owner's sign-in.

• stays

  Stays touching a date range (up to 31 days): confirmation, guest, dates, room, type, status, rate, source. Up to 200 rows a call; use page for more. Needs the owner's sign-in.

• stay

  One stay by its confirmation number. Needs the owner's sign-in.

• availability

  Rooms free each night by room type for a date range (up to 31 days). Needs the owner's sign-in.

• house_inventory

  For one day: arrivals, departures, in house, rooms by housekeeping status, rooms out of order. Needs the owner's sign-in.

• list_automations

  The hotel's automations: what each sends, when, and whether it is on. Needs the owner's sign-in.

• automation_status

  The last runs of the hotel's automations: when, result, error. Needs the owner's sign-in.

• tasks_waiting_on_me

  Open tasks on the signed-in person's Home board. Needs the owner's sign-in.