`lametro_route_stops`

Pack: la-metro · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/lametro_route_stops for the schema, then POST the same URL with its arguments for the data.

Every stop served by one LA Metro route, in running order, with stop id, name, direction and service day type. AUTHORITATIVE for “which stops does route N serve” and for turning a route into stop ids you can look up with lametro_stop.

Parameters

Name	Type	Required	Description
`route_code`	string	yes	Route code from lametro_routes — a number for bus (e.g. “10”, “720”), or a line name for rail (e.g. “Metro A-Line”).
`agency`	string	no	’LACMTA’ (bus, default) or ‘LACMTA_Rail’.
`direction_id`	number	no	Optional: keep only direction 0 or 1.

Example call

Arguments

{
  "route_code": "720",
  "direction_id": 0
}

curl

curl -X POST https://gateway.pipeworx.io/la-metro/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"lametro_route_stops","arguments":{"route_code":"720","direction_id":0}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('lametro_route_stops', {
  "route_code": "720",
  "direction_id": 0
});

More examples

{
  "route_code": "10"
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Connect to just the la-metro pack

{
  "mcpServers": {
    "la-metro": {
      "url": "https://gateway.pipeworx.io/la-metro/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

lametro_route_stops