2,500+ MCP servers ready to use
Vinkius

Lyko MCP Server for Vercel AI SDK 12 tools — connect in under 2 minutes

Built by Vinkius GDPR 12 Tools SDK

The Vercel AI SDK is the TypeScript toolkit for building AI-powered applications. Connect Lyko through Vinkius and every tool is available as a typed function. ready for React Server Components, API routes, or any Node.js backend.

Vinkius supports streamable HTTP and SSE.

typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { generateText } from "ai";
import { openai } from "@ai-sdk/openai";

async function main() {
  const mcpClient = await createMCPClient({
    transport: {
      type: "http",
      // Your Vinkius token. get it at cloud.vinkius.com
      url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    },
  });

  try {
    const tools = await mcpClient.tools();
    const { text } = await generateText({
      model: openai("gpt-4o"),
      tools,
      prompt: "Using Lyko, list all available capabilities.",
    });
    console.log(text);
  } finally {
    await mcpClient.close();
  }
}

main();
Lyko
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 Lyko MCP Server

Connect your Lyko Transit API mobility platform to any AI agent and take full control of European public transit planning, real-time departure monitoring, and multimodal journey optimization through natural conversation.

The Vercel AI SDK gives every Lyko tool full TypeScript type inference, IDE autocomplete, and compile-time error checking. Connect 12 tools through Vinkius and stream results progressively to React, Svelte, or Vue components. works on Edge Functions, Cloudflare Workers, and any Node.js runtime.

What you can do

  • Trip Planning — Plan door-to-door intermodal journeys combining buses, trains, subways, trams, ferries, bike-sharing, and walking
  • Real-Time Departures — Check upcoming departures at any transit stop with ETAs, platforms, and delay indicators
  • Arrival Tracking — Monitor incoming services for passenger pickup and connection coordination
  • Stop Discovery — Search transit stops by name, address, or landmark across 300+ European operators
  • Nearby Stops — Find all transit stops near any geographic location with distance calculations
  • Stop Details — Get comprehensive stop information including served lines, accessibility, and amenities
  • Line Information — Research transit lines with operator details, service hours, and route characteristics
  • Line Routes — View complete stop sequences and route patterns for any transit line
  • Operator Directory — Browse 300+ transit operators across Europe with coverage areas and service modes
  • Network Status — Check service disruptions, planned works, strikes, and delay alerts for any operator
  • GTFS Feeds — Access raw GTFS transit data for offline analysis and academic research
  • Trip Booking — Book train tickets, bus passes, bike rentals, and other mobility services through Lyko Book

The Lyko MCP Server exposes 12 tools through the Vinkius. Connect it to Vercel AI SDK 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 Lyko to Vercel AI SDK via MCP

Follow these steps to integrate the Lyko MCP Server with Vercel AI SDK.

01

Install dependencies

Run npm install @ai-sdk/mcp ai @ai-sdk/openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the script

Save to agent.ts and run with npx tsx agent.ts

04

Explore tools

The SDK discovers 12 tools from Lyko and passes them to the LLM

Why Use Vercel AI SDK with the Lyko MCP Server

Vercel AI SDK provides unique advantages when paired with Lyko through the Model Context Protocol.

01

TypeScript-first: every MCP tool gets full type inference, IDE autocomplete, and compile-time error checking out of the box

02

Framework-agnostic core works with Next.js, Nuxt, SvelteKit, or any Node.js runtime. same Lyko integration everywhere

03

Built-in streaming UI primitives let you display Lyko tool results progressively in React, Svelte, or Vue components

04

Edge-compatible: the AI SDK runs on Vercel Edge Functions, Cloudflare Workers, and other edge runtimes for minimal latency

Lyko + Vercel AI SDK Use Cases

Practical scenarios where Vercel AI SDK combined with the Lyko MCP Server delivers measurable value.

01

AI-powered web apps: build dashboards that query Lyko in real-time and stream results to the UI with zero loading states

02

API backends: create serverless endpoints that orchestrate Lyko tools and return structured JSON responses to any frontend

03

Chatbots with tool use: embed Lyko capabilities into conversational interfaces with streaming responses and tool call visibility

04

Internal tools: build admin panels where team members interact with Lyko through natural language queries

Lyko MCP Tools for Vercel AI SDK (12)

These 12 tools become available when you connect Lyko to Vercel AI SDK via MCP:

01

book_trip

Supports booking train tickets, bus tickets, bike-sharing rentals, car-sharing reservations, and other mobility services available through the Lyko Book platform. Returns booking confirmation, payment details, ticket information, QR codes for validation, and cancellation policies. Availability and booking capabilities vary by operator and service type. Essential for Mobility-as-a-Service integration, ticket purchasing, service reservations, and end-to-end journey planning with booking. AI agents should use this when users ask "book this train ticket", "reserve a bike for this trip", or want to complete a mobility service reservation after planning a route. Book a transit trip or mobility service through Lyko Book

02

get_arrivals

Returns list of arriving services with line names and numbers, origins, scheduled and real-time arrival times (ETA), platform or bay information, delay indicators, and operator details. Essential for passenger pickup coordination, arrival monitoring, transit hub management, and real-time arrival boards. AI agents use this when users ask "when does the next train arrive at X", "show incoming services at this station", or need to track arriving services for passenger coordination. Get upcoming arrivals at a specific transit stop

03

get_departures

Returns list of departing services with line names and numbers, destinations, scheduled and real-time departure times (ETD), platform or bay information, delay indicators, and operator details. Supports buses, trains, trams, subways, and ferries across European transit networks. Essential for passenger information displays, departure boards, travel apps, and real-time transit monitoring. AI agents should reference this when users ask "when is the next bus from stop X", "show departures from this station", or need to monitor upcoming services at a known transit stop. Get next departures from a specific transit stop

04

get_line_info

Returns line name, number, type (bus, train, tram, subway, ferry), operator, color code, route description, service hours, frequency, and accessibility information. Essential for line identification, transit network exploration, service information queries, and route planning context. AI agents should reference this when users ask "tell me about line M1", "what operator runs bus line 42", or need line metadata to understand transit service characteristics. Get information about a specific transit line

05

get_line_routes

Returns route variants (e.g., direction A and B), complete stop sequences with order, scheduled frequencies, first and last service times, and any service variations (express vs. local, peak vs. off-peak). Essential for complete line visualization, stop sequence analysis, transit mapping, and understanding service patterns. AI agents use this when users ask "show me all stops on line X", "what is the full route of bus 42", or need to understand complete service patterns for a transit line. Get all routes and stops for a specific transit line

06

get_nearby_stops

Returns nearby stops with distances from the coordinate, stop names, locations, served lines, operators, and stop types, sorted by proximity. Essential for location-based transit discovery, passenger navigation, "stops near me" features, and geographic transit analysis. AI agents use this when users ask "what stops are near my current location", "find transit stops within 500m of these coordinates", or need to discover accessible transit options from a specific point. Find transit stops near a geographic location

07

get_network_status

Returns active service disruptions, planned works, line closures, delay information, weather impacts, strike notifications, and alternative service recommendations. Essential for real-time service monitoring, disruption awareness, passenger communication, and travel planning during service changes. AI agents should reference this when users ask "are there any disruptions on SNCF trains", "is the Berlin U-Bahn running normally", or need to check service reliability before planning trips. Get current network status and service alerts for a transit operator

08

get_operators

Returns operator names, IDs, countries, coverage areas, transport modes operated (bus, train, tram, subway, ferry), contact information, and service status. Covers 300+ operators across Europe including SNCF (France), DB (Germany), NS (Netherlands), RENFE (Spain), Trenitalia (Italy), and many regional and local operators. Essential for operator research, transit network scoping, country-specific transit analysis, and understanding service coverage. AI agents should use this when users ask "what transit operators are available in France", "list all train operators in Germany", or need to identify operators for a specific country or region. List public transit operators available in a country or region

09

get_stop_info

Returns stop name, location (latitude, longitude, address), served lines and routes, stop type (bus stop, train station, tram stop, subway station, ferry terminal), operator information, accessibility features (wheelchair access, elevators), and available amenities. Essential for stop identification, accessibility planning, transit network analysis, and passenger information. AI agents should use this when users ask "tell me about this stop", "what lines serve stop X", or need detailed stop metadata to contextualize transit queries. Get detailed information about a specific transit stop

10

get_transit_feed

Returns feed metadata, last update timestamp, included operators, coverage area, data freshness indicators, and download or access URLs. GTFS feeds contain static schedule data, route definitions, stop locations, fare information, and service calendars. Essential for transit data analysis, offline planning applications, academic research, and transit network visualization. AI agents use this when users need access to raw GTFS data, want to analyze transit schedules offline, or require complete network definitions for planning applications. Access GTFS transit feed data for a specific operator or region

11

plan_trip

Supports multiple transport modes including buses, trains, subways, trams, ferries, bike-sharing, car-sharing, and walking combinations. Returns complete itinerary with departure and arrival times, duration, number of transfers, legs with mode details (line name, operator, vehicle type), intermediate stops, walking distances, fares if available, and real-time delay information. Essential for travel planning, multimodal journey optimization, passenger information systems, and Mobility-as-a-Service (MaaS) applications. AI agents should use this when users ask "how do I get from X to Y by public transport", "plan a trip from Paris Gare du Nord to Versailles", or need intermodal route options with timing and transfer details. Plan an intermodal trip between two locations using public transit

12

search_stops

Returns matching stops with stop IDs, names, locations (latitude, longitude), served lines, operators, and stop types. Essential for stop discovery, journey planning interfaces, transit stop identification, and building location-based transit features. AI agents should use this when users ask "find the bus stop near Champs-Elysees", "search for stops called X", or need to identify stop IDs for use in departure/arrival queries. Search for transit stops by name or location

Example Prompts for Lyko in Vercel AI SDK

Ready-to-use prompts you can give your Vercel AI SDK agent to start working with Lyko immediately.

01

"Plan a trip from Paris Gare du Nord to the Palace of Versailles using public transit."

02

"Show me all departures from Berlin Alexanderplatz station in the next 30 minutes."

03

"What transit operators are available in the Netherlands, and is NS (Dutch Railways) running normally today?"

Troubleshooting Lyko MCP Server with Vercel AI SDK

Common issues when connecting Lyko to Vercel AI SDK through the Vinkius, and how to resolve them.

01

createMCPClient is not a function

Install: npm install @ai-sdk/mcp

Lyko + Vercel AI SDK FAQ

Common questions about integrating Lyko MCP Server with Vercel AI SDK.

01

How does the Vercel AI SDK connect to MCP servers?

Import createMCPClient from @ai-sdk/mcp and pass the server URL. The SDK discovers all tools and provides typed TypeScript interfaces for each one.
02

Can I use MCP tools in Edge Functions?

Yes. The AI SDK is fully edge-compatible. MCP connections work on Vercel Edge Functions, Cloudflare Workers, and similar runtimes.
03

Does it support streaming tool results?

Yes. The SDK provides streaming primitives like useChat and streamText that handle tool calls and display results progressively in the UI.

Connect Lyko to Vercel AI SDK

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