4,000+ servers built on MCP Fusion
Vinkius
LlamaIndexFramework
LlamaIndex
Why use MTA MCP Server with LlamaIndex?

Bring Real Time Transit
to LlamaIndex

Create your Vinkius account to connect MTA to LlamaIndex and start using all 12 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.

MCP Inspector GDPR Free for Subscribers
Get Bus Estimated ArrivalGet Bus PredictionsGet Bus RoutesGet Bus StopsGet Bus Vehicle At StopGet Bus VehiclesGet Lirr FeedGet Metro North FeedGet Service AlertsGet StationsGet Subway FeedGet System Time
ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
MTA

What is the MTA MCP Server?

Connect your MTA API New York City public transit data platform to any AI agent and take full control of real-time NYC Subway and MTA Bus tracking, arrival predictions, LIRR and Metro-North commuter rail monitoring, and service disruption awareness through natural conversation.

What you can do

  • Subway Real-Time Feeds — Access live GTFS-RT data for all NYC Subway lines with train positions and arrival predictions
  • Bus Routes — List all MTA bus routes across Manhattan, Brooklyn, Queens, Bronx, and Staten Island
  • Bus Stops — Get all stops for any bus route with coordinates and sequence information
  • Bus Predictions — Get real-time estimated arrival times for any bus stop
  • Bus Vehicle Tracking — Track real-time GPS positions of all active MTA bus vehicles
  • Service Alerts — Monitor active disruptions across Subway, buses, LIRR, and Metro-North
  • Subway Stations — List all 472 NYC Subway stations with coordinates, borough, and entrance data
  • LIRR Tracking — Monitor Long Island Rail Road trains with real-time positions and arrivals
  • Metro-North Tracking — Track Metro-North Railroad trains serving northern NYC suburbs
  • Stop-Level Bus Monitoring — Monitor buses at specific stops with targeted arrival predictions
  • Estimated Arrivals — Get route-filtered arrival estimates for buses at any stop
  • System Connectivity — Verify API connectivity and synchronize timestamps

How it works

  1. Subscribe to this server
  2. Enter your MTA API key (free from the Developer Portal)
  3. Start tracking NYC transit from Claude, Cursor, or any MCP-compatible client

No more navigating multiple MTA apps or manually checking train and bus times. Your AI acts as a dedicated NYC transit analyst and trip planning assistant.

Who is this for?

  • NYC Commuters — track subway and buses, check arrivals, and monitor LIRR/Metro-North for daily commutes
  • Tourists — navigate the NYC Subway system with station discovery and real-time arrival awareness
  • Transit Analysts — research service patterns, vehicle positions, and system reliability across all MTA modes
  • Mobility Apps — integrate real-time MTA data into journey planning and transit tracking applications

Built-in capabilities (12)

get_bus_estimated_arrival

Returns predicted arrival times, route information, destinations, wait times, and delay indicators for each expected bus. Supports both multi-route stop queries and single-route filtered queries. Essential for targeted arrival predictions, route-specific wait time estimation, and passenger trip timing. AI agents should reference this when users ask "when is the next M15 at this stop", "show arrival estimates for route B46 at stop 12345", or need route-filtered arrival data at a specific bus stop. Get estimated arrival times for buses at a stop, optionally filtered by route

get_bus_predictions

Returns predicted arrival times, route IDs, destination information, expected wait times, and whether buses are on schedule or delayed. Based on real-time vehicle tracking and schedule adherence. Essential for real-time bus arrival awareness, passenger waiting time estimation, trip timing, and connection coordination. AI agents should reference this when users ask "when is the next M15 bus at stop 12345", "show predictions for this stop", or need real-time arrival data for a specific bus stop. Stop IDs can be found using get_bus_stops. Get next bus arrival predictions for a specific bus stop

get_bus_routes

Returns route IDs, route names, operators (MTA New York City Bus, MTA Bus Company, private operators under MTA contract), and service area information. Covers local, limited-stop, and Select Bus Service (SBS) routes. Essential for route discovery, service area analysis, transit network understanding, and identifying route IDs for use in stop and prediction queries. AI agents should reference this when users ask "list all bus routes in Manhattan", "what routes serve Brooklyn", or need to identify route IDs for subsequent MTA Bus Time queries. List all MTA bus routes in New York City

get_bus_stops

Returns stop IDs (MonitoringRef), stop names, geographic coordinates (latitude, longitude), stop sequence order, and direction information. Essential for stop discovery, journey planning, accessibility mapping, and identifying stop IDs for use in arrival prediction queries. AI agents should use this when users ask "list all stops on the M15", "find bus stops along Broadway", or need to identify stop IDs for use in get_bus_predictions queries. List all stops for a specific MTA bus route

get_bus_vehicle_at_stop

Returns vehicle IDs, route IDs, current positions, expected arrival times, distances from stop, and operational status. More targeted than system-wide vehicle queries. Essential for stop-level bus tracking, passenger waiting awareness, and real-time arrival estimation at specific stops. AI agents should use this when users ask "what buses are coming to this stop", "track vehicles approaching stop 12345", or need stop-specific bus position data for passenger information. Get buses currently at or approaching a specific bus stop

get_bus_vehicles

Returns vehicle IDs, route affiliations, latitude/longitude coordinates, heading direction, speed, recorded time, and prediction availability. Covers all MTA New York City Bus and MTA Bus Company vehicles in active service. Essential for real-time bus fleet monitoring, passenger arrival estimation, route-level service awareness, and transit operations management. AI agents should use this when users ask "where are all the buses right now", "track bus positions system-wide", or need real-time vehicle position data for fleet visualization. Get real-time positions of all active MTA bus vehicles

get_lirr_feed

Returns train positions, trip updates, scheduled vs. real-time arrivals at stations, delays, track information, and service disruptions across all LIRR branches including Babylon, Ronkonkoma, Hempstead, Port Jefferson, Montauk, and more. Essential for commuter rail tracking, arrival predictions at Penn Station and Grand Central Madison, and LIRR service monitoring. AI agents should reference this when users ask "when is the next LIRR train to Penn Station", "track LIRR train positions", or need real-time commuter rail data for trip planning from Long Island into NYC. Get real-time LIRR train data from the Long Island Rail Road

get_metro_north_feed

Returns train positions, trip updates, scheduled vs. real-time arrivals, delays, track information, and service disruptions across all Metro-North lines including Hudson, Harlem, New Haven, Port Jervis, Pascack Valley, and more. Essential for commuter rail tracking, arrival predictions at Grand Central Madison, and Metro-North service monitoring. AI agents should use this when users ask "when is the next Metro-North train from White Plains", "track Metro-North positions", or need real-time commuter rail data for trip planning from Westchester, Connecticut, or the Hudson Valley into NYC. Get real-time Metro-North Railroad train data

get_service_alerts

Returns alert descriptions, affected lines and stations, severity levels, cause types (maintenance, incident, weather, special events, construction), start and end timestamps, and alternative service recommendations. Essential for service disruption awareness, alternative route planning, passenger communication, and understanding system reliability. AI agents should use this when users ask "are there any delays on the 4/5/6 line", "is LIRR running normally", or need to check service reliability before planning MTA journeys. Get current service alerts and disruptions across the MTA system

get_stations

Returns station IDs, station names, complex IDs (for multi-line stations), borough information (Manhattan, Brooklyn, Queens, Bronx, Staten Island), structure types (underground, elevated, embankment, open cut), latitude/longitude coordinates, and North/East/South/West entrance coordinates. Essential for station discovery, rail network mapping, route planning, and identifying station codes for use in journey planning queries. AI agents should use this when users ask "list all stations in Manhattan", "what is the station code for Times Square", or need to understand the NYC Subway network geography. List all NYC Subway stations with details

get_subway_feed

Supports feed IDs grouped by line: "1" (lines 1,2,3,4,5,6,S), "2" (lines A,C,E), "3" (lines B,D,F,M), "4" (lines G), "5" (lines J,Z), "6" (lines N,Q,R,W), "7" (lines L), "11" (Staten Island Railway), "16" (Shuttle 42nd St), "21" (Shuttle Franklin Ave), "26" (Shuttle Rockaway Park). Returns train positions, trip updates, scheduled vs. real-time arrivals, delays, and service disruptions. Essential for real-time subway tracking, arrival predictions, and service monitoring across the entire NYC Subway system. AI agents should use this when users ask "when is the next 1 train", "show real-time positions for the A line", or need live subway data for trip planning. Feed IDs are required and can be found in MTA documentation. Get real-time subway feed data for specific NYC Subway lines

get_system_time

Returns the official server timestamp in ISO 8601 format. Useful for synchronizing local clocks with the MTA system, verifying API connectivity, testing authentication, and timestamp alignment for real-time data correlation. AI agents should use this as a connectivity check before making more complex queries, or when users need to verify API responsiveness and authentication validity. Get the current MTA Bus Time system timestamp

Why LlamaIndex?

LlamaIndex agents combine MTA tool responses with indexed documents for comprehensive, grounded answers. Connect 12 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

  • Data-first architecture: LlamaIndex agents combine MTA tool responses with indexed documents for comprehensive, grounded answers

  • Query pipeline framework lets you chain MTA tool calls with transformations, filters, and re-rankers in a typed pipeline

  • Multi-source reasoning: agents can query MTA, a vector store, and a SQL database in a single turn and synthesize results

  • Observability integrations show exactly what MTA tools were called, what data was returned, and how it influenced the final answer

L
See it in action

MTA in LlamaIndex

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Enterprise Security

Why run MTA with Vinkius?

The MTA connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 12 tools are ready to work instantly without any complex setup.

You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

View full MTA details →
MTA
Fully ManagedNo server setup
Plug & PlayNo coding needed
SecurePrivacy protected
PrivateYour data is safe
Cost ControlBudget limits
Control1-click disconnect
Auto-UpdatesMaintenance free
High SpeedOptimized for AI
Reliable99.9% uptime
Your credentials and connection tokens are fully encrypted

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure

01 / Catalog

Over 4,000 integrations ready for AI agents

Explore a vast library of pre-built integrations, optimized and ready to deploy.

02 / Credentials

Connect securely in under 30 seconds

Generate tokens to authenticate and link external services in a single step.

03 / Guardian

Complete visibility into every agent action

Audit live requests, latency, success rates, and active security compliance policies.

04 / FinOps

Optimize spending and track token ROI

Analyze real-time token consumption and cost metrics detailed by connection.

Over 4,000 integrations ready for AI agents
Connect securely in under 30 seconds
Complete visibility into every agent action
Optimize spending and track token ROI

Explore our live AI Agents Analytics dashboard to see it all working

This dashboard is included when you connect MTA using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.

Why Vinkius

MTA and 4,000+ other AI tools. No hosting, no code, ready to use.

Professionals who connect MTA to LlamaIndex through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.

4,000+MCP Integrations
<40msResponse time
100%Fully managed
Raw MCP
Vinkius
Ready-to-use MCPsFind and configure each manually4,000+ MCPs ready to use
Connection SetupManual coding & server setup1-click instant connection
Server HostingYou host it yourself (needs 24/7 uptime)100% hosted & managed by Vinkius
Security & PrivacyStored in plaintext config filesBank-grade encrypted vault
Activity VisibilityBlind execution (no logs or tracking)Live dashboard with real-time logs
Cost ControlRunaway AI token spend riskAutomatic budget limits
Revoking AccessMust delete files or code to stop1-click disconnect button
The Vinkius Advantage

How Vinkius secures MTA for LlamaIndex

Every request between LlamaIndex and MTA is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can my AI check when the next subway train is arriving at my station?

Yes! Use the get_subway_feed tool with the appropriate feed ID for your line. Feed IDs are grouped: "1" covers lines 1,2,3,4,5,6,S; "2" covers A,C,E; "3" covers B,D,F,M; "4" is G; "5" is J,Z; "6" covers N,Q,R,W; "7" is L; "11" is Staten Island Railway. This returns real-time GTFS-RT data with train positions, trip updates, scheduled vs. real-time arrivals, and delay information. For station-level predictions, combine with get_stations to find your station code first.

02

How do I check when the next MTA bus is arriving at a specific stop?

First use get_bus_stops with a route ID to find the stop ID (MonitoringRef) for your location. Then use get_bus_predictions with that stop ID to get real-time estimated arrival times, route information, destinations, and delay indicators. For more targeted predictions, use get_bus_estimated_arrival which allows filtering by both stop ID and route ID. Stop IDs are numeric identifiers assigned by MTA to each physical bus stop across NYC.

03

Are there any service disruptions affecting my subway line or bus route right now?

Use get_service_alerts to check all active service disruptions across the MTA system. This returns alerts with affected lines and stations, disruption descriptions, severity levels, cause types (maintenance, incident, weather, special events, construction), start and end timestamps, and alternative service recommendations. Covers NYC Subway, buses, LIRR, and Metro-North. Always check this before planning any journey to ensure you are aware of delays, planned work, or service changes.

04

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.

05

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query MTA tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.

06

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

07

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Explore More MCP Servers

View all →