`septa_rail_arrivals`

Pack: septa · 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/septa_rail_arrivals for the schema, then POST the same URL with its arguments for the data.

Philadelphia SEPTA Regional Rail departures board for a station — the next trains leaving, grouped Northbound/Southbound with train number, line, destination, scheduled vs estimated departure time, live status (“On Time” or minutes late), and track. Station names are matched forgivingly (“30th street”, “ardmore”, “suburban” all work). Example: septa_rail_arrivals({ station: “Suburban Station”, results: 8 })

Parameters

Name	Type	Required	Description
`station`	string	yes	Regional Rail station name, e.g. “Suburban Station”, “Gray 30th Street” (accepts “30th Street”), “Temple University”, “Ardmore”, “Airport Terminal B”. Partial names are fuzzy-matched to the official station list.
`results`	number	no	Departures to return per direction (default 8, max 30)

Example call

Arguments

{
  "station": "Suburban Station"
}

curl

curl -X POST https://gateway.pipeworx.io/septa/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"septa_rail_arrivals","arguments":{"station":"Suburban Station"}}}'

TypeScript (@pipeworx/sdk)

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

const result = await pipeworx.call('septa_rail_arrivals', {
  "station": "Suburban Station"
});

More examples

{
  "station": "30th Street",
  "results": 5
}

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 septa pack

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

See Getting Started for client-specific install steps.

septa_rail_arrivals