SynXis CRS MCP Server

MCP server for SynXis CRS (Central Reservation System) integration.

Version: 0.2.0 Status: Internal Bodai integration component

Quick Links

• Overview
• Capabilities
• Quick Start
• MCP Server Configuration
• Tool Reference
• Configuration
• Development
• Installation via Bodai Marketplace

Installation via Bodai Marketplace

This repo is packaged as a Bodai Claude Code plugin. Add the bodai-plugins marketplace, then install the synxis-crs plugin to expose the slash commands (/synxis-crs-lookup, /synxis-crs-availability, /synxis-crs-reservation) and connect to the running MCP server at http://localhost:3046/mcp. The plugin self-references its colocated .mcp.json, so no additional client configuration is required. Use the marketplace to keep the plugin versioned alongside the underlying server and to receive the same update flow as the rest of the Bodai fleet.

Quality & CI

Crackerjack is the standard quality-control and CI/CD gate for SynXis CRS MCP changes. Local verification should mirror the Crackerjack workflow used across the Bodai ecosystem.

Overview

SynXis CRS MCP exposes central-reservations workflows through a FastMCP server. It is designed for agent-facing hotel search, availability, rate lookup, and reservation creation while keeping provider credentials, request validation, and transport concerns in a narrow integration boundary.

The server is intentionally separate from synxis-pms-mcp. CRS owns shopping and booking workflows that belong to the central reservation system; PMS owns property operations such as guest, room, check-in, check-out, and folio workflows.

Capabilities

Tools (4 MCP tools):

• Property search (search_properties): find hotels by city, state, region, or other location text
• Availability lookup (get_availability): check available room types for a property and date range
• Rate lookup (get_rates): retrieve rate plans, totals, currency, and cancellation policy details
• Reservation creation (create_reservation): create a booking from property, room type, rate plan, dates, and guest details

Plus runtime features:

• Mock mode: exercise the MCP tool surface without live SynXis credentials
• HTTP health routes: /health and /healthz for MCP client and process supervision checks

Quick Start

Prerequisites

• Python 3.13+
• UV package manager
• SynXis CRS OAuth2 credentials for live API access

Local Setup

git clone https://github.com/lesleslie/synxis-crs-mcp.git
cd synxis-crs-mcp
uv sync --group dev

Run In Mock Mode

Mock mode is the safest way to validate client wiring and tool behavior before using live credentials.

export SYNXIS_CRS_MOCK_MODE=true
uv run synxis-crs-mcp start
uv run synxis-crs-mcp health

Run With Live Credentials

export SYNXIS_CRS_CLIENT_ID="your-client-id"
export SYNXIS_CRS_CLIENT_SECRET="your-client-secret"
export SYNXIS_CRS_HOTEL_ID="your-hotel-or-chain-id"
uv run synxis-crs-mcp start

The default HTTP bind is 127.0.0.1:3046.

CLI Commands

The CLI is built with mcp-common and provides the standard lifecycle command surface used by Bodai MCP servers.

uv run synxis-crs-mcp start      # Start the HTTP MCP server
uv run synxis-crs-mcp stop       # Stop the managed server process
uv run synxis-crs-mcp restart    # Restart the managed server process
uv run synxis-crs-mcp status     # Show process status
uv run synxis-crs-mcp health     # Run the local health probe

MCP Server Configuration

Claude / Codex Style Configuration

Add the server to an MCP client configuration:

{
  "mcpServers": {
    "synxis-crs": {
      "command": "uv",
      "args": ["run", "synxis-crs-mcp", "start"],
      "cwd": "/Users/les/Projects/synxis-crs-mcp",
      "env": {
        "SYNXIS_CRS_MOCK_MODE": "true"
      }
    }
  }
}

For live access, replace mock mode with credential environment variables supplied by your secret manager.

Health Checks

curl http://127.0.0.1:3046/health
curl http://127.0.0.1:3046/healthz

Tool Reference

Dates use YYYY-MM-DD. Tool responses follow a consistent ToolResponse shape:

{
  "success": true,
  "message": "Found 2 properties in Miami Beach",
  "data": {},
  "error": null,
  "next_steps": []
}

Configuration

Committed defaults live in settings/synxis-crs.yaml. Runtime overrides should come from environment variables or a local .env file that is not committed.

Project Structure

synxis_crs_mcp/
  cli.py              # mcp-common lifecycle CLI
  client.py           # SynXis CRS client boundary
  config.py           # Pydantic settings and logging
  models.py           # Typed CRS domain models
  server.py           # FastMCP application factory
  tools/crs_tools.py  # Registered MCP tools
settings/
  synxis-crs.yaml     # Committed defaults
tests/
  test_schema_validation.py

Development

uv sync --group dev
uv run pytest
uv run ruff check synxis_crs_mcp tests
uv run ruff format synxis_crs_mcp tests

Use direct pytest commands for targeted debugging:

uv run pytest tests/test_schema_validation.py -v

Security Notes

• Do not commit SynXis credentials, bearer tokens, tenant identifiers, or guest payment data.
• Keep examples and tests on mock mode or scrubbed fixtures.
• Treat reservation payloads and guest contact fields as sensitive operational data.
• Keep SynXis URLs, ports, and tenant settings configurable rather than hard-coded in new code.