Lyft MCP. Estimate, Book, Track: Full Ride Cycle Management
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Lyft MCP Server manages your entire ride lifecycle via AI agents. You can check estimated costs and travel times between any two points, find available vehicle types (XL, Lux), book a ride using coordinates or saved locations, track active trips in real time, or pull detailed ride history for expense reports.
What your AI agents can do
Cancel ride
Cancels an existing Lyft ride request when plans change or the booking was wrong.
Get cost estimate
Calculates the estimated cost for a Lyft ride between two specific locations using local currency (USD).
Get eta estimate
Gets estimated arrival times to compare how quickly different Lyft services can reach you at a location.
You can check how much a ride will cost and compare ETAs across various Lyft product types using get_cost_estimate and get_eta_estimate.
The agent reads, saves, or updates favorite addresses (Home/Work) using set_location and retrieves them via get_locations, eliminating the need to type out full coordinates.
You can request a new ride using request_ride or cancel an existing one with cancel_ride through simple commands.
The system tracks active rides and reviews past trips. Use get_ride_details for live updates, or pull full reports using get_ride_history.
You can see exactly which ride classes (e.g., XL, Lux) are available at a specific location by calling get_ride_types.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Lyft MCP Server: 9 Tools for Ride & Trip Management
These tools let your AI client manage every aspect of a Lyft trip—from checking costs to booking and tracking history.
019d75cbcancel ride
Cancels an existing Lyft ride request when plans change or the booking was wrong.
019d75cbget cost estimate
Calculates the estimated cost for a Lyft ride between two specific locations using local currency (USD).
019d75cbget eta estimate
Gets estimated arrival times to compare how quickly different Lyft services can reach you at a location.
019d75cbget locations
Retrieves a list of saved location IDs, names, and coordinates associated with the account.
019d75cbget ride details
Fetches specific details about a single Lyft ride, whether it's currently active or completed.
019d75cbget ride history
Pulls the complete log of past rides, including dates, status, origin/destination, and final costs.
019d75cbget ride types
Lists all available Lyft ride options (like XL or Lux) at a specific latitude/longitude so you know what to book.
019d75cbrequest ride
Books a new Lyft trip using confirmed ride type ID, origin coordinates, and destination coordinates.
019d75cbset location
Saves or updates a preferred location (like 'Home' or 'Work') by assigning it a unique ID and coordinate set.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Lyft, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You're running on Lyft? Forget opening the app and tapping through menus—your agent handles your whole ride lifecycle just by talking to it. This server connects your AI client directly to the Lyft platform, letting you manage everything from estimating costs to tracking trips.
Managing Your Locations
It's simple: You never gotta punch in coordinates again. Use get_locations to pull a list of all the addresses—your saved IDs, names, and precise coordinates—that are already attached to your account. If you need to save or update a favorite spot like 'Work' or 'Home,' use set_location; it assigns that location a unique ID and coordinate set for future use.
Estimating Costs and Times
Before you commit, you gotta know the damage. Use get_cost_estimate to calculate exactly how much any given ride will cost between two locations, giving you the final price in local USD currency. To figure out timing, run get_eta_estimate; this lets you compare estimated arrival times to see which Lyft service gets you there fastest from your current spot.
You also need to know what's even available. Call get_ride_types at a specific latitude/longitude, and it spits out every ride class—like XL or Lux—that’s ready for booking right where you are.
Booking and Controlling Rides
When you're good to go, use request_ride. You just need the confirmed ride type ID, your origin coordinates, and your destination coordinates; it books the new Lyft trip straight up. If your plans change or you booked the wrong thing, don't sweat it. Use cancel_ride to cancel any existing Lyft ride request.
Tracking Status and History
Need an update on a ride that's already happening? Run get_ride_details. This pulls specific details about a single trip, whether it’s active right now or if it just finished up. For the bigger picture—like when you file expenses—use get_ride_history to pull the complete log of every ride.
This includes dates, status updates, where you started and ended, and the final cost for everything.
Basically, your agent orchestrates all this stuff: it reads your saved locations using get_locations, checks how much a trip costs with get_cost_estimate, sees what ride types are available via get_ride_types, and then you can book it with request_ride. If things go wrong, cancel_ride gets the job done. It's all about making sure your trip is monitored—you get live updates using get_ride_details or pull a full expense report by calling get_ride_history.
You've got total control over every stage of the ride process.
How Lyft MCP Works
- 1 Your agent first calls
get_locationsorset_locationto define your start and end points. - 2 Next, it runs preliminary checks: calling
get_cost_estimateandget_eta_estimateto confirm pricing and timing for the chosen route. - 3 Finally, the agent executes the transaction by calling
request_ride, which books the trip using the validated data.
The bottom line is: you tell your AI client what you need—a ride—and it runs the necessary sequence of tool calls (locations -> estimate -> book) for you, without needing manual app interaction.
Who Is Lyft MCP For?
Corporate expense managers and travel coordinators. If you spend more than five minutes a week manually booking rides or compiling receipts after trips, this is for you. This system handles the complex sequence of location management, price comparisons, and booking confirmations automatically.
Manages group bookings by checking get_cost_estimate across multiple routes to ensure the cheapest option is selected before calling request_ride for all attendees.
Uses get_ride_history to pull detailed, structured reports of past trips, making it easy to reconcile corporate expenses without opening separate receipts or apps.
Needs instant ETA comparisons. They call get_eta_estimate when planning a multi-stop route to pick the fastest mode of transport from a central hub.
What Changes When You Connect
- Stop guessing on costs. Use
get_cost_estimateto compare prices across all Lyft products (Lux vs. XL) before you hit the button. You know the expense upfront. - Time saved is real time. Calling
get_eta_estimatelets you compare pickup times for different services, ensuring your agent picks the absolute fastest option for your schedule. - Never type an address again. Use
set_locationandget_locationsto save 'Home' or a client office. Booking then only requires referencing a name, not coordinates. - Audit trails are simple. Instead of digging through emails, run
get_ride_historyonce to get structured data covering all past trips needed for expense reporting. - Real-time visibility means less anxiety.
get_ride_detailsgives you live tracking info—driver name, car model, and status updates as the ride progresses.
Real-World Use Cases
Planning a Multi-Stop Business Day
A coordinator needs to get from the office to Client A, then to the airport. Instead of running three separate searches, they ask their agent: 'Get me the cost and ETA for my whole day.' The agent calls get_cost_estimate and get_eta_estimate sequentially for each leg, presenting a total trip plan before confirming the final booking with request_ride.
Handling Last-Minute Changes
You're on your way to dinner but realize you have another meeting across town. You tell your agent: 'Cancel my current ride and check options for the new location.' The agent first calls cancel_ride then uses get_locations (to find the nearest alternative) followed by a new get_cost_estimate, solving the change instantly.
Reconciling Quarterly Expenses
It's time for expense reports. Instead of manually gathering receipts, you ask: 'Show me all my rides from last quarter.' The agent calls get_ride_history, providing a structured data dump that includes the ride date, type, and cost—ready to paste into an accounting spreadsheet.
Setting Up New Office Locations
Your company opens a new satellite office. Instead of giving coordinates every time, you ask your agent: 'Save this address as the main branch.' The agent executes set_location, creating a permanent record that future booking requests can reference by name.
The Tradeoffs
Booking before checking prices
Telling your agent, 'Book me a Lyft XL to the airport.' The agent books it without knowing if there's a cheaper or faster option available that day.
→
Always check first. Ask: 'What is the cost and ETA from my current location to JFK?' This triggers get_cost_estimate and get_eta_estimate. Once you approve, then ask it to execute the booking using request_ride.
Assuming a saved address works
Telling your agent, 'Just use my work address.' If the underlying location ID is outdated or malformed, the ride request will fail with ambiguous coordinates.
→
Before booking, run get_locations to verify that the correct Location ID exists and is active. Then, pass those validated IDs into the request.
Using vague requests
Simply saying 'Get me a ride.' The agent doesn't know if you want XL, Lux, or basic, leading to an error because no specific ride type ID was selected.
→
First, call get_ride_types at the pickup location. This lists all available options (IDs and names), letting your agent narrow down exactly which service class (get_ride_types) you want before calling request_ride.
When It Fits, When It Doesn't
Use this server if your workflow requires complex, multi-step transportation management. Specifically: If you need to compare costs OR ETAs across different ride types; if you handle corporate expense reports; or if you regularly save and reference recurring addresses (Home/Work).
Don't use it if:
1. You are simply telling a friend where you are going—the native app is faster.
2. Your only goal is to get an address from Google Maps. Use get_locations for that, but don't expect it to be the end point.
3. You need highly granular navigation instructions (e.g., 'Turn left at the third light'). The agent handles logistics and booking; the map app handles driving directions.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Lyft. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 9 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Booking a ride shouldn't involve 5 different screens and half a dozen clicks.
Right now, planning a trip means opening the Lyft app, typing in coordinates (which you might misspell), selecting a car type, hitting 'Estimate,' checking the price against your budget, then canceling it to check another service class. It's tedious context switching.
With this MCP server, you just tell your agent: 'Book me an XL ride from my work address to JFK.' The agent handles finding your saved location via `get_locations`, running a cost check with `get_cost_estimate` (and checking the fastest ETA), and finally executing the booking—all in one command.
Lyft MCP Server: Manage ride requests, costs, and history.
You no longer have to manually gather receipts or cross-reference different apps. Running `get_ride_history` compiles everything into one readable output that includes the date, route details, and final cost.
This is about control. You get structured data for every trip taken, making expense reporting painless. It's not just booking; it's building a complete travel log.
Common Questions About Lyft MCP
How do I check if XL rides are available using the Lyft MCP Server? +
You call get_ride_types with your current location coordinates. This tool returns a list of all valid ride type IDs (like 'XL') and tells you if they're currently offered at that spot.
Can I use the Lyft MCP Server to check prices before booking? +
Yes, absolutely. Use get_cost_estimate by providing two coordinates (origin/destination). This gives you a real-time price comparison without actually reserving the ride.
What if I need to change my destination mid-trip? +
You first call cancel_ride. Then, use get_locations or manually provide the new coordinates and run get_cost_estimate for the updated route before calling request_ride again.
Does get_ride_history include pricing details? +
Yes. The history report pulled by get_ride_history includes the date, status, origin/destination, and the final cost for every past trip.
When does the `cancel_ride` tool process a cancellation fee? +
Fees depend entirely on the ride's status. If a driver has already been assigned, you may incur charges. You should always confirm Lyft’s current policies before using this tool for cancellations.
What format does the `set_location` tool accept when saving spots? +
It requires a location ID, plus precise latitude and longitude coordinates. You can optionally add a display name to help your agent reference it later without typing out full addresses.
How do I determine the fastest pickup option before running `request_ride`? +
Run get_eta_estimate for several ride types first. This returns estimated arrival times, allowing you to compare service speed without having to commit to a booking.
Does the `get_locations` tool require me to use a specific client ID? +
No, it pulls saved locations linked to your authenticated Lyft account. It provides location IDs, names, and coordinates so you can reference them for other tools like request_ride.
Can I actually book rides through this MCP server? +
Yes! Unlike some ride-sharing MCPs that only provide estimates, this server can create actual ride requests via the Lyft API. You can book rides, check status, track driver details, and even cancel — all through AI agent commands. A valid Lyft account with payment method on file is required.
What Lyft API permissions do I need? +
You need Client ID and Client Secret from the Lyft Developer Portal with 'Public' or 'Full' access scopes. The client credentials flow (2-legged OAuth) provides access to ride types, cost estimates, ETA estimates, ride requests, and history. For user-specific data, additional scope approval may be needed.
Does this work in all cities where Lyft operates? +
Yes, this MCP server works in all cities served by Lyft, primarily across the United States and select Canadian cities. Ride availability depends on your local Lyft service area. The API will return accurate ride types, pricing, and ETAs for any location where Lyft operates.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Netease Yunxin IM
Equip your AI Agent with Netease Yunxin to massively manage Live Chat Rooms, moderate IM participants, and broadcast messages.
SEON
Prevent online fraud with device fingerprinting, email and phone analysis, and real-time risk scoring for digital transactions.
Zoho Billing Alternative
Automate your subscription management with Zoho Billing — manage organizations, products, and plans directly from your AI agent.
You might also like
Sobot
Leading AI customer support and ticketing platform in China — manage tickets, agents, and knowledge via AI.
GDACS
Monitor global disaster alerts — earthquakes, cyclones, floods, volcanoes, wildfires and droughts with real-time impact estimates.
Amplemarket
Supercharge your outbound sales with AI-driven prospecting, multi-channel sequences, and smart lead scoring that closes deals.