Skip to main content
Glama

CATA Bus MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Schema

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Tools

Functions exposed to the LLM to take actions

NameDescription
list_routes_tool

List all available bus routes.

Returns a list of routes with their ID, short name, long name, and color.

search_stops_tool

Search for stops by name or ID.

Args: query: Search query string to match against stop names, IDs, or descriptions

Returns: List of matching stops with their ID, name, latitude, and longitude

next_arrivals_tool

Get next arrivals at a specific stop.

Args: stop_id: The stop ID to query horizon_minutes: How many minutes ahead to look (default 30)

Returns: List of upcoming arrivals with trip ID, route ID, arrival time, and delay

vehicle_positions_tool

Get current positions of vehicles on a specific route.

Args: route_id: The route ID to filter by (e.g., "BL" for Blue Loop)

Returns: List of vehicle positions with ID, coordinates, bearing, and speed

trip_alerts_tool

Get current service alerts.

Args: route_id: Optional route ID to filter alerts (if None, returns all)

Returns: List of alerts with route ID, header, description, and severity

health_check

Ultra-fast health check optimized for cloud pre-flight validation.

initialize_data

Manually trigger GTFS data initialization.

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pranav-Karra-3301/catabus-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server