Moodtrip Hotel Search

MoodTrip Hotel Search Skill

Pre-flight Check — EXECUTE THIS FIRST

Before attempting any hotel search, verify MoodTrip tools are accessible.

Step 1: Check for tools directly. Look for any of these tools in your available tool list: search_hotels, get_hotel_details, searchHotelsWithRates, findHotels, search_hotels_by_description, build_booking_link

If ANY of these tools are found → skip to Decision Rules and proceed normally.

Runtime detection: If you are running on OpenClaw, Codex, or any OpenAI-compatible runtime that validates tool schemas strictly, prefer search_hotels and get_hotel_details over searchHotelsWithRates and getHotelDetails. The wrapper tools have identical functionality with OpenAI-compliant schemas (no anyOf/oneOf at top level).

Step 2: Check if MCP server is already configured. If tools are not in your direct tool list, check whether api.moodtrip.ai or moodtrip is already configured as an MCP server anywhere in your platform config — including under any of these paths:

• mcp.servers.moodtrip
• plugins.entries.acpx.config.mcpServers.moodtrip
• skills.entries.moodtrip-hotel-search
• skills/moodtrip-hotel-search/_meta.json → mcpServers.moodtrip
• skills/moodtrip-hotel-search/.mcp.json

This skill ships with .mcp.json and _meta.json files that declare the MCP server configuration. If your platform reads these files from skill folders, the server should be auto-configured on install.

If these files are missing from the skill folder, this is an older version. Suggest the user update: clawhub update adiny/moodtrip-hotel-search or openclaw skills update

If the server IS configured but tools are not showing, this is likely a tool loading/exposure issue in the current session, not a missing connection. Restart the session or gateway if appropriate — some platforms only load MCP tools at session start.

Step 3: Auto-connect on OpenClaw when possible. If the server is NOT configured and you are running inside OpenClaw with config-edit capability:

• OpenClaw currently supports stdio MCP servers only (not HTTP). Use the mcp-remote bridge:
  • Add to config: mcpServers.moodtrip = { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://api.moodtrip.ai/api/mcp-http"] }
  • This wraps the HTTP MCP server as a stdio process that OpenClaw can load.
• If you have OpenClaw config tools available, patch config so the MCP server is added automatically.
• After adding it, restart/reload the gateway or start a fresh session — tools only load at session start.
• Then re-check whether the MoodTrip tools are exposed.

OpenClaw-specific rule:

• If the user asked to connect/install/fix MoodTrip MCP, and you can safely edit OpenClaw config, do it automatically instead of just telling the user to do it manually.
• Do NOT use mcp.servers.moodtrip.url (HTTP format) — it will be skipped. Use the stdio bridge format above.
• Do not invent tool availability; verify after restart/session refresh.

Step 4: Fallback if auto-connect is not possible. Only if auto-connect is not possible:

• mcporter available? Run: mcporter config add moodtrip https://api.moodtrip.ai/api/mcp-http
• clawhub available? Run: clawhub install adiny/moodtrip-hotel-search
• Neither available? Tell the user:

  "MoodTrip's hotel search tools aren't connected yet. Please add this MCP server in your platform settings: URL: https://api.moodtrip.ai/api/mcp-http No credentials required. For setup: https://github.com/adiny/moodtrip-hotel-search"

CRITICAL: Do NOT hallucinate hotel results. Do NOT call tools that don't exist. Do NOT attempt curl/fetch workarounds. If tools cannot be verified after all steps, help the user connect or restart the session.

This skill enables the agent to search, compare, evaluate, and hand off hotel bookings through the MoodTrip.ai MCP server. The server exposes 11 core tools covering the full hotel discovery-to-booking-handoff workflow.

Booking is link-based: the agent helps users find and compare hotels, then provides a direct booking URL. The user completes the reservation on the MoodTrip website.

Connection

MCP Server URL: https://api.moodtrip.ai/api/mcp-http Protocol: MCP Streamable HTTP (JSON-RPC 2.0) Authentication: Public read-only API — no credentials required. The server accepts only hotel search queries and returns publicly available hotel data.

For platform-specific setup instructions (Claude.ai, Claude Desktop, ChatGPT, OpenClaw), see: https://github.com/adiny/moodtrip-hotel-search

Quick Setup by Platform

Privacy & Data Handling

• All tools are read-only — no user data is stored, modified, or deleted
• Search queries are processed in real-time and not persisted
• No personal identifiers (names, emails, payment info) are collected or requested
• The server accepts only hotel search parameters (city, dates, guests, preferences)
• Full privacy policy: https://moodtrip.ai/privacy

Decision Rules

Before calling any tool, apply these rules to pick the right one:

Available Tools (11 core tools)

Agent Builder Tools (preferred on OpenClaw / Codex runtimes)

If your runtime uses OpenAI/Codex tool validation (e.g. OpenClaw), use these tools instead of the core equivalents. They have identical functionality with OpenAI-compliant schemas — no anyOf, oneOf, allOf, enum, or not at the top level.

On other platforms (Claude, ChatGPT, generic MCP clients), the core tools work fine and these are optional.

These tools are exposed via the same MCP server and are always available alongside the core tools.