
Train Tickets
Trains in China through the 12306 MCP server: routes, dates, options, connections and...
Install
npx skills add nano-muse/nanoMuse --skill train-tickets -g -a claude-code -y- Repository
- nano-muse/nanoMuse3k
- Category
- AI and agents
- Updated
- 3d ago
- License
- GPL-3.0
- Context cost
- Lightabout 1,276 tokens
- Runs scripts
- No, instructions only
What it does
Trains in China through the 12306 MCP server: routes, dates, options, connections and stops with no screen; booking only on the user's word, in the 12306 app on their phone, stopping before payment. Use when the user asks about 火车票 / 高铁 / 12306 or a train between two cities.
Train tickets (12306)
Two hands, in this order. Searching is done with the 12306__* tools, a community MCP server (12306-mcp) that reads 12306's public timetable and seat counts; no login, no browser, no phone, nothing typed into an app. Booking has no API a personal agent may use; it happens on the phone's screen with phone_task, and only when the user has picked a train and said to book it.
Is the server there?
Look for 12306__get-tickets in your tools (the tools list is the only place it can be: no shell command or script to check). If it is not there, say so in one line, give the user the lines to add to config.toml, and, when a phone is connected, offer the search on the phone's screen instead (the old way, below); otherwise stop:
[[mcp.servers]]
name = "12306"
command = "npx"
args = ["-y", "12306-mcp"]
risk = "safe"
egress = true
Node is needed for npx; the phone's own runtime has it.
What you need
- From, to, the date, and whether it must be 高铁/动车 (G/D) or any train. The user's habits from
recall(preferred stations, morning or evening, seat class, who travels) count as answers. Ask for the rest with oneask_usercall. - Passengers, seat class and budget only matter for booking; do not ask for them to run a search.

