How to Use the Lyko MCP in Google ADK

Q: Can I filter which Lyko tools my Google ADK agent sees?

Yes. You can pass a toolnames filter to the McpToolset. This restricts the agent to specific capabilities, like only allowing plantrip and getarrivals if you want to limit scope.

Integrate Lyko transit data into your Google ADK agent to power enterprise-scale routing on Google Cloud.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Lyko MCP to Google ADK

Create your Vinkius account to connect Lyko to Google ADK 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 Lyko with Google ADK

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Search and map stops using Google ADK

Utilize `search_stops` and `get_nearby_stops` to locate transit infrastructure based on user coordinates or names. Your agent processes these results to feed location-aware transit features directly into your application. Passing these results into `get_stop_info` gives your agent the specific accessibility data needed for trip planning. This ensures the agent suggests only those stations that meet the user's physical requirements.

Manage transit lines through Google ADK

Retrieve metadata for any European transit line using `get_line_info` and `get_line_routes`. Your agent uses these details to explain service frequencies, operator types, and full stop sequences to the user. This provides the necessary context for your agent to distinguish between express and local services. By analyzing the returned route variants, the agent builds an accurate mental model of the local transit network.

Access transit feeds via Google ADK

Call `get_transit_feed` to pull raw GTFS data for specific regions. Your agent processes this information to perform deep analysis on network coverage or to build offline planning caches for your users. This tool returns the freshness indicators and download URLs required for your backend pipelines. It allows your Google ADK agent to maintain a high-fidelity view of the underlying transit data.

Setup guide

Set up Lyko MCP in Google ADK

Prerequisites

Python 3.10+ installed
google-adk package (pip install google-adk)
Active Vinkius subscription with a valid endpoint token

1

Install Google ADK

Run pip install google-adk to install the Agent Development Kit. MCP support is included via the McpToolset class.
2

Connect via SSE transport

Use McpToolset.from_server() with SseServerParams pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create an LlmAgent

Pass the returned mcp_tools list directly to LlmAgent(tools=mcp_tools). The ADK maps each MCP tool to a native Gemini function call — no manual schema definitions required.
4

Run with any Gemini model

The agent works with any Gemini model (gemini-2.0-flash, gemini-2.5-pro, etc.). Copy the full example on the right to get started with Lyko tools in your ADK agent.

agent.py

from google.adk.agents import LlmAgent
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import SseServerParams

# Connect to the MCP via SSE
mcp_tools, exit_stack = await McpToolset.from_server(
    connection_params=SseServerParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    )
)

# Create your agent with auto-discovered tools
agent = LlmAgent(
    name="Lyko_agent",
    model="gemini-2.0-flash",
    instruction="You have access to Lyko tools via MCP.",
    tools=mcp_tools,
)

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 Lyko. 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 Lyko 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 Lyko MCP in Google ADK

Absolutely. Use the McpToolset with your Lyko server URL to expose the 12 tools to your LlmAgent. The ADK handles the transport, making transit data available as native functions for your agent.

The Lyko MCP Server provides a standard interface for your agent to query transit data while your Google Cloud infrastructure manages the heavy lifting. This keeps your transit logic separate from your primary application code.

Yes. You can pass a tool_names filter to the McpToolset. This restricts the agent to specific capabilities, like only allowing `plan_trip` and `get_arrivals` if you want to limit scope.

Lyko transmits transit coordinates and booking IDs over secure channels. Your Google ADK agent treats this as transient data, never storing PII in your persistent storage unless you explicitly code that behavior.

Yes. The underlying HTTP transport allows your agent to fetch the latest network status via `get_network_status`. This ensures the agent always sees the most recent service disruptions.

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