MCP Server for Netherlands NS Trains

mcp-name: ns-bridge

A Model Context Protocol (MCP) server that enables AI assistants to interact with the Netherlands Railways (NS) API for route planning, pricing, and real-time departure information.

Compatible with any MCP client, including Claude Desktop, custom implementations, and AI agent frameworks.

Features

MCP Tools

1. search_stations - Find train stations by name or country

   • Search by station name

   • Filter by country code

   • Returns station codes needed for trip planning

2. search_trips - Plan routes between stations

   • Get multiple trip options with connections

   • View detailed leg-by-leg journey information

   • See pricing with discount options

   • Choose travel class (1st or 2nd)

   • Search by departure or arrival time

3. get_departures - View real-time departure boards

   • See upcoming departures from any station

   • Track delays and cancellations

   • Monitor platform changes

MCP Resources

• station://{code} - Get detailed information about a specific station

Installation

Prerequisites

• NS API key from NS API Portal

• Choose one installation method:

  • Docker (easiest - no Python installation needed)

  • uv (recommended for development)

  • pip (traditional Python workflow)

Option 1: Docker (Easiest)

Prerequisites: Docker Desktop or Docker Engine

Then configure your MCP client (see Usage section below for configuration examples).

For detailed Docker usage, troubleshooting, and advanced options, see DOCKER.md.

Option 2: Setup with uv (Recommended for Development)

Option 3: Setup with pip

Getting an NS API Key

1. Go to NS API Portal

2. Create an account

3. Subscribe to the following APIs:

   • Reisinformatie API (Travel Information)

   • NS-APP Stations API

4. Copy your subscription key

5. Add it to your .env file as NS_API_KEY

Usage

Running the MCP Server

Development Mode (with Inspector)

This opens the MCP Inspector for interactive testing.

Configuring MCP Clients

This server works with any MCP-compatible client. Below are configuration examples for popular clients.

Claude Desktop

Automatic Installation:

This will automatically configure Claude Desktop to use your MCP server.

Manual Configuration:

Add to your Claude Desktop config file (location varies by OS):

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

Linux: ~/.config/Claude/claude_desktop_config.json

For Docker installation:

Note: The -e NS_API_KEY in the args array tells Docker to pass the environment variable from the host (set by the env section) into the container. Without this, the API key won't be available inside Docker.

For uv installation:

After updating the configuration, restart your MCP client to load the server.

Other MCP Clients

For other MCP-compatible clients (custom implementations, AI agent frameworks, etc.), refer to your client's documentation for stdio server configuration. The server accepts standard MCP protocol messages via stdin/stdout.

Example Queries

Once configured, you can ask your AI assistant:

• "What trains are departing from Utrecht Centraal in the next hour?"

• "Find me a train from Amsterdam to Rotterdam tomorrow at 9 AM"

• "What's the fastest route from Den Haag to Groningen?"

• "How much does a first-class ticket from Eindhoven to Maastricht cost?"

• "Show me stations near the German border"

Development

Project Structure

Developer Tools

This project uses modern Python development tools for code quality:

Pre-commit Hooks

Pre-commit hooks automatically check your code before each commit:

• General checks: Trailing whitespace, EOF fixes, YAML/TOML validation

• Ruff: Fast linting and code formatting

• MyPy: Static type checking

• Bandit: Security vulnerability scanning

Code Formatting & Linting

You can also run tools manually:

See DEVELOPER_TOOLS.md for detailed documentation on each tool and why we use them.

Testing

• pytest: Test framework

• pytest-asyncio: Async test support

• pytest-cov: Code coverage

• pytest-httpx: HTTP mocking for API tests

Run tests:

Virtual Environment Note

Yes, uv is compatible with virtual environments! uv automatically creates and manages a .venv directory in your project. You can activate it manually if needed:

However, uv run automatically uses the virtual environment, so activation is optional for most tasks.

API Documentation

NS API Endpoints Used

1. Stations API (/nsapp-stations/v2)

   • Search and list train stations

   • Filter by country

2. Trips API (/reisinformatie-api/api/v3/trips)

   • Route planning with connections

   • Pricing information

   • Support for via stations

3. Departures API (/reisinformatie-api/api/v2/departures)

   • Real-time departure information

   • Delay and cancellation tracking

Station Codes

Common station codes:

• ut - Utrecht Centraal

• asd - Amsterdam Centraal

• rtd - Rotterdam Centraal

• gvc - Den Haag Centraal

• ehv - Eindhoven Centraal

• nm - Nijmegen

• gn - Groningen

Use the search_stations tool to find more station codes.

Contributing

Suggestions and improvements are welcome!

Development Workflow

1. Create a feature branch

2. Make your changes

3. Run the test suite: uv run pytest

4. Pre-commit hooks will automatically run on commit (or run manually: uv run pre-commit run)

5. Submit a pull request

Note: Pre-commit hooks automatically handle formatting, linting, type checking, and security scanning.

License

MIT License - see LICENSE file for details

Acknowledgments

• Model Context Protocol - Anthropic's MCP specification

• NS API - Netherlands Railways API

• FastMCP - Python MCP SDK

Roadmap

Future enhancements planned:

• Add support for disruptions API

• Include station facilities information

• Add journey details (crowdedness predictions)

• Support for international routes

• Caching for frequently accessed data

• Rate limiting to respect API quotas