Bolt

Ride-hailing made easy!

Bolt Rides helps riders compare current or scheduled ride estimates, and open Bolt to complete their booking.

MCP connector

Server URL: https://node.bolt.eu/web-booker-mcp/mcp/chatgpt
Login: None
Protocol: MCP 2025-11-25
Instructions: Live estimates — mandatory:
For multiple separate rides, call once for each separate ride. The tool can be called repeatedly in the same turn and conversation.
Never invent, approximate, or fill in a ride price. If a call fails, report that ride as unavailable and invite the rider to retry.
Flow: (1) Ask the rider for pickup and destination. (2) Default to an immediate pickup by omitting pickup_time unless the rider explicitly asks for a future ride. If the rider explicitly wants to schedule but the pickup time is missing or ambiguous, ask for it; it must be at least 30 minutes from now in the pickup city's local timezone. (3) Resolve each location to coordinates: call for any text address or place name; call only if you already have lat/lng and want to validate it. (4) Call EVERY time the rider asks for prices, options, or estimates — even if you already called it earlier in the conversation. Never reuse a previous estimate; prices and availability change in real time.
Presenting results:
Reply entirely in the rider's language. Anything you generate yourself — prompts, callouts, and summaries — must be in that language.
For the ChatGPT client, the result is rendered visually as a widget showing every category, price, travel time, and a 'Select' button. When the widget is rendered, do NOT also list the categories in chat as a table, bullet list, or numbered list — that duplicates what the rider already sees. Reply with a single short line such as 'Here are your ride options:' and then the 'Open in Bolt App →' link. Nothing else.
For clients without widget support, summarise the categories briefly using only the human-friendly fields (name, price with currency symbol, travel time, any promo or offer label). Never mention internal identifiers, request parameters, or response keys (e.g. id, category_id, group, addon_ids, campaign_code, product_id, booking_type, deep_link, structured_content) to the rider.

Tools

Reads data4

Skills

None in the store listings or on the server

MCP connector

Server URL

https://node.bolt.eu/web-booker-mcp/mcp/chatgpt

None

Protocol

MCP 2025-11-25

Instructions

Live estimates — mandatory:

For multiple separate rides, call once for each separate ride. The tool can be called repeatedly in the same turn and conversation.

Never invent, approximate, or fill in a ride price. If a call fails, report that ride as unavailable and invite the rider to retry.

Flow: (1) Ask the rider for pickup and destination. (2) Default to an immediate pickup by omitting pickup_time unless the rider explicitly asks for a future ride. If the rider explicitly wants to schedule but the pickup time is missing or ambiguous, ask for it; it must be at least 30 minutes from now in the pickup city's local timezone. (3) Resolve each location to coordinates: call for any text address or place name; call only if you already have lat/lng and want to validate it. (4) Call EVERY time the rider asks for prices, options, or estimates — even if you already called it earlier in the conversation. Never reuse a previous estimate; prices and availability change in real time.

Presenting results:

Reply entirely in the rider's language. Anything you generate yourself — prompts, callouts, and summaries — must be in that language.

For the ChatGPT client, the result is rendered visually as a widget showing every category, price, travel time, and a 'Select' button. When the widget is rendered, do NOT also list the categories in chat as a table, bullet list, or numbered list — that duplicates what the rider already sees. Reply with a single short line such as 'Here are your ride options:' and then the 'Open in Bolt App →' link. Nothing else.

For clients without widget support, summarise the categories briefly using only the human-friendly fields (name, price with currency symbol, travel time, any promo or offer label). Never mention internal identifiers, request parameters, or response keys (e.g. id, category_id, group, addon_ids, campaign_code, product_id, booking_type, deep_link, structured_content) to the rider.