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.

Lyft MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: Lyft
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to Lyft through Vinkius, pass the Edge URL in the `mcps` parameter and every Lyft tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Lyft Specialist",
    goal="Help users interact with Lyft effectively",
    backstory=(
        "You are an expert at leveraging Lyft tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Lyft "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 9 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Lyft MCP Server

What you can do

Connect AI agents to the Lyft platform for complete ride automation:

When paired with CrewAI, Lyft becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Lyft tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

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)

The Lyft MCP Server exposes 9 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Lyft to CrewAI via MCP

Follow these steps to integrate the Lyft MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 9 tools from Lyft

Why Use CrewAI with the Lyft MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Lyft through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Lyft + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Lyft MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Lyft for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Lyft, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Lyft tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Lyft against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Lyft MCP Tools for CrewAI (9)

These 9 tools become available when you connect Lyft to CrewAI via MCP:

cancel_ride

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

get_cost_estimate

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

get_eta_estimate

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

get_locations

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

get_ride_details

Use this to track your active ride or review past ride details. Get details of a specific Lyft ride

get_ride_history

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

get_ride_types

) 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

request_ride

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

set_location

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

Example Prompts for Lyft in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Lyft immediately.

"Get me a price estimate from JFK Airport to Times Square for a Lyft XL"

"Book me a Lyft from my home to San Francisco International Airport"

"Show me my last 20 Lyft rides and total spending"

Troubleshooting Lyft MCP Server with CrewAI

Common issues when connecting Lyft to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Lyft + CrewAI FAQ

Common questions about integrating Lyft MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.