Provides tools for searching the MAST (Mikulski Archive for Space Telescopes) archive, enabling cone searches, mission-scoped queries, CAOM queries, and target name resolution to access NASA's space telescope data.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-mast-nasa resolve coordinates for M31"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MAST — Mikulski Archive for Space Telescopes (STScI) MCP — Hubble, JWST, Pan-STARRS, GALEX, K2/Kepler, TESS data. Keyless.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
cone_search(ra, dec, radius_arcmin, mission?, limit?) — search MAST around a point
mission_search(mission, criteria, limit?) — search by mission with criteria object
caom(query) — generic CAOM (Common Archive Observation Model) query
lookup_name(name) — resolve target name → coords + observations
Related MCP server: NASA MCP Server
https://mast.stsci.edu/api/v0/ (legacy POST-based JSON API).
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"mast-nasa": {
"url": "https://gateway.pipeworx.io/mast-nasa/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/mast-nasa/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Mast Nasa data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
NASA MCP — wraps NASA Open APIs (api.nasa.gov)
NASA astronomy photo of the day + imagery. $0.01/query. Register in-session — free testnet funds.
Search and fetch Wikidata entities, execute SPARQL queries, and resolve external identifiers.
CDS SIMBAD — astronomical object database (~14M objects) via TAP/script