spedas-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| spedas_overviewA | Describe available SPEDAS MCP capabilities and the recommended workflow. |
| search_spedas_data_sourcesC | Recommend whether a SPEDAS request should start with CDAWeb, PDS, SPICE, or a mix. |
| plan_spedas_observationB | Plan a SPEDAS science workflow before using low-level CDAWeb/PDS/SPICE tools. |
| compare_cdaweb_pds_spiceC | Compare CDAWeb, PDS, and SPICE roles for a SPEDAS MCP science request. |
| create_spedas_analysis_bundleC | Create a lightweight request/provenance bundle for a planned SPEDAS analysis. |
| browse_observatoriesA | List CDAWeb observatories with descriptions, dataset counts, and instruments. |
| load_observatoryB | Load CDAWeb observatory prompt/catalog for a lowercase observatory stem. |
| browse_parametersC | Browse variables/metadata for one or more CDAWeb dataset IDs. |
| fetch_dataC | Fetch CDAWeb timeseries data, write a file, and return metadata/stats only. |
| browse_pds_missionsB | List PDS PPI missions/spacecraft with descriptions, dataset counts, and instruments. |
| load_pds_missionA | Load PDS PPI mission prompt/catalog for a lowercase mission stem. |
| browse_pds_parametersC | Browse variables/metadata for one or more PDS PPI dataset IDs. |
| fetch_pds_dataC | Fetch PDS PPI timeseries data, write a file, and return metadata/stats only. |
| list_spice_missionsA | List supported SPICE spacecraft/body missions with NAIF IDs and kernel status. |
| get_ephemerisC | Get single-time state inline or timeseries trajectory written to CSV. |
| compute_distanceC | Compute distance between two SPICE targets over a time range. |
| transform_coordinatesC | Transform a 3D vector between SPICE coordinate frames. |
| list_coordinate_framesA | List supported SPICE coordinate frames and usage notes. |
| manage_cdaweb_cacheC | Manage CDAWeb cache and metadata/catalog refresh operations. |
| manage_pds_cacheC | Manage PDS cache and metadata/catalog refresh operations. |
| manage_spice_kernelsC | Manage SPICE kernels and cache state. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/spedas/spedas_agent_kit'
If you have feedback or need assistance with the MCP directory API, please join our Discord server