
Pulls live satellite tracking data through Two-Line Element sets from tle.ivanstanojevic.me, no authentication required. Part of the Pipeworx gateway ecosystem, which aggregates 250+ data sources behind a single MCP interface. You can either call TLE tools directly or use the ask_pipeworx natural language interface to query satellite positions and orbital data without manually structuring requests. Runs over streamable HTTP, so no local process needed. Reach for this when you're building agents that need real-time orbital mechanics data for tracking satellites, calculating passes, or working with space situational awareness without managing API keys or rate limits.
TLE MCP — satellite tracking via Two-Line Element sets (tle.ivanstanojevic.me, free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_tle | Fetch the Two-Line Element (TLE) set for a specific satellite by its NORAD catalog ID. Returns the satellite name, epoch date, and both TLE lines. |
search_satellites | Search for satellites by name or keyword. Returns matching satellites with their NORAD IDs and TLE data. |
list_recent | List the newest satellites in the NORAD catalog, highest catalog number first. NORAD ids are assigned in roughly launch order, so this approximates most-recently-launched. Note this orders by catalog entry, not by TLE epoch — the upstream offers no epoch-date sort. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"tle": {
"url": "https://gateway.pipeworx.io/tle/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/tle/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Tle data" })
The gateway picks the right tool and fills the arguments automatically.
MIT