Full MCP

Connect Full MCP when an agent should call Nuitee Connect itself. To have the agent write the booking app, install Skills for coding agents.

Need documentation and product knowledge only? Use Docs MCP at https://mcp.liteapi.travel/api/knowledge (no API key, no live booking tools).

Full MCP enables AI assistants to run operations on your account by leveraging the API endpoints made available.

Endpoint

The Nuitee Connect MCP server is available at:

https://mcp.liteapi.travel/api/mcp

Send your API key on the X-API-Key header. ?apiKey= on that URL also works. Prefer the header so the key is not stored in access logs.

For sample calls, send the shared sandbox key sand_ca230deb-5a6b-42e7-bb72-869facd8892b. A connection with no key can return 401 unauthorized on a tool call. Send your own key to use your account.

⚠️ Never expose production API keys in client-side applications.

What Is MCP?

MCP (Model Context Protocol) is a standardized way for AI models to:

Discover available tools
Call APIs in a structured format
Receive machine-readable responses
Perform multi-step workflows safely

The Nuitee Connect MCP server wraps Nuitee Connect functionality as structured tools that AI systems can call deterministically.

Supported Capabilities

The MCP server exposes Nuitee Connect features such as:

Hotel search
Price and availability lookup
Place search
Hotel details retrieval
Prebooking
Booking flows

Available tools may evolve as Nuitee Connect expands AI capabilities.

These tools work with or without your own key:

list_endpoints searches the API catalog (method, host, path)
describe_endpoint returns the HTTP contract for one endpoint
search_docs and fetch_docs_page read pages on https://docs.liteapi.travel
fetch_documentation loads a curated OpenAPI/docs key (searchApi, bookingApi, …)
search_dashboard_kb and fetch_dashboard_feature read Nuitee Connect product guides (dashboard UI / how-to)

Documentation-only agents should use Docs MCP at https://mcp.liteapi.travel/api/knowledge (same seven tools, no live API execute tools, no key).

To have a coding agent build the app in your repo, install the skill for coding agents. Keep the API key on your server. Use Full MCP when the agent should call the API itself.

OAuth

Clients that offer OAuth (Lovable, Claude, ChatGPT, Cursor) use the server URL alone:

https://mcp.liteapi.travel/api/mcp

Leave client id and client secret empty. The client registers itself, then opens Nuitée Connect. Approval uses the dashboard session at https://connect.nuitee.com. Choose sandbox or production there. The access token is not your API key. The MCP server exchanges it for the key on that account.

X-API-Key still works for clients that only have a header.

Authentication

Pass your Nuitee Connect API key on the X-API-Key header. The header name is case-insensitive.

X-API-Key: YOUR_API_KEY

These also work:

Query parameter: ?apiKey=YOUR_API_KEY
Authorization: Bearer YOUR_API_KEY

If more than one is set, the header is the one that is used. Prefer the header. Query parameters end up in access logs.

Sample calls use the shared sandbox key sand_ca230deb-5a6b-42e7-bb72-869facd8892b on X-API-Key. A missing key can return 401. Discovery and docs tools work with that sandbox key.
Sandbox and production keys must match their respective environments
Rate limits apply as per your API plan

Example Configuration (AI Tooling)

{
  "mcpServers": {
    "liteapi": {
      "url": "https://mcp.liteapi.travel/api/mcp",
      "headers": {
        "X-API-Key": "sand_ca230deb-5a6b-42e7-bb72-869facd8892b"
      }
    }
  }
}

The value above is the shared sandbox key. Replace it with your Nuitee Connect key to use your account.

Rate Limits & Usage

The MCP server follows standard Nuitee Connect API policies:

Default rate limit: 500 requests per second
HTTP 429 returned when rate limited
Usage billed according to endpoint pricing
Monitoring available in the Nuitee Connect dashboard

Security Considerations

When integrating AI systems with Nuitee Connect MCP:

Store API keys securely (e.g., environment variables or secret managers)
Do not embed keys in client-side code
Implement retry and backoff logic
Monitor agent behavior to prevent excessive calls