← All integrations

NASA MCP server

24 operations0 webhooks

Astronomy Picture of the Day, near-Earth asteroid data from NeoWs, space weather from DONKI, DSCOVR EPIC imagery, EONET natural events and the NASA Image and Video Library.

Try NASA with your agent

Connect NASA, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in NASA on my account, then run one read-only example and show me the result.

Runs once, when you ask

NASA tools and triggers

Tools are what your agent can do in NASA through Corsair's MCP server. Triggers are the NASA events a routine can start from.

Donki

  • CmeRead-only

    List coronal mass ejections in a date range, with the analyses and ENLIL model runs attached to each

    donki.cme

  • Cme AnalysisRead-only

    List standalone CME analyses, filterable by speed, half angle, catalog and the provider's most-accurate flag

    donki.cmeAnalysis

  • Enlil SimulationRead-only

    List WSA-ENLIL model runs in a date range, with their CME inputs and the estimated arrival at each spacecraft

    donki.enlilSimulation

  • Geomagnetic StormRead-only

    List geomagnetic storms in a date range, with the Kp index readings behind each one

    donki.geomagneticStorm

  • High Speed StreamRead-only

    List high speed solar wind streams in a date range, with the events each one is linked to

    donki.highSpeedStream

  • Interplanetary ShockRead-only

    List interplanetary shocks in a date range, filterable by the observing spacecraft and the catalog

    donki.interplanetaryShock

  • Magnetopause CrossingRead-only

    List magnetopause crossings in a date range

    donki.magnetopauseCrossing

  • NotificationRead-only

    List space weather notifications in a date window of at most 30 days, readable as text or filtered to one event type

    donki.notification

  • Radiation BeltRead-only

    List radiation belt enhancements in a date range

    donki.radiationBelt

  • Solar Energetic ParticleRead-only

    List solar energetic particle events in a date range

    donki.solarEnergeticParticle

  • Solar FlareRead-only

    List solar flares in a date range, with begin, peak and end times, the class and the active region

    donki.solarFlare

Eonet

  • CategoriesRead-only

    List the EONET categories events can be filed under

    eonet.categories

Connect NASA to Claude, ChatGPT or Cursor

  1. 1

    Connect NASA in Corsair

    Add your NASA API key once in Corsair. Corsair stores the credential encrypted and makes the NASA API calls for your agent, so it never goes into a prompt or a config file. Connect NASA

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs NASA. On a ChatGPT personal plan, connect NASA here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. Every NASA operation only reads data, so it runs right away in every mode.

FAQ

Install corsair and @corsair-dev/nasa, add the NASA plugin, and connect with an API key. Then call methods like corsair.nasa.api.apod.get() from your app. Corsair keeps each tenant isolated.

Yes. NASA requires an API key from your NASA account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit NASA, GitHub, Notion, Stripe, and the rest. Trigger NASA from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for astronomy Picture of the Day, near-Earth asteroid data from NeoWs, space weather from DONKI, DSCOVR EPIC imagery, EONET natural events and the NASA Image and Video Library. Common builds include sync jobs, admin tooling, and agents that call NASA APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per NASA API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/nasa in the open repo. When NASA ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your NASA data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store NASA data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put NASA on a link in Strict mode and every write waits for your approval, while destructive actions are refused. Every NASA operation only reads data, so there are no changes to approve today. You can change a link's mode at hub.corsair.dev/me.