Trafikverket MCP Server
Related Servers
Alternatives to Trafikverket MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables querying Swiss public transport data (stations, departures, connections) from the Transport Open Data API via natural language through an MCP gateway.312 npmMIT
- AlicenseAqualityCmaintenanceProvides real-time access to Swedish road weather, traffic cameras, road conditions, and traffic flow data from Trafikverket (Swedish Transport Administration). Enables users to query weather stations, cameras, traffic situations, and flow data through natural language.10MIT
- AlicenseAqualityDmaintenanceProvides access to Deutsche Bahn's timetable data through MCP, enabling real-time train schedules, station search, and change tracking for German railway stations.467 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to access Swiss public transport data including journey planning, real-time departures, disruptions, occupancy forecasts, ticket prices, and train formations via a standardized MCP interface.117MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to query Taiwan's TDX transport data for YouBike availability, bus routes and live arrivals, and high speed rail, Taiwan Railway, metro and Alishan timetables, seat availability, fares and service alerts. A generic endpoint tool also reaches any other TDX API path.50175 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to query Dutch Railways (NS) travel information using an NS API key, including journey planning, live departure and arrival boards, disruptions and engineering works, fares, train composition and crowding, and station facilities. Responses come as compact JSON with a short text summary, and access should be restricted to localhost or an authenticating gateway.29,911 npmMIT
TDQS
Scored across 8 tools
Each tool targets a distinct data source and clearly separates superficially similar concepts: get_railway_events (raw internal event registry) vs get_train_messages (public disruption text) vs get_train_announcements (per-train timetable/delays), with explicit 'use X instead' cross-references in the descriptions. Road tools (situations vs weather) and replacement traffic are likewise unambiguous, and search_stations is clearly the lookup helper for the train tools.
Seven of eight tools follow a strict get_<resource>_<noun> snake_case pattern with consistent resource grouping (train_*, road_*). The single deviation, search_stations, is a conventional, readable choice for a lookup operation rather than an inconsistency.
Eight tools is a well-scoped set for a national transport data API, with each tool mapping to one coherent data domain (rail events, positions, replacement traffic, road incidents, road weather, announcements, messages, station lookup). No tool appears redundant or padded.
The live rail and road information surface is strong, including the station lookup needed to resolve ambiguous names. However, there are no tools for road traffic flow/volumes, weather forecasts, planned timetables/routes for a given train number, or ferry/other Trafikverket modes, leaving some natural follow-up questions unanswered.