Log inSubmit server
TLE Satellite Tracker logo

TLE Satellite Tracker

Search daily TLE data by satellite name or retrieve a record by satellite number.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install TLE Satellite Tracker

Pick your client, then add it in one click or paste the config.

SSE (Remote)
Server URL
https://api.nasa.gov/

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

The TLE Satellite Tracker MCP server provides access to the TLE API’s satellite orbital data. It supports searching by satellite name and retrieving an individual two-line element record by satellite number, with responses served as JSON. Reach for it when an agent needs current TLE records for satellites such as the ISS, Starlink spacecraft, or Hubble.

Use cases

  • Search for a satellite’s current TLE by name
  • Retrieve an orbital record using a satellite number
  • Supply TLE data to an astronomy or satellite-tracking workflow
  • Look up records for the ISS, Starlink, or Hubble

Key features

  • Search TLE records by satellite name
  • Retrieve a record by satellite number
  • Return orbital data as JSON
  • Use daily CelesTrak updates
  • Access records for thousands of satellites

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

4/4 checks healthy over the last 34d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars8Stargazers on the source repository.
Last commit6mo agoMost recent push to the default branch.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How TLE Satellite Tracker works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about TLE Satellite Tracker

TLE Satellite Tracker is an MCP server that connects to the TLE API and exposes tools for searching satellite records by name and retrieving a single TLE by satellite number. The API serves JSON data updated daily from CelesTrak, including records for objects such as the ISS, Starlink satellites, and Hubble.

Search by satellite name using the API’s `/api/tle?search={query}` operation. The service returns matching TLE data in JSON, and the README identifies name search as one of the two available endpoint operations.

Retrieve a record by passing the satellite number to `/api/tle/{id}`. Use the numeric identifier in place of `{id}` to request one TLE record from the API.

The data is updated daily from CelesTrak.

Related MCP servers

All in Aerospace & Astrodynamics All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTLE Satellite Tracker AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/tle-satellite-tracker?style=directory)](https://allmcps.com/mcp/tle-satellite-tracker)
HTML Embed
<a href="https://allmcps.com/mcp/tle-satellite-tracker"><img src="https://allmcps.com/api/badge/tle-satellite-tracker?style=directory" alt="TLE Satellite Tracker on AllMCPs" /></a>