ManosMrgk/oasa-mcp

OASA MCP Server

This project provides a Modular Command Protocol (MCP) server that exposes tools for accessing OASA Telematics data.
It allows an LLM or external client to query real-time and scheduled bus information from the OASA APIs.

Features

The MCP server exposes the following tools:

1. get_lines

Retrieves all available bus lines with their metadata.
Includes both the public LineId (bus number such as Β1, 040, etc.) and the internal line_code used by API endpoints.

2. get_bus_line_stops

Returns all stops for a specific line, grouped by route.
Requires an internal line_code, which can be obtained via get_lines.

3. get_bus_arrivals_on_stop

Fetches live ETAs for a specific stop and line.
Accepts either a stop name (in Greek or English) or a stop code.

4. get_bus_schedules

Lists available schedule types (e.g. Winter, Summer, detour) for a given line.

5. get_bus_departures

Returns planned departures (go and come lists) for a specific line and schedule type.

6. get_routes_for_stop_tool

Lists all routes that serve a particular stop.
The stop can be specified by name (resolved within a given line) or by code.

7. get_arrivals_for_stop_tool

Returns live arrival data for a stop, either by stop name (within a line) or stop code.

Key Concepts

• LineId: The public bus number printed on buses and schedules (e.g. Β1, 040).
• line_code: Internal OASA identifier used in API calls.
• master_line_code: Used to retrieve schedules and departure information.

Typical workflow:

User mentions LineId → get_lines → retrieve line_code / master_line_code → query stops, arrivals, or schedules

The server runs via standard I/O (transport="stdio") and can be connected to any MCP-compatible client or LLM.