Reported issues for tfl-mcp-server

Pod holds 16 of 19 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to tfl-mcp-server.

Most discussed

feat(node): add MCP Apps UI for service_status

Goal

Add a first MCP Apps / MCP-UI experience to the Node.js implementation by attaching a static UI to the existing service_status tool. The UI should be a progressive enhancement: compatible hosts can render it, while all hosts continue to receive the current text response.

Scope

• Target the Node.js MCPB implementation first (node/), not Java parity.
• Attach UI metadata to the existing service_status tool instead of adding a separate *_ui tool.
• Use the recommended MCP Apps

Read the thread · 2026-05-07 · closed · 1 comment

Prepare submission form content (server basics, tools, compliance)

Submission Form Preparation

Prepare all content needed for the connectors directory submission form:

• Server basics: name, URL, tagline, description, use cases
• Connection details: auth type, transport protocol, read/write capabilities
• Data & compliance: data handling practices, third-party connections (TfL API), health data access (none), category (transport/travel)
• Full tool list with human-readable names
• Submission path: [Desktop extension form](http://clau.de

Read the thread · 2026-03-25 · closed · 1 comment

Ensure contract tests pass: ./gradlew contractTest

Testing & Launch Readiness (Required)

Ensure contract tests pass: ./gradlew contractTest

Fix any failures before submission.

Part of the Anthropic Connectors Directory submission checklist.

Read the thread · 2026-03-25 · closed · 1 comment

End-to-end test: server as remote MCP (HTTP/SSE transport)

Testing & Launch Readiness (Required)

Test the server as a remote MCP using HTTP/SSE transport and verify connectivity and all tools work.

• Start server with SSE transport
• Connect via MCP client over HTTP
• Verify all tools respond correctly

Document any issues found.

Part of the Anthropic Connectors Directory submission checklist.

Read the thread · 2026-03-25 · closed · 1 comment

End-to-end test: all 9 tools in Claude Desktop (stdio transport)

Testing & Launch Readiness (Required)

Test the server in Claude Desktop using stdio transport and verify all 9 tools work end-to-end:

• line_status
• arrivals
• stop_search
• disruptions
• journey
• bike_points
• list_modes
• air_quality
• road_disruptions

Document any issues found.

Part of the Anthropic Connectors Directory submission checklist.

Read the thread · 2026-03-25 · closed · 1 comment

Prepare promotional screenshots showing server in action with Claude

Branding (Required)

Prepare promotional screenshot(s) showing the MCP server in action with Claude.

• Show example queries and responses (e.g. line status, journey planning, arrivals)
• Capture from Claude Desktop or similar MCP client
• High quality, suitable for directory listing

Part of the Anthropic Connectors Directory submission checklist.

Read the thread · 2026-03-25 · closed · 1 comment

Document step-by-step TfL API key setup and verification instructions

Documentation & Support (Required)

Prepare step-by-step test account instructions:

1. How to get a TfL API key at https://api-portal.tfl.gov.uk/
2. How to configure the server with the key via TFL_APP_KEY env var
3. How to verify the server is working correctly
4. Note: works without a key at lower rate limits

Part of the Anthropic Connectors Directory submission checklist.

Read the thread · 2026-03-25 · closed · 1 comment

Determine submission category: Desktop extension vs Remote MCP

Authentication (Required — assess applicability)

Determine the submission category:

• Remote MCP: Assess whether OAuth 2.0 is needed for the server's own client auth (separate from TfL API key). TfL uses a simple API key model, not OAuth.
• Desktop extension (MCPB): Document that the TfL API key is optional and supplied via environment variable — no OAuth flow needed.

Decision will determine which submission form to use:

• [Desktop extension form](http://clau.de/desktop-extention-s

Read the thread · 2026-03-25 · closed · 1 comment

Most recent

Migrate to MCP 2026-07-28 and consolidate on Node.js for v2.0.0

Summary

Migrate the TfL MCP Server to the 2026-07-28 Model Context Protocol revision and ship the result as the breaking 2.0.0 release.

This migration will consolidate the project on Node.js/TypeScript, retire the Java implementation, and provide modern-only MCP over both stdio and Streamable HTTP. Existing TfL tool behavior and the service_status MCP App must remain intact.

Context

The repository currently has two implementations:

• Node.js uses @modelcontextprotocol/sdk 1.x

Read the thread · 2026-08-09 · open · 0 comments

Rename project to tfl-mcp-server

Context

The project is currently named mcp-server-tfl across the repository, package metadata, Docker image references, MCP server metadata, documentation, and release examples.

Proposal

Rename the project to tfl-mcp-server consistently across the codebase and published surfaces.

Why

• Puts the domain first: people looking for TfL tooling are more likely to scan for tfl first.
• Makes the project easier to discover as a TfL-specific MCP server while still preserving the MCP s

Read the thread · 2026-05-07 · closed · 0 comments

Review and confirm compliance with Anthropic Software Directory Terms and Policy

Compliance & Policy (Required)

Review and confirm compliance with:

• Anthropic Software Directory Terms
• Anthropic Software Directory Policy
• Confirm commitment to maintain security, respond to issues promptly, and provide accurate descriptions

Part of the [Anthropic Connectors Directory](https://docs.anthropic.com/en/

Read the thread · 2026-03-25 · closed · 0 comments

Create server logo (SVG)

Branding (Required)

Create a server logo in SVG format.

• SVG preferred
• Consider a TfL roundel-inspired icon (be mindful of TfL trademark)
• Should work at various sizes (favicon, README header, directory listing)

Part of the Anthropic Connectors Directory submission checklist.

Read the thread · 2026-03-25 · closed · 0 comments

Document all 9 tools with human-readable names and descriptions

Documentation & Support (Required)

Document all 9 tools with human-readable names and descriptions.

• Ensure docs/tools.md is comprehensive and matches submission form fields
• Cover all 9 tools: line_status, arrivals, stop_search, disruptions, journey, bike_points, list_modes, air_quality, road_disruptions
• Include: tool name, description, parameters, example usage, example response

Part of the [Anthropic Connectors Directory](https://docs.anthropic.com/en/docs/connec

Read the thread · 2026-03-25 · closed · 0 comments

Add Getting Started / setup instructions to README

Documentation & Support (Required)

Add clear "Getting Started" / setup instructions to README.md aimed at a first-time reviewer unfamiliar with the project.

Should cover:

• Prerequisites (Java 25, Gradle)
• How to build the project
• How to run the server
• How to configure the TfL API key (optional, via TFL_APP_KEY env var)
• How to connect to the server from an MCP client (e.g. Claude Desktop)

Part of the [Anthropic Connectors Directory](https://docs.anthropic.com/en/docs/connectors/

Read the thread · 2026-03-25 · closed · 0 comments

Host privacy policy at a stable HTTPS URL

Privacy Policy (Required for local connectors)

Host the privacy policy at a stable HTTPS URL.

Options:

• GitHub Pages
• Raw GitHub URL (e.g. https://raw.githubusercontent.com/oneill9/mcp-server-tfl/main/PRIVACY.md)

The URL must be stable and publicly accessible for the connectors directory submission.

Part of the Anthropic Connectors Directory submission checklist.

Read the thread · 2026-03-25 · closed · 0 comments

Add privacy_policies array to server.json manifest

Privacy Policy (Required for local connectors)

Add privacy_policies array with HTTPS URL(s) to server.json manifest (manifest_version 0.2+).

Example:

{
  "manifest_version": "0.2",
  "privacy_policies": ["https://..."]
}

Depends on hosting the privacy policy at a stable HTTPS URL (see related issue).

Part of the Anthropic Connectors Directory submission checklist.

Read the thread · 2026-03-25 · closed · 0 comments

The remaining reports are on the project's issue tracker.