# TLE Satellite Tracker [Health: Active]

**Category:** 🚀 Aerospace & Astrodynamics  
**Repository:** https://github.com/ivanstan/tle-api  
**GitHub Stars:** 8  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/tle-satellite-tracker

## Description
Access TLE orbital data for thousands of satellites including ISS, Starlink, and Hubble.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "tle-satellite-tracker": {
    "url": "https://api.nasa.gov/"
  }
}
```

## Documentation

## What TLE Satellite Tracker MCP server does

The TLE Satellite Tracker MCP server gives an MCP client access to orbital records from the TLE API. The API provides two-line element sets, or TLEs, for Earth-orbiting objects. Each record encodes orbital elements for a particular point in time and is returned in JSON format.

The available data covers thousands of satellites. The source description specifically identifies the International Space Station, Starlink satellites, and Hubble as examples. Data is updated daily from CelesTrak, so the service is intended for retrieving current records rather than maintaining a static local catalog.

## How it works

The underlying service exposes two HTTP operations. A name search uses `GET /api/tle?search={query}` and looks for satellites by name. A direct lookup uses `GET /api/tle/{id}`, where `id` is the satellite number. The API’s base address is `http://tle.ivanstanojevic.me`, and the README links to that service for additional documentation and response examples.

The TLE Satellite Tracker MCP server makes these two retrieval patterns available to an agent through its listed satellite-data capability. A client can use a name query when the satellite number is unknown, then use the satellite number for a specific record lookup. Results are provided by the remote API in JSON rather than as a local database export.

## Tools and capabilities

Available operations are limited to reading TLE records:

- Search for a satellite by name.
- Retrieve one TLE record by satellite number.
- Return the API response as JSON.
- Access records refreshed daily from CelesTrak.

The repository is the codebase behind the TLE API backend and is listed in NASA’s API catalog. It also references JavaScript, PHP, and C# client libraries, but those libraries are separate projects and are not described as MCP tools.

## Limitations and notes

The documented interface does not describe orbital propagation, position calculation, pass prediction, telemetry, satellite tracking on a map, or write operations. It provides TLE records; another tool or application would be needed to interpret those elements for simulation or observation planning.

The service depends on the remote TLE API and its daily CelesTrak updates. It also does not specify search behavior beyond searching by satellite name, so callers should use the linked API documentation for response details and examples.

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