NASA MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NASA_API_KEY | Yes | Your NASA API key from api.nasa.gov |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {
"enabled": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nasaPicOfDayToolC | get the NASA picture of the day |
| getCurrentDateC | Get todays date |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one retrieves a NASA picture of the day, the other retrieves the current date. There is no overlap or ambiguity between them.
Both names are in camelCase, but their stylistic patterns differ: 'nasaPicOfDayTool' is a noun phrase with a 'Tool' suffix, while 'getCurrentDate' follows a verb_noun imperative. This inconsistency in naming convention across the small set makes it less coherent.
With only two tools, the server feels thin for a domain as broad as NASA data. The count is borderline, hinting at an incomplete or minimal implementation rather than a well-scoped set.
The tool surface is severely incomplete for a NASA MCP server. Many obvious capabilities such as Mars rover photos, near-earth object tracking, or astronomy data are missing, leaving the server with only a trivial utility and a date function.