London Transit
by bibokaram
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Optional. Listening port, default 3000. | 3000 |
| DATA_DIR | No | Optional. A writable directory on persistent storage for owner.json (saved places, preferences, followed journeys). Unset, they live in memory and are lost on restart. | |
| RTT_TOKEN | No | Optional. Realtime Trains API token from https://api-portal.rtt.io: enables live departures for every National Rail operator, calling_at and train_service. | |
| MCP_SECRET | Yes | Enables /mcp and is the secret typed at the OAuth login: at least 32 random characters (openssl rand -hex 32). Unset or too short, /mcp returns 404. | |
| PUBLIC_URL | No | Required off Railway. The public origin, e.g. https://tube.example.com, used in OAuth URLs. On Railway it is read from RAILWAY_PUBLIC_DOMAIN. | |
| TFL_APP_KEY | No | Recommended. TfL API key from https://api-portal.tfl.gov.uk (the "500 Requests per min" product). Stays on the server. Without it, TfL requests are keyless and rate limited. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues