LiteAPI MCP Server

MCP设计创作

提供方 liteapi-travel

设计创作 未标注 会话登录 社区 / 第三方 ClaudeCursorCodexZed
查看接入方式

LiteAPI MCP Server Run just the server for development ` npm run dev ` Run server and inspector ` npm run inspect ` Configure with Claude `json { "mcpServers": { "liteapi": { "command": "/Users/YOUR_USER/.nvm/versions/node/v18.18.2/bin/node", "cwd": "/Users/YOUR_USER/mcp-server", "args": [ "/Users/YOUR_USER/mcp-server/dist/index.js" ] } } } `

一句话选型结论

按资料字段整理

LiteAPI MCP Server 属于设计创作类 MCP 服务器,传输方式未标注,会话登录,可直接接入 Claude、Cursor、Codex 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类设计创作 传输方式未标注 鉴权会话登录 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

设计创作
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

mcp serverdevelopment

安装与配置

未标注 会话登录
上游未给出传输方式
/Users/YOUR_USER/.nvm/versions/node/v18.18.2/bin/node /Users/YOUR_USER/mcp-server/dist/index.js

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
出图与素材

生成配图、图标与素材。

设计稿处理

读取设计稿、批量改尺寸或导出。

内容生成

按主题生成文案与视觉草稿。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、Codex,换客户端不用重新研究配置。

先想清楚的地方

  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在设计创作场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
LiteAPI MCP Server当前 未标注 未标注 未标注 有 未标注
Cursor Talk To Figma MCP Da1c7911 40 未标注 未标注 无 2026-05-17
Blender MCP 17 stdio · 本地进程 本地部署 有 2026-05-18
Nova Canvas MCP Server 2 stdio · 本地进程 本地部署 有 2026-05-17
Figma Context MCP 3aaa8d28 未标注 未标注 支持远程部署 无 2026-05-17
kreuzberg 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

设计创作
字段来自项目仓库与公开索引,中文说明由本站标注
提供方liteapi-travel上游标注的维护方 liteapi-travel
分类设计创作本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · node本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

8.9 KB
来自项目仓库与上游目录的原文,未做删改

LiteAPI MCP Server

MCP server for LiteAPI using Next.js and mcp-handler (Streamable HTTP). Deploys to Vercel.

Quick Start```bash

npm install
npm run dev


MCP endpoint: `http://localhost:3000/api/mcp`

## ChatGPT Setup

Add to ChatGPT MCP Server URL:```
https://mcp.liteapi.travel/api/mcp?apiKey=YOUR_LITEAPI_KEY

Or set LITEAPI_API_KEY in Vercel environment variables for single-tenant deployment.


Features

  • 🔄 Dynamic Tool Generation: Automatically generates MCP tools from OpenAPI specs
  • 📚 Multiple API Modules: Supports Search, Booking, Vouchers, Analytics, Static, Loyalty, and Supply Customization APIs
  • 🔐 API Key Authentication: Secure API key management via environment variables
  • 🎯 Type-Safe: Uses Zod for schema validation and type safety
  • 🚀 Easy Integration: Works with Claude Desktop and other MCP-compatible clients

Prerequisites

  • Node.js 18+
  • npm or yarn
  • LiteAPI API Key

Installation

  1. Clone the repository and install dependencies:```bash
    npm install

2. Build the TypeScript code:```bash
npm run build
  1. Set your LiteAPI API key as an environment variable:```bash
    export LITEAPI_API_KEY=your_api_key_here

## Usage

### Running the Server

The server runs on stdio (standard input/output) for MCP communication:```bash
npm start

Or for development with auto-reload:```bash
npm run dev


## Testing

### Quick Test

Test that the server works correctly:```bash
export LITEAPI_API_KEY=your_api_key_here
npm test

This will connect to the server and list all available tools.

Option 1: Using MCP Inspector (Recommended for Development)

MCP Inspector is a browser-based tool for testing and debugging MCP servers. It's perfect for inspecting tools, testing calls, and debugging without needing Claude Desktop.

  1. Install and run MCP Inspector:```bash

Make sure your API key is set

export LITEAPI_API_KEY=your_api_key_here

Run the inspector (it will automatically start your server)

npm run inspect

Or directly:

npx @modelcontextprotocol/inspector node dist/index.js


2. **The inspector will:**
   - Open a browser window at `http://localhost:6274`
   - Start a proxy server on port 6277
   - Display all available tools with their schemas
   - Allow you to test tool calls interactively
   - Show real-time notifications and responses

3. **In the Inspector UI, you can:**
   - **Tools Tab**: See all available tools, their descriptions, and input schemas
   - **Test Tools**: Click on any tool to test it with sample parameters
   - **View Responses**: See formatted JSON responses from API calls
   - **Debug**: Check for errors and validation issues

**Note:** Make sure Node.js 22.7.5+ is installed for MCP Inspector (check with `node --version`).

### Option 2: Testing with a Simple Client Script

Create a test script to verify the server works:```bash
# Create test-client.js
cat > test-client.js << 'EOF'
import { Client } from '@modelcontextprotocol/sdk/client/index.js';
import { StdioClientTransport } from '@modelcontextprotocol/sdk/client/stdio.js';

async function test() {
  const transport = new StdioClientTransport({
    command: 'node',
    args: ['dist/index.js'],
    env: { LITEAPI_API_KEY: process.env.LITEAPI_API_KEY }
  });

  const client = new Client({
    name: 'test-client',
    version: '1.0.0'
  }, {
    capabilities: {}
  });

  await client.connect(transport);

  // List all available tools
  const tools = await client.listTools();
  console.log(`Found ${tools.tools.length} tools:`);
  tools.tools.forEach(tool => {
    console.log(`  - ${tool.name}: ${tool.description}`);
  });

  await client.close();
}

test().catch(console.error);
EOF

# Run the test
export LITEAPI_API_KEY=your_api_key_here
node test-client.js

Option 3: Connecting to Claude Desktop

  1. Get the absolute path to your project:```bash

macOS/Linux

pwd

Output: /Users/nicholas/Documents/nuitee/liteapi/mcp-server

Windows (PowerShell)

(Get-Location).Path


2. **Open Claude Desktop configuration file:**
   - **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
   - **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
   - **Linux**: `~/.config/Claude/claude_desktop_config.json`

   If the file doesn't exist, create it with an empty JSON object: `{}`

3. **Add the server configuration:**```json
{
  "mcpServers": {
    "liteapi": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-server/run-mcp-server.mjs"],
      "env": {
        "LITEAPI_API_KEY": "your_api_key_here"
      }
    }
  }
}

Important:
- Use run-mcp-server.mjs instead of dist/index.js to ensure ES modules work correctly
- Replace /absolute/path/to/mcp-server with the actual absolute path to this project
- Replace your_api_key_here with your actual LiteAPI API key
- On Windows, use forward slashes / or escaped backslashes \\ in the path

Example for macOS:```json
{
"mcpServers": {
"liteapi": {
"command": "node",
"args": ["/Users/nicholas/Documents/nuitee/liteapi/mcp-server/run-mcp-server.mjs"],
"env": {
"LITEAPI_API_KEY": "sand_c0155ab8-c683-4f26-8f94-b5e92c5797b9"
}
}
}
}


**Note:** The `.mjs` wrapper script ensures Node.js correctly recognizes ES modules when running from Claude Desktop. If you prefer to use `dist/index.js` directly, make sure Claude Desktop runs it from the project root directory.

4. **Restart Claude Desktop** completely (quit and reopen)

5. **Verify connection:**
   - Open Claude Desktop
   - Start a new conversation
   - Look for MCP tools indicator (usually shows available tools)
   - Try asking: "What LiteAPI tools are available?" or "Search for hotels in Paris"

### Troubleshooting Connection Issues

**If Claude Desktop doesn't recognize the server:**

1. **Check the path is correct:**```bash
   # Test that the file exists and is executable
   ls -la /absolute/path/to/mcp-server/dist/index.js
   node /absolute/path/to/mcp-server/dist/index.js
   ```

2. **Check Claude Desktop logs:**
   - macOS: `~/Library/Logs/Claude/claude_desktop.log`
   - Windows: `%APPDATA%\Claude\logs\`
   - Look for errors related to MCP server startup

3. **Verify JSON syntax:**```bash
   # Validate JSON syntax
   cat ~/Library/Application\ Support/Claude/claude_desktop_config.json | python3 -m json.tool
   ```

4. **Test server manually:**```bash
   export LITEAPI_API_KEY=your_api_key_here
   node dist/index.js
   # Should output: "Loaded X endpoints from Y OpenAPI specs"
   # Should output: "LiteAPI MCP Server running on stdio"
   ```

5. **Check Node.js version:**```bash
   node --version
   # Should be 18.0.0 or higher
   ```

### Available Tools

The server automatically generates tools from all OpenAPI specs in the `openapi-schemas/` directory. Each endpoint becomes a callable MCP tool with:

- **Operation ID** as the tool name
- **Description** from the OpenAPI spec
- **Parameters** automatically extracted and validated

Example tools include:
- `post_hotels_rates` - Search for hotel rates
- `get_prebooks_{prebookId}` - Retrieve prebook details
- `post_bookings` - Create a booking
- And many more...

## Project Structure```
.
├── src/
│   ├── index.ts              # Entry point
│   ├── server.ts              # Main MCP server implementation
│   └── utils/
│       ├── openapi-parser.ts  # OpenAPI spec parsing
│       ├── schema-converter.ts # OpenAPI to Zod conversion
│       └── api-client.ts      # HTTP client for API calls
├── openapi-schemas/           # OpenAPI specification files
├── dist/                      # Compiled JavaScript (generated)
├── package.json
├── tsconfig.json
└── README.md

Development

Building```bash

npm run build


### Watching for Changes```bash
npm run watch

Adding New OpenAPI Specs

  1. Add your OpenAPI spec JSON file to openapi-schemas/
  2. Update the specFiles array in src/utils/openapi-parser.ts if needed
  3. Rebuild and restart the server

Environment Variables

  • LITEAPI_API_KEY (required): Your LiteAPI API key for authentication

API Modules

The server supports the following LiteAPI modules:

  • Search (search.json) - Hotel search and rate retrieval
  • Booking (booking.json) - Booking management and prebook operations
  • Vouchers (voucher.json) - Voucher creation and management
  • Analytics (analytics.json) - Analytics and reporting
  • Static (static.json) - Static data endpoints
  • Loyalty (loyalty.json) - Loyalty program operations
  • Supply Customization (supplyCustomization.json) - Supply customization

Error Handling

The server includes comprehensive error handling:
- Missing API keys are caught at startup
- Invalid tool calls return descriptive error messages
- API request failures are properly formatted and returned

License

MIT

Support

For issues related to:
- MCP Server: Open an issue in this repository
- LiteAPI: Contact LiteAPI support

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
LiteAPI MCP Server 怎么安装?

在客户端按下面的安装命令接入:/Users/YOUR_USER/.nvm/versions/node/v18.18.2/bin/node /Users/YOUR_USER/mcp-server/dist/index.js。装完在客户端配置里引用同一个包或端点。

LiteAPI MCP Server 怎么在 Claude、Cursor、Codex 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

LiteAPI MCP Server 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

LiteAPI MCP Server 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

LiteAPI MCP Server 支持哪些客户端?

资料标注支持 Claude、Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

LiteAPI MCP Server 能提供哪些能力?

资料显示能力标签包括 mcp server、development。具体工具清单以官方文档为准。

LiteAPI MCP Server 需要什么运行环境?

运行时为 node。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。