This MCP server, LiteAPI, automatically generates MCP tools from the OpenAPI specs found in the openapi-schemas directory and exposes them as individual MCP tools. Each OpenAPI operation becomes a tool with a name derived from the operation ID, a description from the spec, and input parameters validated against the OpenAPI schema. The server runs via standard input/output (stdio) for MCP communication and is designed to integrate with clients like Claude Desktop or the MCP Inspector. Before use, ensure you have a LiteAPI API key set as an environment variable so requests to LiteAPI are authenticated. The common workflow is to start the server, then query the available tools and invoke them with the appropriate parameters. Tools are generated automatically, so the exact list will reflect the OpenAPI specs included in the repository, such as hotels search, bookings, vouchers, analytics, and loyalty APIs.

Prerequisites:

• Node.js 18+ (with npm or yarn)
• LiteAPI API key (for authentication)

Installation steps:

1. Clone the repository: git clone https://github.com/your-org/liteapi-travel-mcp-server.git
2. Navigate to the project folder: cd liteapi-travel-mcp-server
3. Install dependencies: npm install
4. Build the TypeScript source (if applicable): npm run build
5. Set your LiteAPI API key as an environment variable (example for Unix-like shells): export LITEAPI_API_KEY=your_api_key_here
6. Start the server: npm start

   For development with auto-reload:

   npm run dev

Quick verification:

• The MCP endpoint is typically available via stdio; you can also use tooling from Markdown examples to connect through the inspector or a simple client script.

Tips and notes:

• The server auto-generates tools from all OpenAPI specs in openapi-schemas/. The operation ID becomes the tool name, and inputs are derived from the spec schemas.
• Set LITEAPI_API_KEY in your environment to enable authenticated requests to LiteAPI endpoints.
• For development and debugging, use the MCP Inspector (recommended) to visualize tools, test calls, and view responses. Ensure Node.js version is 22.7.5+ if you’re using the inspector.
• If deploying to Claude Desktop, you may need to point Claude at run-mcp-server.mjs and provide an absolute path to your project in the Claude Desktop configuration.
• If you modify or add OpenAPI specs, re-build or re-run the server to reflect new tools.
• The server communicates via stdio; some environments may require explicit configuration to ensure stdout/stderr are routed correctly to your MCP client.