Amtrak

What Amtrak MCP server does

The Amtrak MCP server exposes current Amtrak operations data to MCP-compatible AI clients. Its primary source is a community mirror of Amtrak’s tracking feed at api-v3.amtraker.com, with train positions updating approximately every few minutes. The available tools cover individual train tracking, station activity, network-wide route summaries, and station metadata.

Train searches accept either a train number, such as 6 or 2150, or a route name such as Coast Starlight or Empire Builder. Station tools accept a three-letter Amtrak code, such as CHI, NYP, or LAX, or a station name.

How it works

The Amtrak MCP server can be connected as a remote MCP endpoint at https://gateway.pipeworx.io/amtrak/mcp. That endpoint lists the Amtrak tools along with shared Pipeworx tools, including routing and discovery functions. The full Pipeworx endpoint is also available when an agent needs direct access to the broader catalog of data sources.

A local alternative uses the @pipeworx/mcp-amtrak package over standard input and output. The standalone process exposes only this pack’s four tools and does not include the gateway’s shared meta-tools. The gateway and local package use the same source and tool set for Amtrak data.

Setup and configuration

For a remote connection, add the gateway URL to the MCP client configuration:

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

For local stdio operation, configure the client to run:

{
  "mcpServers": {
    "amtrak": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-amtrak"]
    }
  }
}

Tools can also be called over HTTP through the Pipeworx tool endpoint, including a direct POST request to https://gateway.pipeworx.io/v1/tools/amtrak_train_status.

Tools and capabilities

• amtrak_train_status returns active instances, GPS position, speed, heading, timeliness, next station, estimated arrival, delay minutes, and scheduled versus actual origin and destination times.
• amtrak_station_board returns en-route trains for a station, including route, scheduled and estimated arrival, delay, and status.
• amtrak_routes_active summarizes active trains by route, with counts, train numbers, and the worst delay in minutes.
• amtrak_station_info returns a station’s name, code, city and state, address, timezone, coordinates, and current inbound train count.

Limitations and notes

The Amtrak MCP server relies on a community mirror rather than a directly documented Amtrak API. Results describe live tracking and operational status, so they may change between calls.

Remote pack connections include shared Pipeworx meta-tools in addition to the listed Amtrak tools. The standalone package avoids those gateway tools but requires the local npx command.