# NJ Transit and PATH Schedules Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## NJ Transit and PATH Schedules

Check NJ Transit rail, bus and light rail schedules, plus live PATH train arrivals, from Muse.

- Record: https://musedirectory.ai/connector/nj-transit-and-path-schedules
- Category: Travel
- Developer: mir-quadri
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 197ms, checked 2026-11-02T01:46:14Z
- Endpoint: https://nj-transit-mcp.vercel.app/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-02T01:46:14Z)
- Source: Found in the official MCP Registry (io.github.mir-quadri/nj-transit-mcp) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.mir-quadri%2Fnj-transit-mcp

Connects to NJ Transit rail, light rail and bus schedules, and live PATH arrivals. Muse can find stations and stops, list the next departures, plan a same-trip route between two points, look up lines and check the server's data status. NJ Transit live delays and alerts need your own NJT credentials, and bus data is scheduled only.

Example request: "When is the next NJ Transit train from Newark Penn Station to Princeton Junction, and is PATH running on time from Journal Square?"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use NJ Transit and PATH Schedules to help me. It is a free service with an MCP server at https://nj-transit-mcp.vercel.app/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- search_stations: Find stations/stops by name. system: 'nj_transit' (rail + light rail), 'nj_bus' (NJ Transit bus street stops), 'path', or 'all'. 'all' includes bus, so a first 'all' search downloads the 50 MB bus GTFS once; use system='nj_bus' for bus-only searches. Returns station/stop IDs to u
- next_departures: Next departures from a station/stop (name or stop ID). system 'nj_transit': rail + light rail, scheduled by default, live delays when NJT credentials are configured. system 'nj_bus': NJ Transit bus, SCHEDULED only in v1.2 (BUSDATA live not enabled). system 'path': live PATH arriv
- trip_between: Next NJ Transit trains/buses from origin to destination on the SAME trip (no transfers). Returns departure, arrival and duration. Times ET. system: 'nj_transit' (default, rail + light rail) or 'nj_bus' (bus, scheduled only in v1.2).
- lines: All lines/routes. NJ Transit: 17 rail + light-rail routes. NJ bus: 263 routes (short_name is the bus number; long names are empty in the bus feed, use trip headsigns for destinations). PATH: 4 daytime routes.
- service_alerts: Service alerts. NJ Transit alerts require NJT credentials (see server_status for how to enable); PATH has no separate alerts feed in v1, so PATH alerts are reported as unavailable, not invented.
- server_status: What data this server is actually serving right now: GTFS date range and counts, whether live NJ data is enabled, PATH feed age. Use this to answer 'is this live or scheduled?' honestly.

Screening checks:
- MCP handshake: pass (Answered in 197ms)
- Domain against threat feeds (Cloudflare security DNS): pass (nj-transit-mcp.vercel.app not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (6 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)