aqc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port | 3000 |
| ADS_API_KEY | No | NASA ADS API token (required for ADS queries) | |
| MCP_TRANSPORT | No | Transport mode (http or stdio) | stdio |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| simbad_queryC | Query SIMBAD astronomical database by object identifier (e.g. M31, NGC 1234, Vega) |
| vizier_queryB | Query VizieR catalog service. Cone search by coordinates+radius on a specific catalog. |
| alma_queryB | Query ALMA (Atacama Large Millimeter Array) archive by object name or coordinates |
| gaia_cone_searchC | Cone search on Gaia DR3 catalog by coordinates and radius |
| gaia_adqlC | Execute a raw ADQL query on the Gaia archive |
| ads_searchA | Search NASA ADS (Astrophysics Data System) for academic papers. Requires ADS_DEV_KEY or ADS_API_KEY env var. |
| aavso_query_starC | Query AAVSO VSX (Variable Star Index) for a specific variable star by name |
| aavso_query_regionC | Query AAVSO VSX for variable stars in a circular region around coordinates |
| fermi_lat_catalog_queryC | Query Fermi LAT point source catalog (4FGL-DR4, the latest 14-year catalog) |
| fermi_lat_adqlB | Execute a raw ADQL query on the Fermi LAT archive (TAP service) |
| esasky_queryC | Query ESASky archive for astronomical observations by position and radius |
| eso_queryC | Query ESO (European Southern Observatory) science archive by target, instrument, or coordinates |
| exoplanet_queryC | Query NASA Exoplanet Archive for confirmed exoplanet data |
| heasarc_queryC | Query HEASARC (High Energy Astrophysics Science Archive) by object name and mission catalog |
| irsa_queryC | Query NASA/IPAC Infrared Science Archive (IRSA) by coordinates and catalog |
| irsa_tapC | Execute raw ADQL query against IRSA TAP service |
| jpl_horizonsC | Query JPL Horizons for solar system body ephemerides, orbital elements, or state vectors |
| jpl_sbdbC | Query JPL Small-Body Database for asteroid/comet orbital and physical data |
| mast_queryC | Search MAST (Mikulski Archive for Space Telescopes) for observations by object name or coordinates |
| ned_queryB | Query NASA/IPAC Extragalactic Database (NED) for object information by name |
| nist_linesC | Query NIST Atomic Spectra Database for spectral line data |
| sdss_queryB | Query the Sloan Digital Sky Survey (SDSS DR18). Supports cone search, specobjid lookup, and plate/mjd/fiberid lookup. |
| splatalogue_linesB | Query the Splatalogue spectral line database by frequency range. Optionally filter by chemical species name. |
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 23 tools
Each tool maps to a distinct astronomy archive or service, so most are easily differentiated by target source. However, the IRSA pair (irsa_tap vs irsa_query) and the Gaia/Fermi ADQL vs cone/catalog pairs could cause slight confusion about which to pick for a given query.
Names consistently use snake_case and generally follow a service_query or service_action pattern. Some action suffixes vary (tap, adql, cone_search, horizons, sbdb, lines), but the pattern remains readable and domain-consistent.
At 23 tools, the set is heavy and includes multiple similar query endpoints for different archives. For a broad astronomy aggregator the breadth is defensible, but the count is above the typical well-scoped range and adds cognitive load.
The surface covers a wide range of major astronomical archives and services, with read-only queries appropriate for the domain. Minor gaps exist, such as no generic TAP discovery or data-product download, but core research workflows are well supported.