# swisstransport [Health: Active]

**Category:** 🚆 Travel & Transportation  
**Repository:** https://github.com/pipeworx-io/mcp-swisstransport  
**GitHub Stars:** 0  
**npm Downloads (last month):** 394  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/swisstransport

## Description
Swiss Transport MCP — wraps Transport Open Data API (free, no auth)

## Tools
Capabilities this server exposes over MCP:

- **search_stations** — Search for Swiss public transport stations (train, bus, tram) by name query.
- **get_connections** — Get public transport connections between two Swiss locations. Returns up to the requested number of next departures.
- **get_stationboard** — Get the live departure board for a Swiss public transport station.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "swisstransport": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-swisstransport"]
  }
}
```

## Documentation

## What swisstransport does

The swisstransport MCP server exposes Swiss public transport data through three MCP tools. `search_stations` finds train, bus, and tram stations from a name query. `get_connections` retrieves upcoming public transport journeys between two Swiss locations, with a caller-selected limit on the number of departures. `get_stationboard` returns the live departure board for a station.

This fits agents that need to answer questions about Swiss station names, next departures, routes between locations, or current departures from a specific stop. The underlying Transport Open Data API is free and does not require authentication.

## How it works

There are two connection modes. The hosted MCP endpoint is available at `https://gateway.pipeworx.io/swisstransport/mcp`. Add that URL to an MCP client that supports remote MCP connections, such as Claude Desktop, Cursor, or Windsurf.

The hosted endpoint is a scoped Pipeworx gateway connection. Its `tools/list` response includes the three transport tools and shared Pipeworx meta-tools, so the total listed tool count is larger than the transport-specific set. The gateway’s `initialize` response reports the exact scope. Shared routing through `ask_pipeworx` can reach other sources in the Pipeworx catalog without adding another MCP server.

The same gateway also provides a full endpoint at `https://gateway.pipeworx.io/mcp`. The full endpoint lists tools from all available packs directly, while the scoped endpoint lists the swisstransport tools directly. Both use the same gateway and data sources.

## Setup and configuration

For a hosted setup, register the scoped endpoint in the client’s MCP configuration:

```json
{
  "mcpServers": {
    "swisstransport": {
      "url": "https://gateway.pipeworx.io/swisstransport/mcp"
    }
  }
}
```

The package also runs as a local stdio server without a Pipeworx account:

```json
{
  "mcpServers": {
    "swisstransport": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-swisstransport"]
    }
  }
}
```

Run `npx -y @pipeworx/mcp-swisstransport` directly to confirm that the local process starts. The local process communicates through stdin and stdout and does not require gateway access.

## Tools and capabilities

- `search_stations`: search Swiss train, bus, and tram stations by name.
- `get_connections`: request upcoming connections between two Swiss locations.
- `get_stationboard`: retrieve live departures for a Swiss station.
- Hosted HTTP access: call tools through the Pipeworx gateway, including direct HTTP requests such as `POST /v1/tools/swisstransport_search_stations`.
- Natural-language routing: use the gateway’s `ask_pipeworx` meta-tool to ask questions instead of selecting a tool and filling its arguments manually.

## Limitations and notes

The hosted endpoint currently includes shared gateway meta-tools in addition to the transport tools. There is no supported way to remove those tools from a scoped gateway connection. If their schemas consume more context than desired, use one full gateway connection rather than several pack endpoints, or run the standalone package.

The local swisstransport MCP server exposes only its own three tools and does not provide `ask_pipeworx` routing. Hosted and local modes use the same source and transport tool set, but the hosted mode adds gateway functionality.

_Full upstream README: https://allmcps.com/mcp/swisstransport/readme_