Tripgo MCP Server

What the skedgo/tripgo-mcp-server MCP server does

The skedgo/tripgo-mcp-server MCP server connects MCP clients to selected TripGo API functions. It supports mixed-mode and multimodal journey planning, transport-related location lookup, departures from a specified public-transport stop, and retrieval of a URL for a trip previously created through routing.

The hosted service is intended for clients that can connect to a remote MCP endpoint. Its deployment target is Cloudflare Workers, and the published endpoint is https://tripgo-mcp-server.skedgo-account.workers.dev/mcp.

How it works

An MCP client connects to the hosted endpoint and discovers the available TripGo tools. The routing tool calculates a trip across supported transport modes. After a route has been calculated, the trip URL tool can return a URL for that previously calculated trip.

The locations tool retrieves transport-related locations, while the departures tool provides departures from a particular public-transport stop. The README does not specify the complete parameter schema, supported geographic coverage, transport modes, or response format for these tools, so those details should be confirmed from the live tool definitions or TripGo documentation.

The skedgo/tripgo-mcp-server MCP server can also be run locally for development. In that mode, the project starts a local endpoint at http://localhost:8787/mcp according to the example client configuration.

Setup and configuration

For normal use, connect an MCP client directly to the hosted endpoint. Claude Desktop can access the service through the mcp-remote proxy, using the hosted MCP URL as the proxy argument. The README specifically documents Claude Desktop configuration and instructs users to restart the application after updating its configuration.

Local development requires a copy of .env.example renamed to .env, with an API key set in that file. The documented development commands are:

npm install
npm run dev:local

The project can be deployed locally with npm install followed by npm run deploy. The provided material does not identify the API-key environment variable by name, so it should not be added to an automated configuration without checking the repository files.

Tools and capabilities

• tripgo-routing: Plan mixed and multimodal trips.
• tripgo-get-trip-url: Retrieve the URL for a trip calculated with tripgo-routing.
• tripgo-locations: Find transport-related locations.
• tripgo-departures: Get departures from a specific public-transport stop.

Limitations and notes

The skedgo/tripgo-mcp-server MCP server is documented as a remote service, not as a package with a standalone install command. The README provides a Claude Desktop connection through mcp-remote, but does not describe native configuration steps for other MCP clients.

The available material does not state pricing, rate limits, authentication details for the hosted endpoint, geographic availability, supported transport operators, or the exact API-key variable name. It also does not provide tool argument or return-value specifications beyond the capabilities listed above. Treat those as unknown until verified against the repository or the live MCP tool schemas.