Quickstart¶
This walks through a first session in Claude Code1; other clients work the same way once connected (Clients).
1. Register the server¶
Leave out -e NEON_TOKEN=… to start without a token; everything except file
listing, downloads and sample views works anonymously.
2. Check it¶
Ask the agent to "call neon_ping". The result shows the version, protocol
2026-07-28, whether a token is configured and whether downloads are enabled.
3. Five calls from question to citation¶
The agent normally chains these on its own; the arguments below are what it sends. Results are abbreviated.
-
Find the product
→
DP1.10003.001Breeding landbird point counts, withnextStepssuggestingneon_get_availability(product='DP1.10003.001'). -
Check availability (no token)
→ one row per site in domain D01 with month ranges such as
"2015-05/2024-06", split by release inbyRelease(PROVISIONALmonths included and counted innotes). -
List the files (token)
{"tool": "neon_list_files", "arguments": {"product": "DP1.10003.001", "site_codes": ["Harvard Forest"], "start_month": "2023-06", "kind": "data"}}→
resolved: [{"input": "Harvard Forest", "code": "HARV", ...}]and thebrd_countdata,brd_perpoint… CSVs with sizes, MD5s and signed URLs valid for about 7 days. -
Download (stdio)
{"tool": "neon_download_files", "arguments": {"product": "DP1.10003.001", "site_codes": ["HARV"], "start_month": "2023-06", "kind": "data"}}→ files under
~/neon-downloads/DP1.10003.001/HARV/2023-06/, MD5-verified, with apandas.read_csv(...)hint. -
Cite
→ NEON-format text and BibTeX with the newest release DOI.
The neon://guide/agent-workflow resource carries the same recipe for agents.
-
Claude Code — MCP. https://docs.claude.com/en/docs/claude-code/mcp ↩
-
NEON Data API. https://data.neonscience.org/data-api/ ↩