Skip to main content
Glama

NPM Version

NASA MCP Server

A Model Context Protocol (MCP) server for NASA APIs, providing a standardized interface for AI models to interact with NASA's vast array of data sources. This server implements the official Model Context Protocol specification.

Big thanks to the MCP community for their support and guidance!

Features

  • Access to 20+ NASA data sources through a single, consistent interface

  • Standardized data formats optimized for AI consumption

  • Automatic parameter validation and error handling

  • Rate limit management for NASA API keys

  • Comprehensive documentation and examples

  • Support for various NASA imagery formats

  • Data conversion and formatting for LLM compatibility

  • Cross-platform support (Windows, macOS, Linux)

Related MCP server: NASA APOD MCP Server

Example prompts

Ask your MCP client things like:

  • "Show me today's Astronomy Picture of the Day and explain what it shows."

  • "Were there any solar storms in September 2026: strong flares, Earth-directed CMEs or geomagnetic storms?"

  • "Which asteroids fly past Earth today, and which one comes closest?"

  • "Will any asteroid pass closer to Earth than the Moon in the next 90 days?"

  • "What are the odds that Bennu hits Earth, according to JPL Sentry?"

  • "Find NASA photos of the Apollo 11 lunar module taken in 1969."

  • "Which tropical storms and hurricanes are active right now?"

  • "Show me a detailed satellite view of the Nile Delta and the Sinai on 2025-07-15."

  • "Find cloud-hosted sea ice concentration datasets in NASA Earthdata."

  • "What were the daily highs, lows and solar energy in Denver during the first week of July 2025?"

  • "List the nearest roughly Earth-sized, temperate exoplanets discovered since 2020."

  • "Where was the ISS over the Earth between 00:00 and 00:10 UTC on 2026-09-29?"

  • "Get the latest two-line orbital elements for the ISS."

  • "Show me a Mars Trek map tile of Olympus Mons."

  • "What was the weather like at NASA's InSight lander during its last reported week on Mars?"

  • "Which near-Earth asteroids need the least delta-v for a mission launched in 2030?"

  • "Which NASA technology projects have worked on solar sails?"

  • "Find NASA patents about solar panels that companies can license."

  • "Which TESS sectors observed Pi Mensae, and where can I download its 2-minute light curves?"

  • "Has JWST observed TRAPPIST-1, and with which instruments?"

Disclaimer

This project is not affiliated with, endorsed by, or related to NASA (National Aeronautics and Space Administration) or any of its subsidiaries or its affiliates. It is an independent implementation that accesses NASA's publicly available APIs. All NASA data used is publicly available and subject to NASA's data usage policies.

Installation

You don't start an MCP server yourself. Your AI app (Claude, Cursor, VS Code, Codex and others) launches it in the background, so installing it means adding an entry to that app's MCP configuration. The only prerequisite is Node.js 22 or newer; npx downloads the server the first time the app starts it.

Most tools need no API key. NASA_API_KEY (free at https://api.nasa.gov/; DEMO_KEY works for light use) is only used by nasa_neo, nasa_insight_weather and nasa_mars_rover, and FIRMS_MAP_KEY only by nasa_firms. Leave out the env block if you don't need them.

Using an AI coding agent (Claude Code, Codex, Cursor, VS Code agent mode)? Paste this into it:

Install the NASA MCP server from https://github.com/ProgramComputer/NASA-MCP-server
for the app you're running in. Follow that app's section under Installation in the
README, add it for all projects, and don't add an API key. Tell me exactly what you
changed and whether I need to restart.

Standard config

Most clients use this JSON shape:

{
  "mcpServers": {
    "nasa": {
      "command": "npx",
      "args": ["-y", "@programcomputer/nasa-mcp-server@latest"],
      "env": {
        "NASA_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

If the file already has an mcpServers object, add the "nasa" entry inside it instead of pasting a second mcpServers.

Open Settings → Developer → Edit Config. This opens claude_desktop_config.json:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Paste the standard config, save, then fully quit and reopen Claude Desktop.

claude mcp add --env NASA_API_KEY=YOUR_API_KEY --scope user nasa -- npx -y @programcomputer/nasa-mcp-server@latest

--scope user makes the server available in every project; leave it out to add it to the current project only. On native Windows, replace npx with cmd /c npx.

The button installs the server without an API key. To install by hand, or to add a key, paste the standard config into ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).

The buttons install the server without an API key. VS Code uses a top-level servers key instead of mcpServers. To install by hand, add this to .vscode/mcp.json in your workspace, or run MCP: Open User Configuration from the Command Palette for all workspaces. VS Code asks for the key the first time the server starts and stores it securely; leave it blank to skip it.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "nasa-api-key",
      "description": "NASA API key (optional)",
      "password": true
    }
  ],
  "servers": {
    "nasa": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@programcomputer/nasa-mcp-server@latest"],
      "env": {
        "NASA_API_KEY": "${input:nasa-api-key}"
      }
    }
  }
}
codex mcp add nasa --env NASA_API_KEY=YOUR_API_KEY -- npx -y @programcomputer/nasa-mcp-server@latest

This writes the following to ~/.codex/config.toml, which the Codex CLI, IDE extension and desktop app share. You can also add it by hand:

[mcp_servers.nasa]
command = "npx"
args = ["-y", "@programcomputer/nasa-mcp-server@latest"]

[mcp_servers.nasa.env]
NASA_API_KEY = "YOUR_API_KEY"

Paste the standard config into ~/.gemini/settings.json (all projects) or .gemini/settings.json (one project).

Most other MCP clients accept the standard config. If a client asks for the command and arguments separately, the command is npx and the arguments are -y @programcomputer/nasa-mcp-server@latest.

To run a local clone instead of the npm package (see Manual Installation), use "command": "node" with "args": ["/absolute/path/to/NASA-MCP-server/dist/index.js"].

Checking that it works

Restart or reload your client and check that a server named nasa appears in its MCP or tools list. Then ask something like "What's today's Astronomy Picture of the Day?"

If the server doesn't appear:

  • Run node --version and make sure it prints v22 or newer.

  • Check the config file for JSON mistakes such as a trailing comma or a second mcpServers object.

  • Run the server from a terminal (below) to see any errors. If it prints nothing and waits, it is working; press Ctrl+C to stop it.

  • On Windows, if the client reports that npx can't be found, use "command": "cmd" with "args": ["/c", "npx", "-y", "@programcomputer/nasa-mcp-server@latest"].

Running from a terminal

You only need this for testing; your MCP client starts the server for you.

env NASA_API_KEY=YOUR_API_KEY npx -y @programcomputer/nasa-mcp-server@latest

You can also pass the API key as a command line argument:

npx -y @programcomputer/nasa-mcp-server@latest --nasa-api-key=YOUR_API_KEY

Manual Installation

# Clone the repository
git clone https://github.com/ProgramComputer/NASA-MCP-server.git

# Install dependencies
cd NASA-MCP-server
npm install

# Build
npm run build

# Run with your API key
NASA_API_KEY=YOUR_API_KEY npm start

Replace YOUR_API_KEY with your NASA API key from https://api.nasa.gov/. Requires Node.js 22 or newer.

Environment Variables

The server can be configured with the following environment variables:

Variable

Description

NASA_API_KEY

Your NASA API key (get at api.nasa.gov); used by NEO and InSight weather

FIRMS_MAP_KEY

Your FIRMS MAP_KEY for fire data (get at firms.modaps.eosdis.nasa.gov/api/map_key); separate from NASA_API_KEY

NASA_MCP_CMR_URL

Optional CMR search URL (default: https://cmr.earthdata.nasa.gov/search)

MCP_TRANSPORT

Transport mode: stdio (default) or http for Streamable HTTP

MCP_HTTP_HOST

Host for Streamable HTTP mode (default: 127.0.0.1)

MCP_HTTP_PORT

Port for Streamable HTTP mode (default: 3000)

MCP_HTTP_PATH

MCP endpoint path for Streamable HTTP mode (default: /mcp)

Transport Modes

By default, the server runs over stdio for local MCP clients such as Cursor.

To run the optional Streamable HTTP transport:

MCP_TRANSPORT=http MCP_HTTP_PORT=3000 NASA_API_KEY=YOUR_API_KEY npm start

The Streamable HTTP endpoint will be available at:

http://127.0.0.1:3000/mcp

Included NASA APIs

This MCP server integrates the following NASA APIs:

  1. NASA Open API (api.nasa.gov, needs NASA_API_KEY):

    • NEO (Near Earth Object Web Service)

    • InSight Mars Weather Service (historical: the feed stopped updating in October 2020)

  2. Other NASA APIs (no key needed):

    • APOD (Astronomy Picture of the Day), from the NASA Science APOD API (science.nasa.gov)

    • DONKI (Space Weather Database Of Notifications, Knowledge, Information), from NASA CCMC (ccmc.gsfc.nasa.gov)

    • EONET (Earth Observatory Natural Event Tracker)

    • TLE (Two-Line Element sets from CelesTrak, via tle.ivanstanojevic.me)

    • Satellite Situation Center (spacecraft locations)

    • TechPort (NASA technology projects)

    • Technology Transfer (patents, software and spinoffs)

    • Mars, Moon and Vesta Trek (WMTS map layers and tiles)

    • NASA Image and Video Library

    • Exoplanet Archive

    • MAST (Mikulski Archive for Space Telescopes): TESS, Hubble, JWST, Kepler/K2 and other observations, their data products, and TESS full-frame image cutouts (TESSCut). The tools return download links to the FITS files rather than the files themselves, so your client can find data but not analyze it.

    • Open Science Data Repository (OSDR) files

    • POWER (Prediction Of Worldwide Energy Resources)

  3. JPL Solar System Dynamics API (ssd-api.jpl.nasa.gov):

    • SBDB (Small-Body DataBase)

    • SBDB Close-Approach Data

    • Fireball Data

    • Sentry (impact risk)

    • Scout (NEO Confirmation Page orbits)

    • NHATS (human-accessible NEOs)

    • Small-Body Mission Design

    • Horizons ephemerides

    • Periodic Orbits

    • Julian date converter

  4. Earth Data APIs:

    • GIBS (Global Imagery Browse Services)

    • CMR (Common Metadata Repository) - Enhanced with advanced search capabilities

    • EPIC (Earth Polychromatic Imaging Camera)

    • FIRMS (Fire Information for Resource Management System)

API Methods

Each NASA API is exposed through standardized MCP methods:

APOD (Astronomy Picture of the Day)

{
  "method": "nasa/apod",
  "params": {
    "date": "2023-01-01", // Optional: YYYY-MM-DD (1995-06-16 or later); defaults to the latest picture
    "max_images": 1 // Optional: how many pictures to embed (0-5)
  }
}

For a range, send start_date and end_date (up to 100 days) instead of date. APOD now comes from the NASA Science APOD API, which needs no key and has no random count or thumbs option.

Near Earth Objects

{
  "method": "nasa/neo",
  "params": {
    "start_date": "2023-01-01", // Required: YYYY-MM-DD format
    "end_date": "2023-01-07" // Required: YYYY-MM-DD format (max 7 days from start)
  }
}

GIBS (Global Imagery Browse Services)

{
  "method": "nasa/gibs",
  "params": {
    "layer": "MODIS_Terra_CorrectedReflectance_TrueColor", // Required: Layer ID
    "date": "2023-01-01", // Required: YYYY-MM-DD format
    "format": "png" // Optional: "png" or "jpg"
  }
}

POWER (Prediction Of Worldwide Energy Resources)

{
  "method": "nasa/power",
  "params": {
    "parameters": "T2M,PRECTOTCORR,WS10M", // Required: Comma-separated list
    "community": "re", // Required: Community identifier
    "latitude": 40.7128, // Required: Latitude
    "longitude": -74.0060, // Required: Longitude
    "start": "20220101", // Required: Start date (YYYYMMDD)
    "end": "20220107" // Required: End date (YYYYMMDD)
  }
}

CMR (Common Metadata Repository)

{
  "method": "nasa/cmr",
  "params": {
    "keyword": "sea surface temperature", // Optional: Collections only
    "search_type": "collections", // Optional: "collections" (default) or "granules"
    "bounding_box": "-100,10,-60,40", // Optional: west,south,east,north ("bbox" also works)
    "temporal": "2024-06-01T00:00:00Z,2024-09-30T23:59:59Z", // Optional: start,end
    "limit": 5 // Optional: 1-100, default 10
  }
}

Results come back in a compact format by default ("response_mode": "raw" returns CMR's own metadata, and fields picks which fields to return). To get the next page, send back only the next_cursor from the response:

{
  "method": "nasa/cmr",
  "params": {
    "cursor": "cmr1..." // Required: next_cursor from the previous response
  }
}

FIRMS (Fire Information for Resource Management System)

{
  "method": "nasa/firms",
  "params": {
    "bbox": "-125,32,-114,42", // Required: west,south,east,north (or latitude, longitude and radius_km)
    "days": 1, // Optional: 1-5
    "source": "VIIRS_SNPP_NRT" // Optional: FIRMS data source
  }
}

For complete documentation of all available methods and parameters, see the API reference in the /docs directory.

Logging System

The server includes comprehensive logging:

  • Operation status and progress

  • Performance metrics

  • Rate limit tracking

  • Error conditions

  • Request validation

Example log messages:

[INFO] NASA MCP Server initialized successfully
[INFO] Processing APOD request for date: 2023-01-01
[WARNING] Rate limit threshold reached (80%)
[ERROR] Invalid parameter: 'date' must be in YYYY-MM-DD format

Security Considerations

This MCP server implements security best practices following the Model Context Protocol specifications:

  • Input validation and sanitization using Zod schemas

  • No execution of arbitrary code

  • Protection against command injection

  • Proper error handling to prevent information leakage

  • Rate limiting and timeout controls for API requests

  • No persistent state that could be exploited across sessions

Development

# Clone the repository
git clone https://github.com/ProgramComputer/NASA-MCP-server.git

# Install dependencies
npm install

# Copy the example environment file and update with your API keys
cp .env.example .env

# Build the TypeScript code
npm run build

# Start the server
npm start

# Run tests
npm test

Testing with MCP Inspector

To test the tools interactively, build the project and start the official MCP Inspector with the server:

npm run build
npx @modelcontextprotocol/inspector node dist/index.js

The server reads NASA_API_KEY and FIRMS_MAP_KEY from a .env file in the working directory (see Development above). The Inspector prints a local URL; open it to list and call the tools.

Example Test Requests

The repository includes example test requests for each API that you can copy and paste into the MCP Inspector:

# View the example test requests
cat docs/inspector-test-examples.md

For detailed examples, see the Inspector Test Examples document.

MCP Client Usage

This server follows the official Model Context Protocol. For local clients, use the stdio configuration in Installation. For Streamable HTTP mode, start the server with MCP_TRANSPORT=http, then connect with the MCP SDK:

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";
import { CallToolResultSchema } from "@modelcontextprotocol/sdk/types.js";

const transport = new StreamableHTTPClientTransport(
  new URL("http://127.0.0.1:3000/mcp")
);

const client = new Client({
  name: "mcp-client",
  version: "1.0.0",
});

await client.connect(transport);

// Example: Get today's Astronomy Picture of the Day
const apodResult = await client.request({
  method: "tools/call",
  params: {
    name: "nasa/apod",
    arguments: {}
  }
}, CallToolResultSchema);

// Example: Search for Near Earth Objects
const neoResults = await client.request({
  method: "tools/call",
  params: {
    name: "nasa/neo",
    arguments: {
      start_date: "2023-01-01",
      end_date: "2023-01-07"
    }
  }
}, CallToolResultSchema);

// Example: Get satellite imagery from GIBS
const satelliteImage = await client.request({
  method: "tools/call",
  params: {
    name: "nasa/gibs",
    arguments: {
      layer: "MODIS_Terra_CorrectedReflectance_TrueColor",
      date: "2023-01-01"
    }
  }
}, CallToolResultSchema);

// Example: Use the new POWER API
const powerData = await client.request({
  method: "tools/call",
  params: {
    name: "nasa/power",
    arguments: {
      parameters: "T2M,PRECTOTCORR,WS10M",
      community: "re",
      latitude: 40.7128,
      longitude: -74.0060,
      start: "20220101",
      end: "20220107"
    }
  }
}, CallToolResultSchema);

Contributing

  1. Fork the repository

  2. Create your feature branch

  3. Run tests: npm test

  4. Submit a pull request

License

ISC License - see LICENSE file for details

Available Tools

32 tools
jpl_cadJPL close approachesC
Read-onlyIdempotent

Asteroid and comet close approaches to the planets, past and future, from the JPL SBDB Close-Approach Data API.

Inputs: des, neo, spk, body, +9 more.

jpl_fireballJPL fireball eventsB
Read-onlyIdempotent

Fireball (bolide) events reported by US Government sensors, from the JPL Fireball API.

Inputs: limit, req_alt, req_loc, req_vel, +9 more.

jpl_horizonsJPL Horizons ephemeridesC
Read-onlyIdempotent

Ephemerides and object data for solar-system bodies from the JPL Horizons API (GET).

Inputs: COMMAND (required), CENTER, format, OBJ_DATA, +7 more.

jpl_horizons_fileJPL Horizons ephemerides (file input)B
Read-onlyIdempotent

Same as jpl_horizons, but submits the parameters as a Horizons input file (POST to horizons_file.api).

Inputs: COMMAND (required), CENTER, format, OBJ_DATA, +7 more.

jpl_jd_calJPL Julian date converterB
Read-onlyIdempotent

Convert between Julian dates and calendar dates (UTC) with the JPL JD-Calendar API.

Inputs: cd, jd.

jpl_mission_designJPL small-body mission designA
Read-onlyIdempotent

Ballistic mission options to asteroids and comets from the JPL Small-Body Mission Design API. Object mode (des, spk or sstr) returns the pre-computed mission options stored for one object (launch and arrival dates, V-infinity, time of flight). List mode returns the most accessible small bodies for the given launch years, ranked by crit, with optional SBDB filters. Porkchop-plot maps (mode M) and mission-extension searches (mode T) are not exposed.

Inputs: des, lim, spk, crit, +9 more.

jpl_nhatsJPL NHATS human-accessible NEOsB
Read-onlyIdempotent

Near-Earth objects accessible to human missions (NHATS): a constrained summary list, or one object by des/spk.

Inputs: h, dv, des, dur, +5 more.

jpl_periodic_orbitsJPL three-body periodic orbitsC
Read-onlyIdempotent

Periodic orbits (halo, DRO, Lyapunov, ...) in three-body systems from the JPL Three-Body Periodic Orbits database.

Inputs: sys (required), family (required), libr, branch, +7 more.

jpl_sbdbJPL Small-Body Database lookupB
Read-onlyIdempotent

Orbital and physical data for one asteroid or comet from the JPL Small-Body Database (SBDB).

Inputs: cad, des, sat, spk, +8 more.

jpl_scoutJPL Scout NEOCP hazard assessmentB
Read-onlyIdempotent

JPL Scout trajectory analysis and hazard assessment for unconfirmed objects on the Minor Planet Center NEO Confirmation Page.

Inputs: file, plot, tdes, limit, +2 more.

jpl_sentryJPL Sentry impact riskB
Read-onlyIdempotent

Earth impact risk assessments from JPL Sentry: summary table, one object, virtual impactors, or removed objects.

Inputs: all, des, spk, h_max, +4 more.

nasa_apodNASA Astronomy Picture of the DayA
Read-onlyIdempotent

NASA's Astronomy Picture of the Day (APOD) from the NASA Science APOD API (science.nasa.gov): the latest picture, one date (1995-06-16 onward), or a date range of up to 100 days. Returns the title, credit, explanation as plain text, image or video URL and page link, and embeds up to max_images pictures. No API key needed.

Inputs: date, end_date, max_images, start_date.

nasa_cmrNASA Earthdata CMR searchA
Read-onlyIdempotent

Search NASA's Common Metadata Repository (CMR) for Earth science collections (datasets) or granules (files). Supports identifiers, temporal and spatial filters (bounding_box, point, polygon, line, circle), platform/instrument/project, facets and sorting. Returns a compact normalized envelope by default (response_mode raw for upstream metadata) and a next_cursor for Search After pagination: continue by passing only {"cursor": next_cursor}. Collection matches describe datasets; they do not prove granules exist for a given time or place. No API key needed.

Inputs: doi, bbox, line, page, +35 more. Returns: raw, error, facets, format, +10 more

nasa_donkiNASA DONKI space weatherA
Read-onlyIdempotent

Space Weather Database Of Notifications, Knowledge, Information (DONKI) events by type for up to 30 days at a time, from the NASA CCMC DONKI API (ccmc.gsfc.nasa.gov): solar flares, CMEs and their analyses, geomagnetic storms, interplanetary shocks, SEP, MPC, RBE and HSS events, WSA-ENLIL simulations and notifications. Compact one-line summaries by default; response_mode raw returns the full records. No API key needed.

Inputs: type (required), limit, endDate, startDate, +1 more.

nasa_eonetNASA EONET natural eventsB
Read-onlyIdempotent

Natural events (wildfires, storms, volcanoes, ice, ...) from the Earth Observatory Natural Event Tracker. Filters are sent exactly as given; no automatic broadening.

Inputs: days, limit, source, status, +1 more.

nasa_epicNASA EPIC Earth imageryB
Read-onlyIdempotent

Earth Polychromatic Imaging Camera (DSCOVR) full-disc Earth images for a day: metadata for every image plus a bounded number embedded.

Inputs: date, collection, max_images.

nasa_exoplanetNASA Exoplanet Archive queryB
Read-onlyIdempotent

Query the NASA Exoplanet Archive through its TAP service (ADQL). Tables use current TAP names such as ps, pscomppars, cumulative and toi.

Inputs: table (required), limit, order, where, +2 more.

nasa_firmsNASA FIRMS active fire detectionsA
Read-onlyIdempotent

Active fire/thermal anomaly detections from NASA FIRMS for a bounding box and 1-5 day window. Requires FIRMS_MAP_KEY (not NASA_API_KEY). The legacy latitude/longitude interface now needs radius_km and is converted to a bbox.

Inputs: bbox, date, days, limit, +4 more. Returns: error, query, source, status, +6 more

nasa_gibsNASA GIBS satellite imageryB
Read-onlyIdempotent

Render a Global Imagery Browse Services (GIBS) layer for a date and bounding box as an image (WMS GetMap, EPSG:4326).

Inputs: date (required), layer (required), bbox, format, +1 more.

nasa_imagesNASA Image and Video Library searchB
Read-onlyIdempotent

Search NASA's Image and Video Library. Returns item metadata and URLs, with a bounded number of preview thumbnails embedded.

Inputs: q (required), page, year_end, page_size, +3 more.

nasa_insight_weatherNASA InSight Mars weather (historical)A
Read-onlyIdempotent

HISTORICAL DATA ONLY: per-sol Mars surface weather (air temperature, pressure, wind) from NASA's InSight lander at Elysium Planitia. The feed is frozen at the last seven sols it reported (sols 675-681, October 2020) and is no longer updated. Requires NASA_API_KEY.

Inputs: no named parameters.

nasa_mars_roverNASA Mars Rover Photos (retired upstream)A
Read-onlyIdempotent

DEPRECATED: the upstream Mars Rover Photos API (api.nasa.gov/mars-photos) has been returning HTTP 404 "No such app" since at least 2026-09-29. Calls still query it and report the upstream status accurately; no photos are fabricated. Requires NASA_API_KEY.

Inputs: rover (required), sol, page, camera, +2 more.

nasa_neoNASA Near Earth Object Web ServiceA
Read-onlyIdempotent

Near-Earth asteroid close approaches from NASA NeoWs: a feed for up to 7 days (defaults to today, UTC) or a single asteroid by ID. Requires NASA_API_KEY.

Inputs: end_date, start_date, asteroid_id.

nasa_osdr_filesNASA OSDR study filesA
Read-onlyIdempotent

List the data files (with download links) for a NASA Open Science Data Repository (OSDR) study.

Inputs: accession_number (required).

nasa_powerNASA POWER daily point dataB
Read-onlyIdempotent

Daily solar and meteorological data for a point from NASA POWER (Prediction Of Worldwide Energy Resources).

Inputs: end (required), start (required), latitude (required), community (required), +4 more.

nasa_ssc_locationsSatellite Situation Center spacecraft locationsA
Read-onlyIdempotent

Positions of spacecraft (and the Moon and Sun) over a time range from the NASA Satellite Situation Center (SSCWeb), in geophysical coordinate systems (GEO, GM, GSE, GSM, SM, GEI). Returns a CSV table per observatory: X/Y/Z in km, latitude/longitude in degrees, local time in hours and radial distance in km. The resolution factor is raised automatically to keep the output bounded. No API key needed.

Inputs: end_time (required), start_time (required), observatories (required), resolution_factor, +1 more.

nasa_ssc_observatoriesSatellite Situation Center spacecraft listA
Read-onlyIdempotent

Spacecraft and other observatories whose locations the NASA Satellite Situation Center (SSCWeb) can compute, with their data time ranges and resolution. Use the IDs with nasa_ssc_locations. No API key needed.

Inputs: search, active_on.

nasa_techportNASA TechPort technology projectsA
Read-onlyIdempotent

NASA's technology project inventory (TechPort): search projects by keyword, or fetch one project with its status, dates, program, technology readiness levels (TRL), lead organization, description and benefits. No API key needed.

Inputs: limit, query, project_id.

nasa_techtransferNASA Technology Transfer searchA
Read-onlyIdempotent

Search NASA's Technology Transfer portfolio (technology.nasa.gov): patents available for licensing, issued patents, the NASA Software Catalog, or Spinoff stories about commercial products that use NASA technology. No API key needed.

Inputs: query (required), limit, collection.

nasa_tleSatellite two-line element setsA
Read-onlyIdempotent

Two-line element sets (TLE) for Earth-orbiting satellites from the TLE API in the api.nasa.gov catalog (tle.ivanstanojevic.me; CelesTrak data refreshed daily): one satellite by NORAD catalog number, or a paged name search. No API key needed.

Inputs: page, sort, search, sort_dir, +2 more.

nasa_trek_layersNASA Trek map layers (Mars, Moon, Vesta)A
Read-onlyIdempotent

Search the map layer catalogs of NASA Mars Trek, Moon Trek and Vesta Trek (trek.nasa.gov): mosaics, colour hillshades and other imagery served as OGC WMTS tiles. Returns layer IDs for nasa_trek_tile, with mission, instrument and WMTS endpoint. No API key needed.

Inputs: body (required), limit, search, projection.

nasa_trek_tileNASA Trek map tile (Mars, Moon, Vesta)A
Read-onlyIdempotent

One WMTS map tile image from NASA Mars Trek, Moon Trek or Vesta Trek for a layer from nasa_trek_layers, addressed by zoom/row/col or (equirectangular layers) by latitude/longitude. Reads the layer's WMTS capabilities to validate the tile and pick the format. No API key needed.

Inputs: body (required), layer (required), col, row, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 32 tools

    Disambiguation3/5

    Most tools target distinct NASA data sources, but several pairs overlap: nasa_neo and jpl_cad both handle close approaches, jpl_sentry and jpl_scout both assess impact risk, and jpl_horizons and jpl_horizons_file offer the same data via different HTTP methods. Descriptions help distinguish these, but an agent could still misselect.

    Naming Consistency5/5

    All tool names use consistent snake_case with a clear provider prefix (nasa_ or jpl_) and service-oriented nouns. The pattern is predictable throughout, with only minor abbreviations like jpl_jd_cal that still fit the convention.

    Tool Count2/5

    32 tools is well above the recommended 3–15 range and feels heavy even for a broad NASA data server. While each tool maps to a distinct API, the set would be more manageable if split into focused sub-servers.

    Completeness3/5

    The surface covers many NASA APIs but misses major ones like NTRS, ADS, PDS, and HEASARC. Additionally, some included tools are deprecated or frozen (nasa_mars_rover, nasa_insight_weather), creating dead ends that limit reliable coverage.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables LLMs to query data from various NASA APIs, allowing access to astronomical data, space weather information, Earth imagery, and exoplanet information directly from compatible AI clients.
      21
      6
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Multi-Agent Conversation Protocol server for accessing NASA's Astronomy Picture of the Day (APOD) API, allowing users to retrieve space imagery and related information through natural language interactions.
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server providing AI agents with access to NASA and space/astronomy data including APOD, Mars rover photos, near-Earth asteroids, exoplanets, Earth imagery, natural events, and space weather.
      11
      MIT