2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 9 Tools SDK

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Lyft as an MCP tool provider through Vinkius and your ADK agents can call every tool with full schema introspection.

Vinkius supports streamable HTTP and SSE.

python
from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
    StreamableHTTPConnectionParams,
)

# Your Vinkius token. get it at cloud.vinkius.com
mcp_tools = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    )
)

agent = Agent(
    model="gemini-2.5-pro",
    name="lyft_agent",
    instruction=(
        "You help users interact with Lyft "
        "using 9 available tools."
    ),
    tools=[mcp_tools],
)
Lyft
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:

Google ADK natively supports Lyft as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 9 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

  • 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 Google ADK 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 Google ADK via MCP

Follow these steps to integrate the Lyft MCP Server with Google ADK.

01

Install Google ADK

Run pip install google-adk

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Create the agent

Save the code above and integrate into your ADK workflow

04

Explore tools

The agent will discover 9 tools from Lyft via MCP

Why Use Google ADK with the Lyft MCP Server

Google ADK provides unique advantages when paired with Lyft through the Model Context Protocol.

01

Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution

02

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Lyft

03

Production-ready features like session management, evaluation, and deployment come built-in. not bolted on

04

Seamless integration with Google Cloud services means you can combine Lyft tools with BigQuery, Vertex AI, and Cloud Functions

Lyft + Google ADK Use Cases

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

01

Enterprise data agents: ADK agents query Lyft and cross-reference results with internal databases for comprehensive analysis

02

Multi-modal workflows: combine Lyft tool responses with Gemini's vision and language capabilities in a single agent

03

Automated compliance checks: schedule ADK agents to query Lyft regularly and flag policy violations or configuration drift

04

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Lyft

Lyft MCP Tools for Google ADK (9)

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

01

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

02

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

03

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

04

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

05

get_ride_details

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

06

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

07

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

08

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

09

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 Google ADK

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

01

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

02

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

03

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

Troubleshooting Lyft MCP Server with Google ADK

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

01

McpToolset not found

Update: pip install --upgrade google-adk

Lyft + Google ADK FAQ

Common questions about integrating Lyft MCP Server with Google ADK.

01

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.
02

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.
03

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.

Connect Lyft to Google ADK

Get your token, paste the configuration, and start using 9 tools in under 2 minutes. No API key management needed.