Side-by-Side Model Context Protocol Comparison
️ Not for Production Use! vs Tfl
In-depth architectural comparison of the ️ Not for Production Use! and Tfl MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
️ Not for Production Use!
Developer Tools · Local stdio
Quality: 37/100 (Fair) | Auth: No auth required
Tfl
Developer Tools · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose ️ Not for Production Use! if you need specialized Developer Tools tools running via a local process. Choose Tfl if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose ️ Not for Production Use! when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
T
Choose Tfl when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer remote streaming HTTP/SSE transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: line_status, stop_search, arrivals.
Feature & Specification Comparison
Tools & Capabilities Breakdown
️ Not for Production Use! Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
Tfl Tools (6)
line_status
Current service status for London transport lines. Pass either a comma-separated list of modes (e.g. "tube,dlr") OR a specific lineId (e.g. "victoria", "central"). Returns each line with lineStatuses + statusSeverityDescription (e.g. "Good Service", "Minor Delays").
stop_search
Search for stops/stations by name. Returns matches with a naptanId (the "id" field) used by the arrivals tool, plus modes, zone, and lat/lon.
arrivals
Real-time predicted arrivals at a stop. Pass the naptanId from stop_search (e.g. "940GZZLUOXC"). Results are sorted by timeToStation (seconds away), nearest first.
plan_journey
Plan a journey across London transport. from/to may be stop names, postcodes, or "lat,lon" coordinates. Returns journey options (legs, durations, modes). If a location is ambiguous, the API returns disambiguation options instead of journeys — refine the input or use a naptanId/coords.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
️ Not for Production Use! Configuration
Tfl Configuration