satellitetracking

The Satellite Tracking MCP Server exposes a set of tools to access satellite data via the N2YO API. You can retrieve real-time satellite positions, fetch TLE data, predict visual and radio passes, find satellites currently above a location, and search for satellites by name or category. Core tools include get_satellite_position, get_satellite_tle, predict_visual_passes, predict_radio_passes, get_satellites_above, and search_satellites. Resources available through the server include satellite://{norad_id}, satellites://category/{category_id}, and satellites://above/{lat}/{lon}/{radius}. To use the server, configure it in your MCP client (e.g., Claude) with the appropriate command and the required N2YO API key in the environment. Once running, you can call a tool by specifying its name and providing the required arguments such as the NORAD ID, observer location, and time window for predictions. The API mirrors common satellite-tracking workflows, making it straightforward to integrate real-time positioning, TLE access, and prediction data into your applications or workflows.

Prerequisites:

• Node.js 18 or higher
• npm (comes with Node.js)
• A N2YO API key

Setup steps:

1. Clone the repository or download the source code for the Satellite Tracking MCP Server.
2. Install dependencies:

cd satellite-tracking-server
npm install

3. Build the server:

npm run build

4. Run or integrate with your MCP client using the provided mcp_config example, ensuring you supply your N2YO API key in the environment variable N2YO_API_KEY.
5. Verify the server is reachable from your MCP client and begin issuing tool requests such as get_satellite_position, get_satellite_tle, and others.

Notes and tips:

• Ensure your N2YO API key is valid and has the required permissions for the endpoints you use.
• The N2YO API has rate limits; plan routing and caching accordingly.
• When configuring in Claude or other MCP clients, set the env var N2YO_API_KEY to your actual key or manage it securely through your client’s secret storage.
• If a satellite has no real-time data, get_satellite_position or other live endpoints may return incomplete data; rely on TLE data with get_satellite_tle for historical or predictive uses.
• You can access satellite resources using the provided satellites:// URIs to navigate categories or specific satellites.
• The server supports a broad range of categories; refer to the in-app or README category table to filter satellites by category_id.