prt-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@prt-mcp when is the next bus at stop 20001?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
prt-mcp
MCP server exposing Pittsburgh Regional Transit (PRT) TrueTime operations as typed tools for agent clients.
What this implements
MCP
toolsfor core TrueTime queries:prt_get_routesprt_get_directionsprt_get_stopsprt_get_vehiclesprt_get_predictionsprt_get_patternsprt_get_service_bulletins
MCP
resources:prt://capabilities(discoverability for clients)
MCP
prompts:transit-arrival-workflow
Related MCP server: marta-mcp
Source references used for design
MCP protocol/spec and server guidance:
modelcontextprotocol.io docs + specification (JSON-RPC, capabilities, safety)
MCP reference implementations:
modelcontextprotocol/servers(everything,fetch,filesystem)
MCP SDK patterns:
modelcontextprotocol/typescript-sdk
PRT data/API entry points:
PRT Developer Resources
TrueTime account/API key workflow
TrueTime v3 endpoint behavior from public community codebases:
juctaposed/bustimePGHaidan2312/prt-api
Prerequisites
Node 20+ (Node 22 recommended)
A PRT TrueTime API key
Configuration
Copy env template:
cp .env.example .envSet:
PRT_TRUETIME_API_KEY(required)Optional tuning:
PRT_TRUETIME_BASE_URLPRT_REQUEST_TIMEOUT_MSPRT_MAX_RETRIESPRT_USER_AGENT
Optional HTTP mode security:
HOST(default:127.0.0.1)PORT(default:3000)MCP_ALLOWED_HOSTS(comma-separatedHostallowlist)MCP_ALLOWED_ORIGINS(comma-separated browserOriginallowlist)MCP_AUTH_TOKEN(Bearer token expected on/mcp)MCP_RATE_LIMIT_WINDOW_MSMCP_RATE_LIMIT_MAX
Run
npm install
npm run build
npm startFor local development:
npm run devFor hosted HTTP mode (remote MCP endpoint):
npm run build
PORT=3000 HOST=0.0.0.0 MCP_AUTH_TOKEN=change-me npm run start:httpHealth check:
curl http://localhost:3000/healthzMCP endpoint:
POST /mcpGET /mcp(SSE stream)DELETE /mcp(close session if stateful)Include
Authorization: Bearer <MCP_AUTH_TOKEN>if auth is enabled.
Alternate SSE endpoint for clients that expect /sse:
POST /sseGET /sse(SSE stream)DELETE /sse(close session if stateful)
Example MCP client config (stdio)
{
"mcpServers": {
"prt": {
"command": "node",
"args": ["/ABSOLUTE/PATH/prt-mcp/dist/index.js"],
"env": {
"PRT_TRUETIME_API_KEY": "YOUR_KEY"
}
}
}
}Hosting options
You now have two transport modes:
Local stdio (
npm start)
Best for Claude Desktop / local agent tools.Remote Streamable HTTP (
npm run start:http)
Best for hosting on Render/Railway/Fly.io/a VM.
Minimal production checklist:
Set
PRT_TRUETIME_API_KEYin host environment variables.Use Node 20+ runtime.
Expose the
PORTyour host provides.Keep at least one health check path (
/healthz).Set
MCP_AUTH_TOKEN.Set
MCP_ALLOWED_HOSTSandMCP_ALLOWED_ORIGINSfor your deployment.Restrict inbound access (IP allowlist, auth gateway, or private network).
Example Render/Railway start command:
npm run build && npm run start:httpDocker
Build image:
docker build -t prt-mcp:latest .Run container:
docker run --rm -p 3000:3000 -e PRT_TRUETIME_API_KEY=YOUR_KEY prt-mcp:latestImplementation best practices applied
Input validation with
zodon every tool schemaFail-fast config checks (missing key)
Retry + timeout behavior to handle unstable upstream API responses
Uniform structured + text output for deterministic agent parsing
Tool execution failures returned as MCP
isErrorresultsTool annotations (
readOnlyHint,idempotentHint,openWorldHint) for client safety hintsHTTP hardening: auth token, origin checks, host allowlist support, and rate limiting
Strict TypeScript + minimal surface area
No secrets in source; env-only configuration
Notes
TrueTime key acquisition is account-gated by PRT.
API responses can differ by data feed (
Port Authority Bus,Light Rail).Some endpoints require additional filters (
rt,stpid,pid).
Available Tools
7 toolsprt_get_directionsGet route directionsCRead-onlyIdempotent
Fetch available directions for a route using getdirections.
Inputs: rt (required), rtpidatafeed.
prt_get_patternsGet route patternsCRead-onlyIdempotent
Fetch route geometry/pattern data via getpatterns.
Inputs: rt, pid, rtpidatafeed.
prt_get_predictionsGet stop predictionsCRead-onlyIdempotent
Fetch arrival predictions for one or more stop IDs.
Inputs: stpid (required), top, rtpidatafeed.
prt_get_routesGet PRT routesCRead-onlyIdempotent
Fetch route metadata from TrueTime getroutes.
Inputs: rtpidatafeed.
prt_get_service_bulletinsGet service bulletinsCRead-onlyIdempotent
Fetch service bulletins using getservicebulletins.
Inputs: rt, rtpidatafeed.
prt_get_stopsGet route stopsCRead-onlyIdempotent
Fetch stops for a route with optional direction using getstops.
Inputs: rt (required), dir, rtpidatafeed.
prt_get_vehiclesGet active vehiclesCRead-onlyIdempotent
Fetch live vehicle data via getvehicles.
Inputs: rt, vid, rtpidatafeed.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool targets a distinct TrueTime data endpoint: routes, directions, stops, vehicles, predictions, patterns, and service bulletins. The nouns alone make the intended data type unambiguous, so an agent can reliably select the correct tool.
Every tool follows the same prt_get_<plural_noun> snake_case pattern with a shared prt prefix. There are no deviations in verb style, casing, or structure, making the set highly predictable.
Seven read-only tools map cleanly to the seven TrueTime API endpoints. The count is well-scoped for a transit data wrapper, with no redundant or filler tools.
The surface covers the full TrueTime read-only endpoint set: routes, directions, stops, vehicles, predictions, patterns, and service bulletins. All standard transit-data queries are reachable with no obvious dead ends for the stated purpose.
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Hosted MCP server for live public-data APIs and Skills for AI agents.
MCP server exposing the Backtest360 engine API as tools for AI agents.
Read-only MCP server for the Durable Agent Directory: search and compare agent-infrastructure tools.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that provides tools for querying live transit data (stops, departures, routes, vehicles, alerts) from any WP GTFS Pro site, enabling AI assistants to answer rider questions.8 npmGPL 2.0
- AlicenseAqualityCmaintenanceMCP server for Atlanta MARTA real-time transit data, enabling queries about train arrivals and bus positions via natural language.4MIT
- AlicenseBqualityDmaintenanceMCP server that integrates with the transport12 API to provide tools for searching stops, routes, arrivals, and vehicle forecasts, enabling natural language interaction with public transport data.1711 npmMIT
- FlicenseAqualityDmaintenanceMCP server for St. Louis transit developer tooling, providing 45 tools for GTFS and GTFS-Realtime inspection, feed surveillance, schedule and arrival queries, assertions, drift detection, and golden-fixture generation for the Light Phone 3 Kotlin transit app, all backed by public unauthenticated sources.45-