Bring Ride Sharing
to Cline
Learn how to connect Lyft to Cline and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
What is the Lyft MCP Server?
What you can do
Connect AI agents to the Lyft platform for complete ride automation:
- Get available ride types (Lyft, XL, Lux) at any location
- Estimate ride costs across all products before booking
- Compare pickup ETAs to choose the fastest option
- Request rides directly with origin and destination coordinates
- Track active rides with driver info, vehicle details, and real-time status
- Cancel rides when plans change
- View complete ride history with pricing and route data
- Save favorite locations (Home, Work, custom places)
How it works
1. Connect your Lyft account via Client ID and Secret from Lyft Developer Portal
2. Ask your AI agent to estimate rides, book trips, or check history
3. No app navigation needed — natural language commands execute all operations
4. Automatic OAuth — the MCP handles token generation using client credentials flow
Who is this for?
Perfect for frequent travelers, urban commuters, executive assistants, travel coordinators, and corporate teams managing business transportation. Let AI agents handle ride booking, expense tracking via ride history, and location management. Ideal for professionals taking 10+ Lyft rides monthly who want streamlined booking workflows, instant price comparisons, and automated ride tracking.
Built-in capabilities (9)
Cancellation policies vary based on ride status - cancellations after driver assignment may incur fees. Use this to cancel rides that were booked by mistake or are no longer needed. Cancel an existing Lyft ride request
Prices are in local currency (USD). Use this to compare costs across different Lyft products before booking. Get cost estimate for a Lyft ride between two locations
Use this to compare how quickly different Lyft services can reach you. Lower minutes mean faster pickups. Get estimated arrival times for Lyft at a location
Returns location IDs, names, addresses, and coordinates. Use this to quickly reference saved locations for ride requests without typing full addresses. Get saved locations for the Lyft account
Use this to track your active ride or review past ride details. Get details of a specific Lyft ride
Returns ride date, status, origin/destination, ride type, driver, and cost. Use this to review past rides, calculate expenses, or find previous trip details. Get ride history for the authenticated Lyft account
) available at the specified latitude/longitude. Returns ride type IDs, display names, capacity, and descriptions. Use this to see which ride options are available before requesting price or time estimates. Get available Lyft ride types at a location
Requires ride type ID (from get_ride_types), origin coordinates, and destination coordinates. Optionally include pickup/dropoff addresses for clarity. Returns the ride ID and status. Use this to book a ride after confirming price and availability. Request a new Lyft ride
Requires location ID, latitude, and longitude. Optionally include a display name. The location ID can be home, work, or any custom string. Returns the saved location details. Use this to manage your favorite pickup/dropoff spots. Save or update a location for the Lyft account
Why Cline?
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Lyft tool calls without waiting for prompts between steps. Connect 9 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
- —
Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
- —
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
- —
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
- —
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
Lyft in Cline
Lyft and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Lyft to Cline through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Lyft in Cline
The Lyft MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 9 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cline only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Lyft for Cline
Every tool call from Cline to the Lyft MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
How does Cline connect to MCP servers?
Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
Can Cline run MCP tools without approval?
By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
Does Cline support multiple MCP servers at once?
Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.
Server shows error in sidebar
Click the server name to see logs. Verify the URL and token are correct.