wheels-router轮子路线规划

What I do

I help you plan public transit trips anywhere in the world by connecting to the Wheels Router MCP server.

For Hong Kong trips, I use the Wheels Router API which provides:

• - Detailed routing with MTR, bus, tram, ferry, and walking
• Real-time schedules and accurate fares
• Platform information and exit details
• Interchange discounts (轉乘優惠) when available

For worldwide trips, I use the Transitous API which covers:

• - Major cities globally with transit data
• Basic routing with public transportation
• Walking directions and transfers

When to use me

Use this skill whenever you need to:

• - Plan a trip using public transportation
• Find the best route between two locations
• Check transit schedules and connections
• Get fare estimates for Hong Kong transit
• Search for locations before planning routes

Examples:

• - "How do I get from Yau Tong MTR to Hong Kong Airport?"
• "What's the best way to Central from Causeway Bay right now?"
• "Plan a trip from Tokyo Station to Shibuya"
• "Search for locations near Victoria Park"

How to connect

If you're using mcporter (clawdbot, etc.)

Follow your mcporter skill, if you don't have one follow below:
Add to config/mcporter.json:

CODEBLOCK0

Then call tools directly:
CODEBLOCK1

For other MCP clients

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
CODEBLOCK2

Cursor/Windsurf/VS Code (.cursor/mcp.json or similar):
CODEBLOCK3

Available tools

search_location

Search for places before planning trips. Always use this first if you don't have exact coordinates.

Parameters:

• - query (required): Place name or address (e.g., "Hong Kong Airport", "Yau Tong MTR Exit A2")
• INLINECODE5 (optional): Number of results (1-10, default 5)

Example:
CODEBLOCK4

Returns:

• - display_name: Full address
• INLINECODE7, lon: Coordinates for use in INLINECODE9
• INLINECODE10, class: Location category

plan_trip

Plan a transit route between two points.

Parameters:

• - origin (required): Starting point as "lat,lon" or INLINECODE15
• INLINECODE16 (required): Ending point as "lat,lon" or INLINECODE18
• INLINECODE19 (optional): ISO 8601 departure time (e.g., "2026-01-26T10:00:00+08:00")
• INLINECODE21 (optional): ISO 8601 arrival deadline
• INLINECODE22 (optional): Comma-separated modes like "mtr,bus,ferry" (only specify if needed)
• INLINECODE24 (optional): Limit number of route options (1-5)

Example:
CODEBLOCK5

Returns:

• - plans: Array of route options

Best practices

1. 1. Always search first: Use search_location to find coordinates before calling INLINECODE32
2. Use coordinates: Plan trips with lat,lon format for best results
3. Specify times: Include depart_at or arrive_by for accurate schedules
4. Check multiple options: Request 2-3 route options with INLINECODE36
5. Understand fares: fares_min and fares_max show the range—interchange discounts are noted separately when available

Important notes

• - Interchange discounts (轉乘優惠): Only shown when explicitly present in Hong Kong routes, not all routes qualify
• Real-time data: Hong Kong routes use live schedules; worldwide coverage may vary
• Time zones: Use UTC or local timezone offsets (HKT is UTC+8)
• Coverage: Best for Hong Kong; worldwide coverage varies by city

Example workflow

CODEBLOCK6

Error handling

• - "Could not find location": Try a more specific search query
• "No routes found": Check if coordinates are valid and in a covered area
• "Invalid time format": Ensure ISO 8601 format with timezone
• Rate limits: Be mindful of API usage, cache results when appropriate

Coverage areas

• - ✅ Full coverage: Hong Kong (MTR, bus, tram, ferry, detailed fares)
• ✅ Good coverage: Major global cities with Transitous data
• ⚠️ Limited coverage: Smaller cities may have incomplete transit data