Docs MCP
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 Full MCP 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
| Docs MCP | Full MCP | |
|---|---|---|
| URL | https://mcp.liteapi.travel/api/knowledge | https://mcp.liteapi.travel/api/mcp |
| Auth | None | API key or OAuth |
| Docs, OpenAPI catalog, product guides | Yes | Yes |
| Live search / rates / book tools | No | Yes |
| Best for | Learning the product, grounding answers, least privilege | Agents 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.
What the agent can do
Seven tools only:
list_endpoints— search the local OpenAPI catalog (method, path, summary)describe_endpoint— full HTTP contract for one operation (no live call)search_docs— search pages on docs.liteapi.travelfetch_docs_page— read one docs page by URLfetch_documentation— load a curated OpenAPI or docs overview by key (searchApi,bookingApi,flightsIndexApi, …)search_dashboard_kb— search Nuitee Connect product guides (dashboard UI: bookings, payments, Whitelabel, Direct Connections, …)fetch_dashboard_feature— read one product guide by slug
Public dashboard guides only. Internal staff notes are not exposed.
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"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"nuitee-knowledge": {
"url": "https://mcp.liteapi.travel/api/knowledge"
}
}
}Add to claude_desktop_config.json:
{
"mcpServers": {
"nuitee-knowledge": {
"type": "http",
"url": "https://mcp.liteapi.travel/api/knowledge"
}
}
}You can run both MCPs in the same client: knowledge for docs, full MCP (with a key) for live API calls. Give them different names so the agent can tell them apart.
Try it
- Add the knowledge URL in your AI client.
- Ask: “What is Direct Connections in Nuitee Connect?” or “Describe
POST /hotels/rates.” - The agent should use
search_dashboard_kb/fetch_dashboard_featurefor product how-tos, andlist_endpoints/describe_endpoint/fetch_documentationfor API contracts.
If you need sample hotel rates or a real booking flow from the agent, switch to Full MCP with a sandbox or account key.
Updated about 3 hours ago

