MyDriverParis MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WP_API_KEY | Yes | WordPress API key | |
| WP_API_URL | Yes | WordPress API URL | |
| ZEPLAN_API_KEY | Yes | Zeplan API key | |
| ZEPLAN_API_URL | Yes | Zeplan API URL | |
| STRIPE_SECRET_KEY | Yes | Stripe secret key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_vehiclesA | List all available vehicles with capacity and base rates. Use this to help the customer choose the right vehicle for their trip. |
| get_quoteA | Calculate the exact price for a private chauffeur transfer. Returns prices for all available vehicles. Always call this before book_ride to get an accurate quote. |
| book_rideA | Create a payment link to book a private chauffeur transfer. The customer will receive a Stripe Checkout URL to complete payment. Once paid, the booking is automatically created and a chauffeur is assigned. Always call get_quote first to get the correct price and vehicle_id. |
| get_service_infoA | Get information about MyDriverParis services, coverage areas, airports served, and policies. Use this to answer customer questions about what is included. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: listing vehicles, quoting prices, booking a ride, and providing service info. There is no functional overlap, making it easy for an agent to select the correct tool.
All tool names follow the verb_noun pattern with consistent get_ and book_ prefixes (get_vehicles, get_quote, book_ride, get_service_info). Naming is uniform and predictable.
Four tools is well-scoped for a chauffeur booking server. Each tool is necessary for the core workflow: discover vehicles, get pricing, book, and answer questions.
The booking workflow is complete (vehicles → quote → book), and service info covers typical questions. However, there are no tools for viewing managing existing bookings, which is a minor gap in the domain.