mcp-tfl-journey
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TFL_API_KEY | No | Your TFL API key. Get it from https://api-portal.tfl.gov.uk/signup | 6674e72d9f3d4678a3539ffbb24d5c92 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_journeyC | Search for journey information between two TfL stations |
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 1 tool
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is unique.
The single tool uses a clear verb_noun pattern (search_journey), establishing a consistent naming convention by default.
One tool is too few for a journey planning domain, which typically requires multiple operations like station lookup or route details.
The tool surface is severely limited, covering only journey search and missing other essential TfL operations such as station information or service status updates.