{
  "markdown": "# mcp-amtrak\n\nAmtrak MCP — live Amtrak train tracking via the community Amtraker API\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `amtrak_train_status` | Live Amtrak train status and GPS tracking — \"where is my Amtrak train\", \"is train 6 late\", \"track the California Zephyr\". Accepts a train number (\"6\", \"2150\") or route name (\"Coast Starlight\", \"Empire Builder\"). Returns each active instance of that train: current GPS position, speed, heading, timeliness, next station with ETA and delay minutes, and origin/destination scheduled vs actual times. Data is a community mirror of Amtrak's own tracking feed (api-v3.amtraker.com); positions update about every few minutes. Example: amtrak_train_status({ train: \"6\" }) |\n| `amtrak_station_board` | Amtrak station departures/arrivals board — upcoming trains at a station. \"What trains are arriving at Chicago Union?\", \"next train at CHI\", \"station board for Denver\". Accepts a 3-letter Amtrak station code (\"CHI\", \"NYP\", \"LAX\") or a station name (\"Chicago\", \"Portland\"). Returns trains currently en route to that station with route, scheduled vs estimated arrival, delay minutes, and status. Live community mirror of Amtrak tracking (api-v3.amtraker.com). Example: amtrak_station_board({ station: \"CHI\" }) |\n| `amtrak_routes_active` | Summary of ALL currently active Amtrak trains grouped by route — \"how many Amtrak trains are running right now\", \"which Amtrak routes have delays\", national system overview. Returns per route: active train count, train numbers, and the worst delay in minutes. Compact; live from a community mirror of Amtrak's tracking feed. Example: amtrak_routes_active({}) |\n| `amtrak_station_info` | Amtrak station lookup by code or name — station name, 3-letter code, city/state, street address, timezone, coordinates, and how many trains are currently inbound. \"Where is the Amtrak station in Denver?\", \"what is station code NYP\". Example: amtrak_station_info({ station: \"Denver\" }) |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"amtrak\": {\n      \"url\": \"https://gateway.pipeworx.io/amtrak/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/amtrak/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Amtrak data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 4103,
  "sha": "56fcf93cd260f6b3139fcb1b21d737ce451d7b02c2524523a2c5ffd686ee8206",
  "repo_slug": "pipeworx-io/mcp-amtrak",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_amtrak_38e2387a/readme"
}