How to Use the Lyft MCP in AutoGen

Q: How do AutoGen agents negotiate the best Lyft ride price?

One AutoGen agent queries getcostestimate while another checks getetaestimate. They debate the trade-off between Lyft price and wait time in the chat before deciding to trigger requestride.

Q: How do AutoGen agents manage my saved Lyft locations?

Your AutoGen agents can query getlocations to find saved Lyft coordinates, discuss which destination is correct, or update them by executing setlocation during the conversation.

Q: How do my AutoGen agents verify which Lyft vehicle types are available?

Have an AutoGen agent run getridetypes to check Lyft capacities and descriptions. The agents can then debate whether to book a standard Lyft or a larger vehicle based on team size.

Let AutoGen agents debate prices and arrival times using this Lyft MCP Server to book the optimal ride for your schedule.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Lyft MCP to AutoGen

Create your Vinkius account to connect Lyft to AutoGen and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Lyft with AutoGen

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run AutoGen agent debates on Lyft ride options

Your AutoGen budget agent queries `get_cost_estimate` to start a debate with your scheduling agent about Lyft ride trade-offs. The AutoGen agents discuss the trade-offs in your conversation thread to find the sweet spot between Lyft cost and speed. Once the AutoGen agents agree, a booking agent triggers `request_ride` to secure the Lyft. This prevents hasty decisions and ensures your AutoGen group never accidentally books a high-surge Lyft when a cheaper option is minutes away.

Coordinate complex Lyft travel plans via AutoGen debate

Your AutoGen agents can pull coordinates using `get_locations` to coordinate multi-passenger Lyft logistics through conversation. One agent checks vehicle capacities with `get_ride_types` to ensure everyone fits in the requested Lyft. If plans shift, a coordinator AutoGen agent can step in and call `cancel_ride` to stop the active Lyft trip. The agents then negotiate a new destination using `set_location` within the chat thread.

Audit your Lyft travel expenses with this MCP Server

Your AutoGen finance agent can query `get_ride_history` to pull past Lyft receipts and audit corporate travel spending. The audit agent reviews the logs and uses `get_ride_details` to verify that employees booked the correct Lyft vehicle types. The AutoGen agents discuss any Lyft booking discrepancies directly in the chat. Because Vinkius manages the authentication, your AutoGen agents can access these Lyft tools securely using a single endpoint token.

Setup guide

Set up Lyft MCP in AutoGen

Prerequisites

Python 3.10+ installed
autogen-ext[mcp] package
Active Vinkius subscription with a valid endpoint token

1

Install AutoGen with MCP
Run pip install "autogen-ext[mcp]" autogen-agentchat. The MCP extension includes mcp_server_tools for stateless tool access.
2

Fetch tools from the MCP
Call mcp_server_tools(SseServerParams(url=...)) with your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Run your agent
Pass the tools to AssistantAgent and call agent.run(). The agent invokes Lyft tools and returns structured results.

agent.py

from autogen_ext.tools.mcp import SseServerParams, mcp_server_tools
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient

server_params = SseServerParams(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

tools = await mcp_server_tools(server_params)

agent = AssistantAgent(
    name="Lyft_assistant",
    model_client=OpenAIChatCompletionClient(model="gpt-4o"),
    tools=tools,
)

result = await agent.run("List recent Lyft data")
print(result.messages[-1].content)

Get your connection token →

Prerequisites

Python 3.10+ installed
autogen-ext[mcp] + autogen-agentchat
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Same packages as above. McpWorkbench is ideal when your agent needs stateful sessions across multiple tool calls.
2

Use McpWorkbench as context manager
Wrap your agent in async with McpWorkbench(...) to maintain shared state and resources. The workbench manages the full MCP session lifecycle.
3

Run with workbench
Pass workbench=workbench to your agent. State is preserved across multiple tool calls within the same session.

agent.py

from autogen_ext.tools.mcp import McpWorkbench, SseServerParams
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient

server_params = SseServerParams(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

async with McpWorkbench(server_params) as workbench:
    agent = AssistantAgent(
        name="Lyft_assistant",
        model_client=OpenAIChatCompletionClient(model="gpt-4o"),
        workbench=workbench,
    )

    result = await agent.run("List recent Lyft data")
    print(result.messages[-1].content)

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Lyft now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Lyft MCP in AutoGen

One AutoGen agent queries `get_cost_estimate` while another checks `get_eta_estimate`. They debate the trade-off between Lyft price and wait time in the chat before deciding to trigger `request_ride`.

Yes. If a scheduling AutoGen agent detects a calendar conflict, it can use the MCP tools to call `cancel_ride` and terminate the active Lyft trip immediately.

Your AutoGen agents can query `get_locations` to find saved Lyft coordinates, discuss which destination is correct, or update them by executing `set_location` during the conversation.

Have an AutoGen agent run `get_ride_types` to check Lyft capacities and descriptions. The agents can then debate whether to book a standard Lyft or a larger vehicle based on team size.

Yes. This MCP Server runs on the Vinkius platform inside secure, ephemeral V8 isolates. Your coordinates, location IDs, and trip history are never stored, ensuring complete data privacy for your AutoGen workflows.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript