MCP for Developer Integrations

Connect an AI agent to Nuitee Connect documentation and product knowledge — without giving it live hotel search, prebook, or booking tools.

Use this when the agent should understand Nuitee Connect (API contracts, guides, dashboard how-tos). Use MCP for AI Agents when the agent should call the API on your account.

Endpoint

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

No API key and no OAuth required. Every tool is read-only.

Works in Cursor, Windsurf, Claude, ChatGPT, and other MCP clients that support Streamable HTTP.

When to use which

MCP for Developer IntegrationsMCP for AI Agents
URLhttps://mcp.liteapi.travel/api/knowledgehttps://mcp.liteapi.travel/api/mcp
AuthNoneAPI key or OAuth
Docs, OpenAPI catalog, product guidesYesYes
Live search / rates / book toolsNoYes
Best forLearning the product, grounding answers, least privilegeAgents that book or query your account

To have an agent write a booking app in your repo (key stays on your server), install Skills for coding agents instead of relying on MCP to generate the app.

Tools preview

Seven read-only tools. No live search, rates, prebook, or book.

ToolWhat it does
list_endpointsSearch the local OpenAPI catalog by name, path, summary, or tag. Returns method, host, and path.
describe_endpointReturn the HTTP contract for one endpoint (URL, headers, parameters, body). Does not call the API.
search_docsSearch public pages on docs.liteapi.travel.
fetch_docs_pageRead one docs page as plain text by full https://docs.liteapi.travel/... URL.
fetch_documentationLoad a curated OpenAPI or docs overview by key (searchApi, bookingApi, hotelDataApi, loyaltyApi, voucherApi, analyticsApi, priceIndexApi, flightsIndexApi, mainDocs, overview).
search_dashboard_kbSearch Nuitee Connect product guides (dashboard UI: bookings, payments, Whitelabel, Direct Connections, …).
fetch_dashboard_featureRead one product guide by slug from search_dashboard_kb. Public guides only.

Connect your MCP client and call tools/list on https://mcp.liteapi.travel/api/knowledge to see the live schemas.

Setup

No key. Point the client at the knowledge URL.

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "nuitee-knowledge": {
      "url": "https://mcp.liteapi.travel/api/knowledge"
    }
  }
}

You can run both MCPs in the same client: knowledge for docs, MCP for AI Agents (with a key) for live API calls. Give them different names so the agent can tell them apart.

Try it

  1. Add the knowledge URL in your AI client.
  2. Ask: “What is Direct Connections in Nuitee Connect?” or “Describe POST /hotels/rates.”
  3. The agent should use search_dashboard_kb / fetch_dashboard_feature for product how-tos, and list_endpoints / describe_endpoint / fetch_documentation for API contracts.

If you need sample hotel rates or a real booking flow from the agent, switch to MCP for AI Agents with a sandbox or account key.


Did this page help you?