Roadmap¶
edi-mcp is built in seven steps, one pull request each. Steps 1–5 are released on
main: the scaffold and auth probe, the MCP core (registry, transports, edi_ping,
conformance tests), the EDI client with both backends, the four
discovery tools, and the package, metadata and entity tools. Everything on this page is planned and not yet
available; tool names and inputs may still change. The tool reference
lists only what is registered today.
Step 6 — previews, downloads, citations and key-only services¶
| Planned tool | Purpose | Key |
|---|---|---|
edi_preview_entity |
The first rows of a tabular entity, read with a byte cap. | optional |
edi_download_entities |
Save data entities under the configured download directory and verify their SHA-1. stdio only. | optional |
edi_download_package |
Save a whole package as a zip. stdio only. | required |
edi_get_citation |
A formatted citation (ESIP, DRYAD or BibTeX) from cite.edirepository.org. |
optional |
edi_get_quality_report |
A summary of PASTA's congruence checks for a package. | required |
edi_get_lineage |
Provenance: a package's sources and descendants. | required |
edi_recent_changes |
Recent inserts, updates and deletes, by date or scope. | required |
edi_get_read_counts |
Download and read counts for a package. | required |
"Required" tools have no DataONE counterpart and will return auth_required without
a key (see Backends). Downloads will be the only tools that write,
will never overwrite, and will be offered only over stdio.
Step 7 — resources, prompts and release¶
- More
edi://guides and references, and resource templates for a package and its raw EML. - Prompts for finding data, citing a package and planning a download.
- A
server.jsonfor the MCP Registry, a Docker image, and the v0.1.0 release on PyPI.