`stop_search`

Pack: tfl · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/stop_search for the schema, then POST the same URL with its arguments for the data.

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.

Parameters

Name	Type	Required	Description
`query`	string	yes	Stop/station name to search for, e.g. “Oxford Circus”.
`modes`	string	no	Optional filter.

Example call

Arguments

{
  "query": "Oxford Circus"
}

curl

curl -X POST https://gateway.pipeworx.io/tfl/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"stop_search","arguments":{"query":"Oxford Circus"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('stop_search', {
  "query": "Oxford Circus"
});

More examples

{
  "query": "King's Cross",
  "modes": "tube,national-rail"
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Connect to just the tfl pack

{
  "mcpServers": {
    "tfl": {
      "url": "https://gateway.pipeworx.io/tfl/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

stop_search