line_status — Tfl MCP Tool
line_status
(line status) is one of 50 tools on the
Tfl
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call line_status from your client
- Claude Code Tfl line_status run in your project directory
- Claude Desktop Tfl line_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Tfl line_status ~/.cursor/mcp.json
- VS Code Tfl line_status .vscode/mcp.json
- Zed Tfl line_status ~/.config/zed/settings.json
- Windsurf Tfl line_status ~/.codeium/windsurf/mcp_config.json
- Cline Tfl line_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Tfl line_status ~/.gemini/settings.json
- Grok Tfl line_status .mcp.json (in your project root)
- ChatGPT Tfl line_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Tfl line_status Settings → Connectors → Add custom connector
- LangChain Tfl line_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http tfl https://gateway.pipeworx.io/tfl/mcpOther tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- company_register_search
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- prediction_calibration
- updown_venue_compare
- updown_divergence_rate
- archive_evidence
- archive_compare
- research_row
- classify_row
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- stop_search
- arrivals
- plan_journey
- bike_points
- disruptions
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.