SC-MCP-SERVER

SC-MCP-SERVER

MCP server for AI agents to execute the complete NevioServiceCenter flight booking flow. It provides 10 tools for flight search, cart management, passenger details, seat selection, ancillaries, and booking confirmation with automatic JWT token management.

Category
访问服务器

README

SC-MCP-SERVER — Create Booking Agent

MCP server for AI agents to execute the complete NevioServiceCenter flight booking flow. Provides 10 tools against the live APIM gateway with automatic JWT token management.


Quick Start

cd SC-MCP-SERVER
pip install -r requirements.txt
python check.py          # verify all 18 checks pass
python server.py         # start in stdio mode

Architecture

┌─────────────────────────────────────────────────────────┐
│                    AI Assistant                          │
│            (Claude / Copilot / Custom Agent)             │
└──────────────────────┬──────────────────────────────────┘
                       │ MCP Protocol (stdio / SSE)
                       ▼
┌─────────────────────────────────────────────────────────┐
│                  SC-MCP-SERVER v2.0                      │
│                                                         │
│  ┌──────────────────────────────────────────────────┐   │
│  │           10 Booking Agent Tools                  │   │
│  │    + 1 Prompt (booking_flow guide)                │   │
│  └──────────────────────┬───────────────────────────┘   │
│                         │                                │
│                  ┌──────┴───────┐                        │
│                  │ APIM Client  │                        │
│                  │ + Token Mgr  │                        │
│                  └──────┬───────┘                        │
└─────────────────────────┼────────────────────────────────┘
                          │ HTTPS + JWT
                          ▼
            ┌──────────────────────────┐
            │  APIM Gateway            │
            │  (Azure API Management)  │
            │                          │
            │  /token                  │
            │  /shop/flights           │
            │  /create-cart            │
            │  /checkout/passengers    │
            │  /services               │
            │  /seatmap                │
            │  /seat/services          │
            │  /cart/retrieve          │
            │  /checkoutConfirm        │
            │  /orders/retrieve        │
            └──────────────────────────┘

Booking Flow (10 Tools)

Token management is automatic — the server fetches, caches (~28 min), and refreshes JWT tokens transparently.

Flow Sequence

SearchFlights → CreateCart → UpdatePassengers → [GetServiceCatalog] → [GetSeatMap]
     │               │              │                   │                   │
  SKU IDs      checkoutId    passenger IDs         service SKUs        seat grid
                    │              │                   │                   │
                    └──────────────┴───────────────────┴───────────────────┘
                                          │
                              [AddAncillaries] / [AddSeats]
                                          │
                                    RetrieveCart
                                          │
                                    ConfirmBooking
                                          │
                                     orderId / PNR
                                          │
                                    RetrieveOrder

Steps in [ ] are optional.

Tool Reference

# Tool Endpoint Purpose
1 search_flights /shop/flights Search flight offers
2 create_cart /create-cart Create booking cart from SKU IDs
3 update_passengers /checkout/passengers Add passenger identity & contact
4 get_service_catalog /services Browse ancillary services
5 get_seat_map /seatmap View seat availability
6 add_seats /seat/services Assign seats
7 add_ancillaries /seat/services Add bags, meals, wifi
8 retrieve_cart /cart/retrieve Review cart before confirm
9 confirm_booking /checkoutConfirm Create order (PNR) — irreversible
10 retrieve_order /orders/retrieve Fetch confirmed order

Rules

  • Thread checkoutId from step 2 through steps 3–9
  • Always call retrieve_cart before confirm_booking
  • confirm_booking is irreversible — confirm with user first
  • At least one passenger must have contactDetails (email + mobile)
  • Dates use YYYY-MM-DD format

1. search_flights

Parameter Type Required Description
trip_type string Yes OW, RT, or MC
departure_location string Yes IATA code (e.g. HEL)
arrival_location string Yes IATA code (e.g. JFK)
departure_date string Yes YYYY-MM-DD
passengers list Yes [{"passengerTypeCode": "ADT", "discountCode": "ADT"}]
fare_type string No Economy (default), Business, First
return_date string No Required for RT trips

2. create_cart

Parameter Type Required Description
sku_ids list[str] Yes SKU IDs from search results
airline_id string No Default AY
agent_id string No Default MCP-Agent

Key outputs: checkoutId (steps 3–9), passengers[].passengerId (step 3), connections[].flights[].id (step 5)

3. update_passengers

Parameter Type Required Description
checkout_id string Yes From create_cart
passengers list[dict] Yes Identity + contact details

4. get_service_catalog

Parameter Type Required Description
checkout_id string Yes From create_cart
promotion_code string No e.g. SCUISEATP

5. get_seat_map

Parameter Type Required Description
checkout_id string Yes From create_cart
flight_id string Yes Flight segment ID from create_cart
promotion_code string No e.g. SCUISEATP

6. add_seats

Parameter Type Required Description
checkout_id string Yes From create_cart
traveller list[dict] Yes [{id, seat: [{flightId, seat, bundleId?}]}]

7. add_ancillaries

Parameter Type Required Description
checkout_id string Yes From create_cart
traveller list[dict] Yes [{id, services: [{id, quantity}]}]

8. retrieve_cart

Parameter Type Required Description
checkout_id string Yes From create_cart

9. confirm_booking

Parameter Type Required Description
checkout_id string Yes From create_cart

10. retrieve_order

Parameter Type Required Description
order_id string Yes From confirm_booking (e.g. 8LUTXS)

Configuration

Variable Default Description
APIM_BASE_URL https://nevioservicecenterapim.azure-api.net APIM gateway URL
APIM_TOKEN_TTL 1700 JWT token cache TTL in seconds
MCP_TRANSPORT stdio Transport: stdio or sse
MCP_PORT 3100 HTTP port (SSE mode)
MCP_HOST 127.0.0.1 HTTP host (SSE mode)
MCP_API_KEY (empty) Bearer token for HTTP auth
API_REQUEST_TIMEOUT 30 HTTP request timeout in seconds

Connection Guides

Claude Desktop

{
  "mcpServers": {
    "sc-booking-agent": {
      "command": "python",
      "args": ["C:/path/to/SC-MCP-SERVER/server.py"]
    }
  }
}

GitHub Copilot (VS Code)

Add to .vscode/mcp.json:

{
  "servers": {
    "sc-booking-agent": {
      "command": "python",
      "args": ["C:/path/to/SC-MCP-SERVER/server.py"]
    }
  }
}

HTTP/SSE

python server.py --transport sse --port 3100
{
  "mcpServers": {
    "sc-booking-agent": {
      "url": "http://localhost:3100/sse"
    }
  }
}

REST API (SSE mode)

# List tools
curl http://localhost:3100/api/tools

# Call a tool
curl -X POST http://localhost:3100/api/tools/search_flights \
  -H "Content-Type: application/json" \
  -d '{"trip_type":"OW","departure_location":"HEL","arrival_location":"JFK","departure_date":"2026-07-24","passengers":[{"passengerTypeCode":"ADT","discountCode":"ADT"}]}'

Project Structure

SC-MCP-SERVER/
├── server.py              # Entry point — 10 tools, 1 prompt, SSE/stdio
├── config.py              # APIM + transport configuration
├── check.py               # Readiness check (18 checks)
├── requirements.txt       # Python dependencies
├── README.md              # This file
└── src/
    └── tools/
    │   └── booking_tools.py   # 10 booking tool implementations
    └── utils/
        ├── apim_client.py     # APIM HTTP client with auto JWT auth
        └── token_manager.py   # JWT token fetch, cache, refresh

Token Management

  1. First API call → TokenManager calls POST {APIM_BASE_URL}/token
  2. JWT extracted from AuthToken cookie (fallback: response body, Set-Cookie header)
  3. Cached for APIM_TOKEN_TTL seconds (default ~28 min)
  4. Auto-refreshes on expiry
  5. On HTTP 401, invalidates token and retries once with a fresh token

No manual token handling needed.


Dependencies

Package Purpose
mcp>=1.0.0 Model Context Protocol framework
httpx>=0.27.0 HTTP client for APIM calls
uvicorn[standard]>=0.30.0 ASGI server (SSE transport)

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选