Transitous MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port | 3000 |
| MCP_API_KEY | No | Protects the MCP endpoint (recommended for HTTP) | |
| MCP_TRANSPORT | No | Set 'http' for remote deployment | stdio |
| MCP_ALLOWED_ORIGINS | No | Comma-separated browser origins | |
| TRANSITOUS_BASE_URL | No | Upstream base URL | https://api.transitous.org |
| TRANSITOUS_USER_AGENT | Yes | App name/version/contact required by Transitous | |
| MCP_REQUESTS_PER_MINUTE | No | Per-IP inbound HTTP limit | 60 |
| TRANSITOUS_REQUESTS_PER_MINUTE | No | Per-process uncached upstream safety limit | 20 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_locationsA | Find Transitous stop IDs and coordinates for a station or stop name. Read-only. Usage warning: Transitous is a volunteer-run, best-effort service intended for FOSS and non-profit use. Use a descriptive User-Agent with contact details, cache results, avoid heavy traffic, and contact Transitous before resource-intensive or commercial use. Policy: https://transitous.org/api/ |
| search_connectionsA | Plan public transport journeys between two station names using Transitous/MOTIS. Returns legs, transfers, times, available realtime status, tracks, and accessibility fields. It does not sell tickets or guarantee accuracy. Usage warning: Transitous is a volunteer-run, best-effort service intended for FOSS and non-profit use. Use a descriptive User-Agent with contact details, cache results, avoid heavy traffic, and contact Transitous before resource-intensive or commercial use. Policy: https://transitous.org/api/ |
| search_api_actionsA | Search or list the complete allowlisted Transitous/MOTIS API action catalog. Returns action IDs, methods, paths, accepted query/body fields, and resource-intensity flags for use with execute_api_action. Read-only. API documentation: https://transitous.org/api/ OpenAPI: https://github.com/motis-project/motis/blob/v2.10.2/openapi.yaml Usage warning: Transitous is a volunteer-run, best-effort service intended for FOSS and non-profit use. Use a descriptive User-Agent with contact details, cache results, avoid heavy traffic, and contact Transitous before resource-intensive or commercial use. |
| execute_api_actionA | Execute one read-only operation from the allowlisted Transitous/MOTIS action catalog. Supports every documented GET and computational POST operation; arbitrary URLs and undocumented parameters are rejected. Use search_api_actions to obtain the action ID and parameter fields. Large responses may be truncated. API documentation: https://transitous.org/api/ OpenAPI: https://github.com/motis-project/motis/blob/v2.10.2/openapi.yaml Usage warning: Transitous is a volunteer-run, best-effort service intended for FOSS and non-profit use. Use a descriptive User-Agent with contact details, cache results, avoid heavy traffic, and contact Transitous before resource-intensive or commercial use. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: discovering actions (search_api_actions), executing them (execute_api_action), planning journeys (search_connections), and finding locations (search_locations). No overlap in functionality.
All tool names follow a consistent verb_noun pattern (search_api_actions, execute_api_action, search_connections, search_locations). The naming is predictable and intuitive.
Four tools is well-scoped for a transit API server. Each tool covers a core operation: discovery, execution, journey planning, and location lookup. No unnecessary tools, and no missing essential categories.
The tool set provides a flexible generic action executor (execute_api_action) that can handle any read-only API endpoint, plus convenience tools for common tasks (search_connections, search_locations). Minor gap: no dedicated departure/arrival board tool, but that can be achieved via execute_api_action.