ClarityIBE MCP Client

Connect Claude Desktop to the ClarityIBE booking API via Model Context Protocol (MCP).

Features

✈️ Flight Search - Search flights with flexible parameters 🎫 Booking Management - Create and manage bookings 💺 Seat Selection - Get seat maps and ancillary services 📄 Document Management - Handle travel documents 🔄 Post-Booking Services - Manage existing bookings

Prerequisites

• Node.js 14+ (Download)
• Claude Desktop (Download)

Quick Start

1. Configure Claude Desktop

Edit your Claude Desktop configuration file:

Windows: %APPDATA%\Claude\claude_desktop_config.json Mac/Linux: ~/Library/Application Support/Claude/claude_desktop_config.json

Add this configuration:

{
  "mcpServers": {
    "clarity-ibe": {
      "command": "npx",
      "args": ["-y", "clarity-ibe-mcp-client"],
      "env": {
        "CLARITY_SERVER_URL": "https://qa.clarity-mcp.claritytts.com",
        "CLARITY_API_KEY": "your-api-key-here"
      }
    }
  }
}

Important: Replace your-api-key-here with your actual API key provided by your administrator.

2. Restart Claude Desktop

Close and reopen Claude Desktop completely.

3. Verify Connection

In Claude Desktop, ask:

Can you list the available MCP tools?

You should see tools like:

• search_flights
• create_booking
• manage_booking
• get_seat_map_and_services
• And more...

Usage Examples

Search Flights

Search for flights from Delhi to Mumbai on December 1st, 2025 for 2 adults

Create Booking

Create a booking for this offer with passenger details:
- Name: John Doe
- DOB: 1990-01-15
- Email: [email protected]

Get Seat Map

Show me the seat map for this flight

Configuration

API Key (Required)

Get your API key from your administrator. The API key is required for authentication.

{
  "mcpServers": {
    "clarity-ibe": {
      "command": "npx",
      "args": ["-y", "clarity-ibe-mcp-client"],
      "env": {
        "CLARITY_SERVER_URL": "https://qa.clarity-mcp.claritytts.com",
        "CLARITY_API_KEY": "clarity_mcp_YOUR_ACTUAL_KEY_HERE"
      }
    }
  }
}

Server URL

The default server URL is https://qa.clarity-mcp.claritytts.com.

To use a different server (production, staging, etc.), update the CLARITY_SERVER_URL in your config:

{
  "mcpServers": {
    "clarity-ibe": {
      "command": "npx",
      "args": ["-y", "clarity-ibe-mcp-client"],
      "env": {
        "CLARITY_SERVER_URL": "https://your-custom-server.com",
        "CLARITY_API_KEY": "your-api-key"
      }
    }
  }
}

Multiple Environments

You can configure multiple servers (e.g., QA and Production):

{
  "mcpServers": {
    "clarity-ibe-qa": {
      "command": "npx",
      "args": ["-y", "clarity-ibe-mcp-client"],
      "env": {
        "CLARITY_SERVER_URL": "https://qa.clarity-mcp.claritytts.com",
        "CLARITY_API_KEY": "your-qa-api-key"
      }
    },
    "clarity-ibe-prod": {
      "command": "npx",
      "args": ["-y", "clarity-ibe-mcp-client"],
      "env": {
        "CLARITY_SERVER_URL": "https://prod.clarity-mcp.claritytts.com",
        "CLARITY_API_KEY": "your-prod-api-key"
      }
    }
  }
}

Troubleshooting

"Command not found" or "npx not found"

Solution: Install Node.js from nodejs.org

"Failed to connect to server"

Possible causes:

1. Server is not running
2. Wrong server URL
3. Network/firewall blocking connection

Solutions:

• Verify server URL is correct
• Test server connectivity: curl https://qa.clarity-mcp.claritytts.com/health
• Check firewall settings

Tools not showing in Claude Desktop

Solutions:

1. Verify configuration file syntax (use a JSON validator)
2. Restart Claude Desktop completely
3. Check Claude Desktop logs for errors
4. Ensure Node.js is installed: node --version

"Parse error" or "Invalid JSON"

Solution: Your configuration file has syntax errors. Use a JSON validator like jsonlint.com to check.

"401 Unauthorized" or "Invalid API key"

Possible causes:

1. Missing API key in configuration
2. Incorrect API key
3. API key expired

Solutions:

• Verify you've added CLARITY_API_KEY to your config
• Check the API key is correct (no extra spaces or quotes)
• Contact your administrator for a valid API key
• Example correct format:

  "CLARITY_API_KEY": "clarity_mcp_gPMJO1j8rrnMdCMPepZ26MF-ZNX3Rw1R8uCHGZD226o"

How It Works

┌─────────────────┐
│ Claude Desktop  │  (Your Machine)
└────────┬────────┘
         │ stdio (JSON-RPC)
         ↓
┌─────────────────┐
│  MCP Client     │  (This Package - via npx)
│  Bridge Script  │
└────────┬────────┘
         │ HTTPS
         ↓
┌─────────────────┐
│  ClarityIBE     │  (Remote Server)
│  MCP Server     │
└─────────────────┘

The client acts as a bridge:

1. Claude Desktop sends requests via stdio
2. Client forwards requests to HTTP server
3. Server processes and returns results
4. Client sends results back to Claude Desktop

Available Tools

| Tool | Description | |------|-------------| | search_flights | Search for available flights | | get_comprehensive_offer_details | Get detailed offer information | | create_booking | Create a new booking | | retrieve_booking | Retrieve existing booking details | | manage_booking | Cancel or modify bookings | | get_seat_map_and_services | Get seat maps and ancillary services | | manage_travel_documents | Manage travel documents | | reschedule_flight | Reschedule existing flights | | post_booking_services | Manage post-booking services |

Support

• Issues: GitHub Issues
• Documentation: Full Documentation
• Server Status: Check /health endpoint on your server

License

MIT License - See LICENSE file for details

Related

• Model Context Protocol
• Claude Desktop
• ClarityIBE API Documentation