NASA-MCP. Integration via MCP with NASA APIs

Created By
AnCode666a year ago
MCP server for use NASA APIs
Overview

what is NASA-MCP?

NASA-MCP is a server that integrates with NASA APIs, allowing users to retrieve astronomical data, space weather information, Earth imagery, and more through the Model Context Protocol (MCP).

how to use NASA-MCP?

To use NASA-MCP, install it via the Smithery CLI or the uv package manager, configure it with your NASA API key, and integrate it with compatible clients like Claude for Desktop.

key features of NASA-MCP?

  • Access to Astronomy Picture of the Day (APOD) with explanations and imagery
  • Query Near Earth Objects data and asteroid information
  • Retrieve Space Weather data from DONKI
  • Get Earth imagery from Landsat 8 satellite
  • Access EPIC camera images showing the full Earth disk
  • Query the Exoplanet Archive database for information about exoplanets

use cases of NASA-MCP?

  1. Displaying today's astronomy picture
  2. Finding asteroids that will pass near Earth
  3. Retrieving information about solar flares
  4. Showing Earth imagery for specific coordinates
  5. Searching for exoplanets in the habitable zone

FAQ from NASA-MCP?

  • How do I get an API key?

You can get a free API key from NASA at https://api.nasa.gov/.

  • Can I use NASA-MCP with any client?

Yes, NASA-MCP can be integrated with any MCP-compatible client.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AnCode666
Star
1
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago