# tle [Health: Active]

**Category:** 🚀 Aerospace & Astrodynamics  
**Repository:** https://github.com/pipeworx-io/mcp-tle  
**GitHub Stars:** 0  
**npm Downloads (last month):** 453  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/tle

## Description
TLE MCP — satellite tracking via Two-Line Element sets (tle.ivanstanojevic.me, free, no auth)

## Tools
Capabilities this server exposes over MCP:

- **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.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "tle": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-tle"]
  }
}
```

## Documentation

## What the tle MCP server does

The tle MCP server exposes satellite catalog queries through the Model Context Protocol. Its data source is tle.ivanstanojevic.me, described as free and requiring no authentication. The server returns Two-Line Element sets, which include the two orbital-data lines used by compatible tracking and propagation software.

Use `get_tle` when the NORAD catalog ID is already known. The result includes the satellite name, the TLE epoch date, and both TLE lines. Use `search_satellites` when an agent needs to find satellites from a name or keyword; matches include NORAD IDs and TLE data. `list_recent` returns entries with the highest NORAD catalog numbers first.

## How it works

The tle MCP server can be connected as a remote MCP endpoint at `https://gateway.pipeworx.io/tle/mcp`. The gateway exposes this pack's three satellite tools along with shared Pipeworx meta-tools. A connection's `initialize` response is the authoritative source for the tools available at that time.

The same gateway also exposes an HTTP tool interface. For example, callers can send a JSON POST request to `https://gateway.pipeworx.io/v1/tools/get_tle` with a `norad_id` value.

A local package is also available through `@pipeworx/mcp-tle`. In standalone mode it communicates over stdin and stdout and exposes only the satellite tools, without the gateway's shared meta-tools or cross-catalog routing.

## Setup and configuration

For a remote connection, add the gateway URL under an MCP server named `tle` in a compatible client. For local use, configure the client to run `npx -y @pipeworx/mcp-tle` as the command. Running that command directly can verify that the package starts and speaks MCP over stdin/stdout.

No environment variables or account credentials are documented as required. The remote endpoint and the local package use the same source and provide the same pack-specific tools.

## Tools and capabilities

- `get_tle`: Retrieves a named satellite's epoch and two TLE lines from its NORAD catalog ID.
- `search_satellites`: Finds matching satellites using a name or keyword and returns their IDs and TLE data.
- `list_recent`: Lists satellites by descending NORAD catalog number.

## Limitations and notes

`list_recent` is an approximation of recent launches, not a launch-date or TLE-age query. NORAD identifiers are assigned in roughly launch order, so higher IDs generally indicate newer catalog entries. The upstream source does not provide sorting by TLE epoch date.

The gateway pack endpoint includes shared Pipeworx tools in addition to the three tools listed above. Standalone mode avoids those extra schemas but also does not provide gateway routing through `ask_pipeworx`. The available scope of a remote connection can change, so clients should inspect initialization results when exact tool availability matters.

_Full upstream README: https://allmcps.com/mcp/tle/readme_