New:Microsoft Teams Notifications Are Now Available in Socket.Learn more
Get Started

manna-mcp

Package Overview
Dependencies
Maintainers
1
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

manna-mcp

MANNA — MCP Architecture for NOIRLab, NRAO, and Additional Archives

pipPyPI
Version
0.9.0
Weekly downloads
925
Maintainers
1
Created

MANNA

Documentation

MANNAMCP Architecture for NOIRLab, NRAO, and Additional Archives.

An MCP server exposing IVOA-compliant astronomical archives (NOIRLab Astro Data Lab, NRAO/ALMA, CADC, ESO, Gaia, …) to LLM clients.

Naming: MANNA in prose (it's an acronym); lowercase manna for every identifier — the Python package, python -m manna, the manna:dev image tag, and the MCP client alias (mcp__manna__*). The one exception is the PyPI distribution, manna-mcp (bare manna is admin-prohibited on PyPI).

Tools

MANNA has four layers. Connections call the standard IVOA interfaces (TAP, SIA, SCS, RegTAP, Sesame). Workflow tools bundle a multi-step task into one call. Result handling returns small results inline and a link plus a fetch recipe for large ones. Archive notes are one file per archive holding its addresses and notes about its quirks, each note with a check that re-verifies it. Every tool below is tagged with the layer it belongs to.

ToolProtocolLayerDescription
list_archivesArchive notesList known archives with endpoint URLs and usage notes
describe_tableArchive notesCurated per-table schema facts (missing columns, enum values, spatial index hints)
resolve_target_nameSesameConnectionsResolve an object name (e.g. "M87", "Cygnus A") to RA/Dec coordinates
run_adql_queryTAPConnections · Result handlingSubmit sync or async ADQL queries; returns inline or promoted results
get_async_job_statusTAPConnectionsPoll an async job by ID
get_async_job_resultsTAPConnections · Result handlingReturn a completed async job's result URL + pyvo fetch recipe (client fetches the data)
abort_async_jobTAPConnectionsAbort a running async job
search_ivoa_registryRegTAPConnectionsSearch the IVOA registry by keyword or service type
describe_ivoa_serviceRegTAPConnections · Result handlingDescribe a specific registry resource (columns, capabilities)
search_catalog_by_positionSCSConnections · Result handlingSimple Cone Search for legacy SCS-only archives
search_images_by_positionSIA 2.0Connections · Result handlingSearch for images by position and waveband (returns access URLs to fetch client-side)
find_observations_of_targetSIA 2.0 / SCSWorkflow toolsOne-call workflow tool: resolves a target name or coordinates, auto-selects an archive by service/waveband, then runs the SIA (image) or SCS (catalog) search — chains resolve_target_name + list_archives + search_images_by_position/search_catalog_by_position so the model doesn't have to
count_observations_near_targetTAPWorkflow toolsCount observations/sources near a target in one call (resolve → select archive → COUNT)
survey_archives_for_targetTAPWorkflow toolsSurvey which archives hold data for a target, with per-archive counts
preview_tableTAPWorkflow tools · Archive notesColumns + curated enums/notes + a sample of rows for one table, in one call

Renamed in 0.9.0. Tool names dropped the vo_ prefix for verb-first, descriptive names; clients pinned to the old names must update.

Before 0.9.0Now
vo_archive_listlist_archives
vo_schema_describedescribe_table
vo_inspect_tablepreview_table
vo_target_resolveresolve_target_name
vo_tap_queryrun_adql_query
vo_tap_statusget_async_job_status
vo_tap_resultsget_async_job_results
vo_tap_abortabort_async_job
vo_registry_searchsearch_ivoa_registry
vo_registry_describedescribe_ivoa_service
vo_cone_searchsearch_catalog_by_position
vo_sia_searchsearch_images_by_position
vo_find_observationsfind_observations_of_target
vo_count_observationscount_observations_near_target
vo_survey_targetsurvey_archives_for_target

The recommended LLM workflow for a positional query:

  • resolve_target_name — get RA/Dec for a named object
  • list_archives — discover the archive and its endpoint
  • describe_table — get table-specific quirks before writing ADQL
  • describe_ivoa_service — live column introspection
  • run_adql_query (mode=async for data reads) — run the query

Install

pip install manna-mcp                # distribution name; the import + CLI are `manna`
manna                                # boots the server on http://localhost:8000
# or run without installing:
uvx manna-mcp

As an MCP server in a client

MANNA speaks stdio with --stdio, and streamable HTTP otherwise. For a stdio client (Claude Desktop, Claude Code, IDE extensions):

claude mcp add manna -- uvx manna-mcp --stdio

or, editing a client config by hand:

{"mcpServers": {"manna": {"command": "uvx", "args": ["manna-mcp", "--stdio"]}}}

The first launch resolves astropy and pyvo, which is a large download; run uvx manna-mcp --stdio once in a terminal before wiring it into a client whose startup timeout is short.

Quickstart

uv sync
uv run pytest --record-mode=none        # 732 tests, offline replay
uv run python -m manna                  # server on http://localhost:8000

Smoke test with MCP Inspector:

npx -y @modelcontextprotocol/inspector --cli http://localhost:8000/mcp --method tools/list

Development

uv sync                        # install runtime + dev deps
uv run pre-commit install      # enable git pre-commit hooks (once per clone)

uv run ruff check .            # lint
uv run ruff format .           # format
uv run pyright                 # type check (src/, basic mode)
uv run pre-commit run --all-files   # run every hook over the whole tree

Pre-commit runs ruff (lint + format), file-hygiene checks, and pyright on each commit; the full test suite runs in CI, not at commit time.

Branch flow (see CLAUDE.md for detail): feature branches <initials>/<name> branch off dev and PR into dev; dev is promoted to main via PR. main is protected — it only advances through PRs with passing CI.

Configuration

All settings are optional — defaults work for local dev. Set via environment variables prefixed MANNA_ or in a .env file:

VariableDefaultDescription
MANNA_PORT8000HTTP listen port
MANNA_HOST0.0.0.0Bind address
MANNA_LOG_LEVELINFODEBUG / INFO / WARNING / ERROR
MANNA_TAP_SYNC_TIMEOUT_SECONDS20.0Timeout for sync TAP queries
MANNA_ALLOWED_HOSTS(unset)Comma-separated hostnames the server may fetch (exact or subdomain match). Unset ⇒ any public host; private/loopback/link-local targets are refused regardless
MANNA_ARCHIVES(unset)Comma-separated archive short_names to activate. Unset/empty ⇒ all archives physically present in archives/ except paused ones (nrao ships paused; name it here to re-enable)
MANNA_INLINE_ROW_LIMIT200Max rows in an inline result before it's routed to an async job (TAP) or truncated (cone/SIA)
MANNA_INLINE_BYTE_LIMIT49152Max bytes in an inline result before the same promotion/truncation applies (48 KiB)
MANNA_REGISTRY_DESCRIBE_BYTE_LIMIT49152Above this, describe_ivoa_service degrades from per-column detail to a table catalog (names + descriptions + column counts)

See .env.example for a template.

Docker

docker build -t manna:dev .
docker run -p 8000:8000 manna:dev

Forking for a specific deployment

This repo is the multi-archive base. Each archive is one self-contained file — its endpoints, usage notes, and per-table schemas all live in src/manna/archives/<short_name>.py. Shape which archives make curated claims two ways:

  • Physical — delete the unwanted src/manna/archives/<short_name>.py files. Discovery picks up whatever remains; no other file needs touching.
  • Runtime — set MANNA_ARCHIVES=datalab,alma (comma-separated short_names) to narrow a shared image without deleting files. Unset/empty ⇒ every archive active.
  • Paused — an archive can set paused="<reason>" to ship inactive by default without losing its notes. nrao is paused while NRAO rebuilds its TAP service; MANNA_ARCHIVES=datalab,alma,nrao re-enables it.

A dropped or deselected archive loses only the server's curated claims about it — never its reachability. It's still reachable via search_ivoa_registry.

Refreshing recorded cassettes

Tests replay archive HTTP traffic from YAML cassettes in tests/<area>/cassettes/. To refresh a stale cassette:

# requires network access to the archive endpoint
rm tests/<area>/cassettes/<test_module>/<test_name>.yaml
uv run pytest tests/<area>/<test_module>.py::<test_name> --record-mode=once

Inspect the cassette diff before committing — large changes in the VOTable namespace URI or response headers may indicate an upstream breaking change.

Docs

Full documentation: https://manna.readthedocs.io — installation, client setup (Claude Code, Claude Desktop, Jupyter AI), a guide to how results and archive notes work, the generated tool reference, and tutorials.

Deployment configurations are maintained in a separate repository.

Keywords

adql

FAQs

Related posts