# How to connect Nasa to OpenClaw (paste one key, 136 tools) > Connect Nasa to OpenClaw with ClawLink: paste your Nasa key once and 136 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/nasa The usual route to Nasa access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Nasa setup: install one ClawHub skill, connect Nasa in the browser, and OpenClaw can call real Nasa actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/nasa ## Setup It takes three steps to connect OpenClaw to Nasa. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Nasa** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect nasa # connect Nasa (browser OAuth) npx -y @useclawlink/cli actions nasa # list available actions npx -y @useclawlink/cli run nasa --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Nasa in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Nasa API key once. Verify the connection by asking OpenClaw: > Use Nasa to browse neo and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Nasa is connected in the dashboard, that agent calls the same 136 Nasa tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Nasa MCP for OpenClaw Looking for a Nasa MCP server for OpenClaw? ClawLink connects Nasa to OpenClaw and exposes 136 Nasa tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Nasa integration](https://claw-link.dev/hermes/nasa) works the same way. ## What the OpenClaw Nasa integration can do 136 Nasa tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 136. ### 30 of 136 Nasa tools for OpenClaw | Tool | What it does | |---|---| | **Browse neo** `nasa_browse_neo` | Browse the complete NASA near-Earth object (asteroid) dataset with pagination support | | **Create graph request** `nasa_create_graph_request` | Create orbital and position graphs for NASA satellites using the Satellite Situation Center (SSC) web service | | **Download citation document** `nasa_download_citation_document` | Downloads a document file from a NASA NTRS (NASA Technical Reports Server) citation | | **Get agage data** `nasa_get_agage_data` | Retrieve information about AGAGE (Advanced Global Atmospheric Gases Experiment) data files | | **Get agage data by file name** `nasa_get_agage_data_by_file_name` | Search for AGAGE (Advanced Global Atmospheric Gases Experiment) data files by file name | | **Get agage data json for graph** `nasa_get_agage_data_json_for_graph` | Retrieve AGAGE atmospheric composition data in JSON format optimized for graphing | | **Get agage data versions** `nasa_get_agage_data_versions` | Retrieve information on all AGAGE (Advanced Global Atmospheric Gases Experiment) data versions | | **Get apod** `nasa_get_apod` | Retrieves NASA's Astronomy Picture of the Day (APOD) for a specified date or today | | **Get citation** `nasa_get_citation` | Retrieve detailed citation information from NASA Technical Reports Server (NTRS) by citation ID | | **Restore citation revision** `nasa_restore_citation_revision` | Restore a previous version of a citation record within NASA's Common Metadata Repository | | **Get citation downloads** `nasa_get_citation_downloads` | Retrieve all available download links for a NASA technical report or publication by citation ID | | **Get citation revision ID** `nasa_get_citation_revision_id` | Retrieve citation revision IDs from NASA Common Metadata Repository (CMR) GraphQL API | | **Get citations autocomplete** `nasa_get_citations_autocomplete` | Get autocomplete suggestions from NASA NTRS (Technical Reports Server) citations | | **Get citations redistributions** `nasa_get_citations_redistributions` | Retrieve redistributed citations from NASA's Technical Reports Server (NTRS) | | **Get cmr collections** `nasa_get_cmr_collections` | Retrieve collections from the Common Metadata Repository (CMR) | | **Get cmr granules** `nasa_get_cmr_granules` | Search for data granules in NASA's Common Metadata Repository (CMR) | | **Get compounds** `nasa_get_compounds` | Retrieve information on all data compounds available in NASA's AGAGE (Advanced Global | | **Get data by file name** `nasa_get_data_by_file_name` | Get information about specific TOLNet (Tropospheric Ozone Lidar Network) data files by file name | | **Get data download** `nasa_get_data_download` | Download AGAGE (Advanced Global Atmospheric Gases Experiment) data files by ID | | **Get data frequencies** `nasa_get_data_frequencies` | Retrieves all available data frequency options from NASA's AGAGE (Advanced Global Atmospheric | | **Get data json** `nasa_get_data_json` | Retrieve JSON versions of TOLNet (Tropospheric Ozone Lidar Network) data by ID | | **Get data json for graph** `nasa_get_data_json_for_graph` | Retrieve JSON versions of TOLNet data including O3_Number_Density (ozone mixing ratio) and | | **Get document** `nasa_get_document` | Retrieve metadata for a single TOLNet (Tropospheric Ozone Lidar Network) document by ID | | **Get document download** `nasa_get_document_download` | Download a single TOLNet (Tropospheric Ozone Lidar Network) document by ID | | **Get documents** `nasa_get_documents` | Retrieve document information from NASA's TOLNet (Tropospheric Ozone Lidar Network) archive | | **Get donki cme** `nasa_get_donki_cme` | Retrieve Coronal Mass Ejection (CME) data from NASA's DONKI database | | **Get donki cme analysis** `nasa_get_donki_cme_analysis` | Retrieve Coronal Mass Ejection (CME) analysis data from NASA's DONKI (Database Of | | **Get donki gst** `nasa_get_donki_gst` | Retrieve Geomagnetic Storm (GST) data from NASA's Space Weather Database Of Notifications | | **Get donki hss** `nasa_get_donki_hss` | Retrieve High Speed Stream (HSS) data from NASA's DONKI space weather database | | **Get donki ips** `nasa_get_donki_ips` | Retrieve Interplanetary Shock (IPS) data from NASA's DONKI space weather database | ## Example prompts **Browse Neo** > Use Nasa to browse neo and walk me through the result in plain English. **Create Graph Request** > Create it in Nasa for me, then confirm the important fields before you finish. **Download Citation Document** > Use Nasa to download citation document and walk me through the result in plain English. **Get Agage Data** > Pull the relevant data from Nasa, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Nasa working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Nasa API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Nasa account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Nasa. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Nasa actions to the runtime in a format your agent can reliably use. | 136 tools for Nasa are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Nasa to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Nasa in the browser, and the 136 tools above work from chat. There is no SDK and no config file, and the Nasa key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Nasa skill but can't call the tools The ClawHub skill teaches OpenClaw about Nasa, but the calls run through the ClawLink plugin and your connected account. Make sure Nasa is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Nasa from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Nasa tools Nasa tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Nasa call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Nasa returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Nasa has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Nasa integration? Yes. ClawLink is the fastest way to connect OpenClaw to Nasa: link your Nasa account once in the browser and OpenClaw can call the Nasa API through 136 ready-made tools — no custom code or token handling. ### How do I add Nasa to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Nasa skill from ClawHub, then you click Connect in the dashboard to authorize Nasa. OpenClaw calls the tools from the next message — no config files, and the Nasa key you paste is stored server-side instead of in your environment. ### How long does it take to connect Nasa to OpenClaw? About two minutes. Sign in, click Connect next to Nasa in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Nasa up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Nasa working from chat. ### OpenClaw installed the Nasa skill but can't call the tools The ClawHub skill teaches OpenClaw about Nasa, but the calls run through the ClawLink plugin and your connected account. Make sure Nasa is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.